►
From YouTube: Weekly Package Meeting 07-16-19
Description
In which we discuss the 12.1 and 12.3 milestones.
C
It's
on
there
I
like
this:
better
okay,
so
weekly
package
meeting.
We
have
a
few
items
on
the
agenda,
I
think
just
a
actually
only
a
few,
so
it
might
be
a
quick
meeting,
so
the
first
ones
may
I
have
the
reviewed
12.1
milestone
to
see
which
issues
need
to
carry
into
12.2
or
12.3,
and
then
I
just
highlighted
a
couple
of
items
that
I
put
into
the
blog
post.
That's
going
to
go
out
on
the
22nd.
C
C
A
D
D
A
B
D
D
B
It's
the
super-surprising
we've
had
a
couple
engineers
on
the
release
team
that
are
this
newer
ish
and
some
of
the
things
that
they've
been
having
to
focus
on
more
than
they
expected
was
sort
of
that
deliberate
communication.
So
making
sure
that
before
you
sign
up
for
the
day,
you
you
shipped
everything
that
that
person
is
going
to
need
when
they
wake
up
in
four
hours.
B
You
know
or
like
a
chunk
it
out
a
little
bit
so
that
you
can
use
feature
flags
to
you,
know,
sort
of
limit
the
impact
of
a
change
and
then
go
and
and
instead
of
one
big,
mr-
that
takes
a
long
time
to
review
and
can
lead
to
cascading
refactorings
like
that,
take
it
and
break
it
down
into
smaller
pieces.
So
then
you
can
like
do
this.
B
B
Think
I
think
it's
a
little
bit
unique
here,
but
I've
definitely
seen
that
happen
with
engineers
on
release
to
where,
especially
that
first
one
where
you're
like
I,
got
this
change
and
it's
done
and
then
you
run
into
a
brick
wall
and
it
takes
a
while
to
gets
rid
so
yeah,
that's
that's!
Those
are
the
things
that
I
would
focus
on
is
like
that.
You
know
deliberate
communication
and
then
you
know
try
to
try
to
break
it
down
as
best
you
can.
It
doesn't
work
for
every
feature.
D
B
A
Thanks
for
that
sadly
appreciate
your
experience
and
your
Steve
I'm
happy
to
be
like
helpful
there.
Obviously
it's
these
new,
your
first
few
issues
and
I'm
trying
to
just
let
you
figure
what
out
you
figure
everything
out
as
you
need
to
figure
it
out,
but
I
feel
like
I
feel
at
some
level.
There's
a
bit
of
a
disconnect
here
with
maybe
I
could
have
been
more
helpful
with
guidance
around
finishing
off
communication
at
the
end
of
the
day,
those
sorts
of
things,
if
you
think
I,
could
be
doing
something
better.
C
Thanks
that
was
awesome.
Okay,
so,
as
far
as
12-1
goes,
I
shared
a
link
to
the
chat
as
well.
Just
a
12-1
planning
board
and
I'm.
Looking
in
the
open
and
deliverable
columns,
I
believe
there's
three
issues
for
Conan,
the
the
Conan
Skelton
API,
the
server
authentication
and
the
overall
MDC
I
believe
we're
moving
all
of
those
to
12
right.
A
C
E
A
E
A
E
Sorry,
I,
don't
think,
was
picked
up
as
a
regression.
I
think
it
was
just
basically
because
we
couldn't
use
the
standards
empty
state
component
that
exists
in
gitlab
UI,
because
we
want
it
to
inject
some
more
customized
content
than
the
component
would
allow.
So
because
we
did
that
and
we
didn't
use
the
standard
component.
E
The
width
of
the
message
wasn't
up
to
get
labs
standard,
empty
state
size,
and
that
was
pointed
out
via
mu,
X,
the
UX,
despite
that
and
create
a
new
issue
which
we've
now
since
resolved
and
I've
also
updated
them
to
state
component,
although
that
isn't
it
hasn't
been
merged
to
give
up
UI
just
yet,
but
that
will
be
coming
and
I
believe.
There's
a
tech
debt
issue
to
now
change
what
we've
used
to
get
around
this
to
actually
using
the
get
LabVIEW
I
component
when
it's
ready
nice.
C
E
C
That's
for
that.
That's
for
changing
the
navigation
to
rolling
the
registry
under
packages.
The
list
that's
going
to
yeah,
okay,
so
it's
it's
merged,
but
it's
not
live
yet
I
believe
so
yeah,
okay,
okay,
yeah,
because
sometimes
I
see
it
that
it
is
there
sometimes
I,
like
oh
I,
just
like
yesterday,
I
was
in
one
project
and
I
saw
packages
in
list
and
then
and
another
one
I'll
see
the
registry
and
package
separate
like
the
old
way.
I,
don't
know
if
that's
possible.
E
C
C
Think
there's
some
other
UI
issues
and
documentation
things
I
could
follow
up
with
axel
and
and
see
what
what's
happening
with
that.
Okay,
that
makes
sense
so
then
for
I
did
want
to
do
a
quick
review
of
what's
going
in
12
3
right
now
is
that
if
we
could
take
a
minute
for
that,
so
I'm
now
I'm
looking
on
the
our
normal
package
planning
board,
this
is
linked
in
the
dock,
but
I'll
just
link
it
here.
Just
so,
we
have
it
and
I'm.
C
Looking
at
the
12
3
column,
which
the
first
item
here
is
an
issue
that
Georgina's
is
working
on.
This
is
the
popular
issue
where
deleting
a
tag
deletes
all
tags
with
the
same
image
ID.
Historically,
this
has
been
due
to
a
an
issue
with
the
docker
API,
not
supporting
this
and
Dockers.
Had
this
issue
open
for
a
couple
of
years
and
our
users
are
saying
you
have
to
solve
this.
This
is
this
is
too
much
of
a
problem,
so
we
prioritized
this
one.
C
C
So,
with
the
new
release
of
helm,
three
basically
helm
charts,
which
is
the
package
manager
for
kubernetes,
changed
the
back
end
for
helm,
charts
that
you
stuff
to
use
tiller
as
the
container
repository
and
now
you
can
use
a
doctor
at
container
registry,
so
they're,
taking
advantage
of
the
Oakland
container
initiative
and
they're
basically
changed
the
backend
for
that
microsoft's.
Already
doing
this,
they'll
announced
that
azure
devops
container
registry
supports
home
charts.
Some
of
our
users
in
the
issue
are
actually
already
doing
this
and
showing
it
work
showed
it
working.
C
So
this
issue
is
just
to
add
that
minimal
support
to
see
if
it
works
and
then
add
some
documentation
to
our
our
examples.
So
we
could
show
users
how
to
do
it
and
see
what
we
need
to
do
to
add
more
support
in
the
future.
If
we
need
to
the
next
issue,
is
this
authenticate
CI
job
token
for
the
NPM
registry?
I
actually
had
wasn't
sure
about
this
one
Steve,
because
I
know
we
changed
the
personal
access
token
to
be
OAuth,
but
I'm,
not
sure.
C
I'll
keep
the
issue
in
there.
Maybe
I'll
make
it
a
similar
investigate
if
a
new
issue,
it
says,
like
investigative
CI
job
token,
has
support
for
OAuth
and
I'll
put
that
above
this
one
and
if
it
does,
then
we
could
have
another
one
that
says,
make
the
change
and
then
like.
We
did
for
personal
access,
token
cool.
D
C
And
then
the
Maven
packages
support
for
subgroups
and
group
endpoints.
So
it's
basically
what
we
did
for
NPM
I,
really
like
how
we
changed
the
way
that
we
do
our
naming
conventions
as
well
so
doing
something
similar
for
maven
would
be
awesome,
would
be
really
would
bring
those
features
into
parity.
So
it's
another
issue,
that's
planned,
and
then
we
have
two
issues
that
came
up
from
the
hacker
one
security
report.
C
These
are
about
basically
for
the
list
of
packages
and
for
the
container
registry
you
have
users
who
shouldn't
have
access
to
the
project
can
view
them,
so
those
were
labeled
as
I
think
s3.
So
we
have
90
days
to
address
them,
but
really
for
us
to
do
them
in
twelve.
Three,
that's
right
at
that
90-day
limit,
so
I'm
prioritizing
those
two
security
issues
in
twelve
three
and
then
a
couple
more.
The
API
endpoint
to
list
the
packages
of
a
group,
so
Steve
I
think
you're
already
working
on
this
for
the
container
registry
in
12.
C
A
Those
all
look
good
I,
think
you
know
with
the
security
with
those
p3s
trees.
We
probably
want
to
invest
a
little
time
ahead
of
ahead
of
one.
We
need
to
get
them
down
to
make
sure
actually
looking
at
what's
involved,
I
would
hate
to
have
those
slip,
so
it's
probably
worth
investing
a
minute,
I'm,
not
sure
Steve.
You
have
thoughts
around
how
that
would
work
for
you.
A
Obviously,
if
the
team
grows,
I
have
more
people
that
contribute
there,
but
right
now,
whether
you
need
help
or
whether
you
want
to
spend
like
spend
a
couple
of
hours
each
looking
at
them
just
ahead
of
time
to
see.
If
you
have
any
big
question
marks,
I
think
with
those
sorts
of
things
it's
important
to
sort
of
be
relatively
confident
in
the
work
that
we
have
to
get
done
prior
to
sort
of
putting
it
into
one
of
our
milestones.
Disc
is
the
security
factor.
It's
I,
don't
want
to
mention
them
too
much,
because
that's.
C
The
point
but
yeah
I
was
I
was
thinking
next
week
we
on
the
22nd
or
23rd.
That's
when
we're
supposed
to
have
the
milestone
finalized
from
a
product
perspective,
and
then
that's
when
engineering
usually
does
the
investigation
from
we
they're
in
the
first.
So
that
could
be
a
likely
allotted
time
to
go
in
and
and
it'll
give
me
a
little
bit
more
time
to
finalize
the
the
milestone,
and
so
then,
next
week,
to
the
basically
from
the
22nd
to
the
1st
could
be
used
for
investigation.
D
C
I
think
Steve
the
big
change
for
you
might
be.
If
we're
trying
to
transition
the
Konan
work
to
you,
there
might
be
some
changes
on
some
other
priorities:
we'll
need
to
figure
that
out
as
well
cool,
okay
and
then
Nick
I.
Are
there
any
issues
that
you
wanted
to
bring
forward?
I
know
actually
you're
in
it.
Your
issue
on
on
this
board
is
really
cool.I.
The
container
registry
UI
update
I
wonder
if
we
should
plan
on
bringing
that
into
twelve
three
as
well.
E
Yeah
I
think
so
I'm
just
in
the
process
of
putting
a
mock-up
of
what
it
could
potentially
look
like
and
then
yeah
I
invite
any
sort
of
feedback.
And
if
my
point
was,
is
that
I've
created
this
issue,
and
so,
if
anybody
had
any
ideas
or
feedback
suggestions,
comments
whatever
to
check
out
the
issue
and
leave
them
there
and
hopefully
yeah
we
can.
We
can
work
on
building
something
that
looks
sort
of
a
little
bit
nicer
than
what
it
does
right
now
yeah,
but
yeah.
We
if
we
can
bring
it
forward,
then
I'm.
C
Awesome
yeah,
that's
great
I,
really,
like
all
your
ideas
and
I
I'm
impressed
with
how
code
fresh
handles
there
can
take
container
registry
I
think
they
have
a
lot
of
similar
use
cases
to
us
and
that
they
have
pipelines
built
in.
They
have
the
code
the
commit
Shaw's
in
there
and
the
branches
compared
to
like
how
docker
hub
or
Quay
does
it,
because
they
don't
have
the
same
set
of
considerations
that
we
do
so.
It
could
be
a
little
bit
of
inspiration
to
look
through
some
of
their
documentation
or
watch
some
of
their
example.
E
F
Thank
you,
and
basically
it
was
just
a
quick
update
on
what
I'm,
currently
working
on
being
the
distribution
tanks,
with
the
help
of
Steve
I,
was
able
to
understand
well
basically
with
the
endpoints
how
to
find
endpoints,
and
that
was
the
be
hurdle
for
for
a
while.
What
I'm
working
on
so
a
day,
ideally
would
be
the
option
to
list
tags.
So
I
saw
that
the
end
points
is
slash.
F
This
tags,
but
it's
not
hitting
so
I'll,
have
to
I'll
have
to
figure
out
why
maybe
I
didn't
create
the
correct
endpoint,
but
otherwise
I
feel
confidence
about
writing
specs
this
week
and
hopefully
having
something
ready
next
week
and
I'll
probably
reach
out
to
unit,
because
we
have
to
list
the
tags
in
the
UI
and
I'll
probably
need
some
help
with
that,
or
so,
ideally,
like
a
pairing
session.
In
your
time
with,
you
would
be
awesome
if
that
works.
For
you.
F
A
I
guess
I'm
I'm
I,
don't
have
enough
context
to
sort
of
know
whether
there's
extra
work
that
has
to
go
into
this
so
I'm
also
still
learning
how
we
usually
do
that
so
I
don't
know
Darby.
If
you
want
to
weigh
in
on
whether
that's
something
that
someone
would
normally
assigned
to
themselves,
but
if
you're
sort
of
actively
working
on
it
I
don't
know
I
generally
look
at
issues,
although
I
do
look
at
a
lot
of
Emma's
as
well
so
thoughts.
B
Daddy
sorry,
the
question
was
about
assigning
an
M
R
or
an
issue
issue
yeah
I,
think
I.
Think
in
general
we
at
least
unreleased.
We
try
to
indicate
that
we're
working
on
something
by
having
an
having
it
having
our
face
on
it.
So
that's
that's,
that's
usually
how
we
do
it
or
that
we
plan
to
work
on
it.
If
it
doesn't
have
an
assignee,
then
it's
not
really
clear
who's.
Who
who
owns
it
so
trying
to
have
some
sort
of
ownership
indicated
by
that
is,
is
usually
the
goal.
A
A
Well,
thank
you
peeps,
for
your
time,
I
think.
If
there's
no
one
else
has
anything
and
then
we
can
wrap
this
up.
Everyone
awesome
work.
Thank
you
so
much.
It's
really
nice
to
see
everyone
sort
of
getting
up
to
speed
and
getting
things
done,
it's
a
really
motivating
and
it's
really
fun
really
appreciate
everyone's
effort.
It's
awesome.
Thank
you.