►
From YouTube: 2022-03-29 Package Quad Weekly Planning
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).
A
B
I
have
the
first
one
so
currently
the
cdn
test
has
been.
It
has
been
work
already
for
a
while
and
while
it
it
seems
closer
and
closer
it's
just
I.
I
wasn't
able
to
make
progress,
so
I
already
reached
out.
We
have
a
little
sync
and
we're
gonna
take
a
look
at
it
because
it's
just
it's
a
big
setup.
So
it's
better.
If
we
actually
sync
it.
A
C
Yeah,
so
the
the
first
dependency
is
in
my
internal
review.
I
started
working
on
the
second
one
and
I
just
noticed
that
this
third
one
is
not
scheduled
for
1410.
Actually,
it's
in
the
backlog.
A
Yeah,
this
is
an
interesting
one,
so
we
got
the
approval
to
get
jose,
supporting
us
with
the
frontend
issues,
so
he's
trying
to
figure
out
where
the
quickest
one
to
to
work
so
they're
we're
going
to
have
some
bombs
in
there.
If
we
have
dependencies
with
back
and
work.
C
A
Jose
is
going
to
be
picking
the
issues
and,
as
soon
as
he
starts
working
he's
going
to
move
them
to
the
milestone.
If
he's
able
to
work
on
this
mice
and
hurt,
but
the
back
incisions
were
on
this
master
right.
A
A
Good
anyone
remember
any
other
situation
that
we
have
chain
dependencies.
D
No,
I
just
know
that
I've
seen
a
lot
of
issues
open
for
the
phase
two
work,
but
it
seems
like
they're
getting
opened
and
closed
just
as
fast
just
making
sure
there's
no
does
anything
else
need
to
shift
out
of
the
milestone
that
we
should
be
aware
of
as
a
result
of
those.
E
I
covered
this
in
the
in
the
next
section,
a
little
bit
jump
right
into
that,
and
so
on
the
real
side
yeah.
We
continue
to
have
small
fixes
for
phase
two,
but
we're
down
to
just
two
p1
issues
remaining
that
have
weight
two.
As
far
as
I
could
tell
there's
one
security
issue
and
one
regular
issue,
and
so
I
think
overall
we're
in
a
good
position
to
deliver
everything
this
milestone,
because
those
phase
two
fixes
or
issues
are
slowing
down
like
last
week.
E
There
was
a
big
flood
of
them
and
then,
in
the
last
day
or
two,
there
hasn't
been
as
many
so
hopefully
it
just
continues
to
slow
down
over
the
next
weeks.
A
Yeah
also
great
amazing,
and
if
you
start
to
see
like
for
some
reason,
this
is
this
is
don't
slow
down
and
we
start
to
see
more
issues
like
the
reminder
that
we
can
kick
off
like
it
out
from
the
milestone
wherever
and
make
sure
that
we
focus
on
the
phase.
Two.
D
I
saw
one
of
the
p1
security
issues
was
resolved
pretty
quickly,
so
yeah.
A
A
B
Yeah,
just
basically
it
doesn't
make
sense,
doesn't
make
sense
to
be
working
on.
B
I
just
look
at
the
code
for
the
online
garbage
collection
tool
that
we
did
back
then
in
the
beginning,
when
I
was
testing
the
in
earlier
migration,
it
makes
some
sense
to
be
working
on
this
now
after
the
migration
is
finished,
and
we
there's
probably
some
lesson
learned,
I
guess
it
makes
sense
to
work
on
that
only
later.
So
I
don't
see
the
point
on
having
this
on
this
mask.
Then
it's
just
yeah,
probably
we'll
take
it
out
of
there.
D
A
Good
next
topic
on
the
reliability
and
r
triage
report,
we
are
very
good
on
the
top
priorities
that
are
first
prioritization,
that
is,
security
and
infrared
error
budget
continues
in
red,
but
we
know
that
this
is
the
degradation
on
the
google
cloud
service,
but
for
other
issues
like
corrective
actions,
regressions
box,
f1
and
feature
flags,
we
have
a
long
list
of
things
to
do.
I
was
thinking
that,
if,
like
we
talked
about
having
a
focus,
milestone
on
reliability
is
15-2
a
good
candidate
for
this.
What
do
you
think.
D
Yeah,
I
know
that
there
are
probably
like
five
or
six
bugs
that
have
been,
that
I've
been
hunting
back
milestones
for
that
are
related
to
the
package.
That
would
be
awesome
to
tackle
if
we
could
bundle
those-
and
that
would
be
great
and
then
maybe
the
subsequent
milestone
that
could
be
sort
of
like
paying
down
technical
debt
and
that's
like
removing
feature
flags
and
anything
else
from
the
sprinting
that
we've
been
doing.
If
that
makes
sense,.
A
D
D
E
I
think
it's
safe
to
leave
room
until
the
migration
is
done
just
in
case.
It
hopefully
should
be
less
and
less
room
that
we
need,
but
we
should
definitely
plan
to
make
a
little
time.
E
D
The
big
one
is
the
permissions
changed
on
the
settings
just
because
that
we
might
want
to
do
that
behind
a
feature
flag
or
something
I
mean,
we've
already
announced
it
that
it
was
deprecated
for
a
while
the
rest
of
the
items,
I
believe,
have
already
been
deprecated,
so
it
is
just
the
removal
so
yeah,
just
the
permissions
change
is
the
one
that
I
think
might
be
a
little
bit
more
complex.
D
D
I'll
I'll
dig
that
issue
out.
Let
me
that
that
one,
I
think,
would
be
non-trivial
as
well.
D
A
D
G
A
D
So
the
next
yeah
it
seems
like
nothing
on
the
ux
debt
issues
this
time
and
on
strategy
updates.
I
just
added
a
couple
of
fyi
items,
the
first
just
being
that
we
have
this
package
use
case
page
that's
used
by
tams
and
sales
to
sort
of
understand
what
is
the
package
stage
and
how
can
they
engage
with
customers?
D
In
towards
that
goal
I
added
a
bunch
of
metrics
and
how
they
can
be
used
and
to
measure
adoption
for
each
customer.
The
only
limitation
here
is,
it
does
have
to
be
the
service
ping
data
it
can't
since
snowplow
at
least
the
metrics.
We
have
can't
look
at
the
specific
customer
level.
It's
just
anonymized
counts,
but
yeah,
I'm
just
sharing
that
and
we
saw
double
digit
growth
in
the
percentage
of
month
and
total
number
of
monthly
active
users
for
nougat
generic
packages
and
helm.