►
From YouTube: Package Weekly Sync 02-17-20
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
A
We
have
an
agenda
that
we're
going
through
and
it
looks
like
Dan
has
the
first
several
items.
I
will
do
my
best
to
do
my
best
dan
impression
number
one.
In
twelve
nine
we
have
an
issue
to
investigate
pipey
I
support.
G
G
is
going
to
take
this
issue
on
so
that's
already.
It
looks
like
that
was
already
assigned
to
him
and
everything
so
very
similar
to
what
we,
what
we're,
but
we've
done
with
nougat
and
Conan.
It's
you
know
the
similar
functionality
being
able
to
build
our
publish
and
pull
packages.
A
C
C
A
Another
a
mark
for
our
handbook
page
that
Dan
created,
is
removing
the
option
to
wait
something
as
five
plus
I
know.
We
had
him
and
I
had
a
conversation
on
I,
think
Friday,
where
we
were
talking
about.
We
want
to
avoid
having
issues
where
the
weights
are
five
or
more
because
it's
it's
too
big
to
fit
into
a
milestone.
So
we're
trying
to
add
add
language
to
our
handbook
for
that,
so
you
could
check
that
out.
If
you
have
any
concerns,
you
could
leave
a
comment
and
Emma.
A
We
added
a
board
that
lists
different
functional
teams,
issues
for
twelve
nine.
So
this
is
like
a
an
attempt
to
gain
efficiency
and
planning.
You
can
now
see
the
continued
Haley
and
Jerome
on
the
container
registry.
You
could
see
the
back
end
rails
and
then
the
front
end
team,
and
this
way
we
could
see
how
many
issues
and
what
the
weight
is
by
each
team
and
any
questions
on
any
of
that
stuff,
that
we
should
talk
about
all
right.
So
that's
my
day
and
impression
enter
David.
D
A
That's
awesome
to
hear
about
nougat
and
and
and
your
holiday,
hopefully
it's
fun
fun
one.
So
the
milestone
closes
today
and
I
noticed
that
there's
still
issues
that
are
open
in
twelve
eight
that
look
like
they
could
probably
be
closed
now,
like
nougat,
for
example.
So
can
everyone
just
take
a
look
and
close
any
that
have
been
released?
That
would
be
helpful
and
on.
C
E
Yeah
I
just
wanted
to
ask
a
general
question:
if
anybody
knows
that
we
have
any
issues
for
showing
when
a
dependency
proxy
was
used
within
a
pipeline.
It's
just
I
seem
to
remember
talking
about
this,
but
I
couldn't
find
any
issues
about
it
at
all,
and
I
I've
been
hanging
around
this
morning
for
I've
been
on
an
idea
bench
this
morning.
So
I
was
gonna,
write
up
a
bunch
of
issues
and
didn't
want
to
duplicate
effort,
similar.
E
Kind
of
like
my
idea
was
that
I
wanted
a
pipeline
to
clearly
demonstrate
that
it
had
touched
a
dependency
proxy,
so
you
could
sort
of
see
like
with
an
icon
or
something
like
that.
That's
what
I
was
thinking
of,
but
then
there's
there's
a
bunch
of
follow-on
ideas.
I
had
on
top
of
that
as
well,
but
I
distinctly
remember
discussing
it,
but
I
can't
find
any
issues
about
it.
A
E
F
B
So
the
container
registry
B
to
dot
a
dot
one
is
now
available
in
production.
It
was
deployed
three
hours
ago,
more
or
less,
and
the
same
goes
for
the
technology
improvements
in
in
github
I'm,
going
to
do
some
benchmarking
today
to
compare
the
results
now
and
the
ones
that
we
have
been
seeing
till
yesterday.