►
From YouTube: Weekly Package Group Retro 20200214
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
There's
a
little
back
and
forward
on
some
of
the
review
process,
which
is,
which
is
the
sort
of
slightly
more
detail.
They're
also
from
Gigi,
had
another
missing
feature
on
one
of
my,
mrs
that
managed
to
fix
it
in
a
new,
mr
and
then
over
to
Dan.
That's
me
trying
to
get
my
local
development
environment
hasn't
been
super
successful
so
far,
and
then
metrics
actually
haven't
stayed
consistent
and
dashboards
I've
been
using,
which
has
been
really
frustrating
for
me,
and
I
got
to
dig
into
a
little
bit
away.
A
What's
going
on
there,
it
might
just
be
that
the
projects
that
we
should
have
in
their
list
are
not
included.
So
I
need
to
verify
that
which
Dan
point
did
I
skip.
Oh
yeah,
yeah
I
did
thanks.
I,
said
I've
been
feeling
pretty
tense
all
week
and
making
sure
I'm
not
making
poor
decisions
around
that
has
been
a
bit
tough
for
me
was
that
the
one
thanks
follow
up
there.
Everyone
I
know
the
state.
B
This
week,
a
small
change
to
the
package
validation
in
order
to
fix
some
restrictions
with
the
Konan
naming
ended
up
being
kind
of
a
difficult
change
which
involves
some
database
index
changes
and
some
other
stuff,
and
then
that
ended
up
breaking
master
and
then
debugging
that
air
and
ended
up
being
a
pretty
puzzling
factory.
Bot
bug
so
just
ended
up
taking
a
lot
longer
than
expected
to
get
that
one
through
Tim.
C
Okay,
so
yeah
this
week,
just
flew
by
for
me
having
a
bunch
of
stuff
going
on
I
didn't
get
to
spend,
as
I
said
as
much
time,
but
really
anytime
on
some
of
the
problem,
validation
issues
that
I
wanted
to
work
on.
So
that
was
disappointing
and
then
I
learned
that
snow
plow
events
are
not
smell
eligible
and
that
they
don't
include
self-managed
instances.
C
So
I
added
something
to
the
handbook,
but
it
does
mean
that
a
lot
of
our
event
tracking
doesn't
include
our
self
manage
of
customers.
So
we
may
see.
I
did
learn
that
the
opt-out
rate
for
the
usage
ping
is
pretty
high,
but
we're
still
seeing
lower
numbers
than
expected
so
opened
up
some
issues
and
posted
some
stuff.
In
slack.
To
start
that
conversation,
though
hunter
Nick.
D
Yeah
say
for
me:
today's
felt
pretty
slow,
like
intensive
productivity.
From
my
point
of
view,
I
think
it's
because
I
had
a
front-end
review
this
morning
and
that
just
seemed
to
take
quite
a
while
and
just
I.
Don't
know
it
just
knocked
me
off
my
momentum.
I
guess.
I've
also
had
a
few
TDK
she's
this
week,
mostly
like
my
runners,
just
stopped
working
for
some
reason.
I
think
might
have
been
down
to
like
a
docker
update
or
something
like
that.
E
Yeah
so
last
week
this
this
Friday
last
week,
I
discovered
an
issue
with
the
resource
usage
for
s3.
We
need
to
use
the
and
flag
on
garbage
collection
and
I
had
to
you
know,
work
quickly
to
mitigate
that
which
was
not
a
fun
experience
to
find
that
issue,
and
this
week
I
just
stressed
worried
about
a
lot
of
the
the
release
and
I
think
it
I
just
didn't
feel
effective.
So
on
David.
F
So
this
week,
yeah
I
was
not
sure
how
to
release
the
you
know,
get
MVC
with
the
feature
flag
and
the
change
log
entry,
so
I
had
to
create
a
quick
Amara
yesterday
and
keep
fingers
crossed
that
it
would
be
merged.
It
has
been
so
we
should
be
cool
on
this
side.
Also,
the
Nuggets
are
Jamar
is
stealing
maintain
a
review
after
a
full
week,
so
yeah
start
feeling
really
we
do
so
over
to
Joe.
G
So
this
week
we
found
a
problem
in
Changi
which
causes
the
previous
container
registry
releases.
Not
to
do
it's
the
the
github.com
production
environment.
So
that's
very
substantial
because
of
this
in
12
fights
we
are
going
to
ship
more
than
we
thought.
We
would
forget
loud
welcome
and
then
asked
what
CNG
stands
for.
That's
a
good
question.
H
H
A
You
our
Charter,
was
correct.
Nice
job
I
got
to
create
more
chaos,
which
was
nice.
Are
they
with
deliverable
last
Friday,
so
I
completed
those
which
I'm
happy
about
and
I've
shared
those
with
everyone
on
the
team?
So
you
could
all
look
at
them
happy
to
get
feedback
on
those,
oh
cars
as
well.
If
people
feel
like
they
would
like
to
created
dashboards
and
getting
through
some
of
my
to
news
and
can
just
start
contributing
on
code
and
appreciate,
Steve
and
Hayley's
help
they're
trying
to
get
GDK
set
up.
A
B
Lagging
for
some
reason
so
this
week
the
container
expression
policy
fix
was
merged,
so
that
was
exciting,
that
that
went
through
relatively
quickly
and
then
I
was
also
able
to
get
us
a
couple
of
small
side,
mrs
through
which
always
feels
good,
and
I
was
pleasantly
surprised
that
the
first
twelve
nine
issue,
though
I
started
to
work
on
which
I
had
originally
thought,
was
going
to
be.
A
three
has
ended
up
moving
much
more
quickly.
So
that's
nice!
C
Think
I
was
very,
I
added
a
bunch
this
week,
so
I
think
the
milestone
planning
has
gone
really
well
for
twelve
nine,
although
we
don't
have
the
deliverable
tags
labels
yet,
but
I
the
conversations
been
really
productive
and
I
feel
like
we've,
iterated
a
bunch
on
the
issues
and
updated
proposals
and
stuff
like
that.
I've
I've
learned
a
lot
managing
the
release
post
both
about
other
stages
and
some
of
the
features
that
they're
releasing
and
prioritizing
and
also
different,
get
workflows
that
have
pushed
my
limits
and
I'm
proud
of
our
stage.
C
Science,
dashboard
and
I
haven't
actually
utilized
some
of
the
data
that
we
have
in
to
decisions
and
issues
this
week,
which
felt
really
cool
because
for
a
long
time
we're
just
making
decisions
and
now
we're
actually
using
data
and
actually
had
a
customer
reach
out
to
me
and
just
say
that
12-8
is
looks
like
an
awesome
release
and
that
they're
really
excited
for
all
those
features.
So
I
think
generally
it's
going
to
be
our
best
release
ever
lots
of
really
exciting
features
coming
out
in
that
and
then
I
added
one.
Thank
you.
C
We
got
the
first
version
of
the
survey
published
and
we
are
officially
gathering
data
around
the
jobs
to
be
done,
and
that's
for
the
survey
that
is
saying
what
has
to
be
true
for
you
to
replace
your
existing
third
party
package
manager,
tool
and
really
great
feedback
and
iteration
on
the
container
registry
UI.
It's
going
to
be
wrapped
up
and
ready
for
solution,
validation
in
1210,
the
next
milestone
onto
Nick.
D
Yes,
so
for
me
this
week,
I
got
quite
a
lot
of
little
Emma's
and
refactoring
Emma's
all
merged
this
week,
which
I
really
wasn't
expecting
to
happen
because
at
the
end
of
the
milestone,
it's
like
maintained
as
a
busy
except
researchers.
So
I
was
quite
surprised
that
a
lot
of
those
got
merged,
but
it
feels
good.
D
E
H
G
So
this
week
was
a
roller
coaster.
We
ship
the
ps3
performance
improvements
for
12
weights.
We
have
not
one
but
two
container
registry
releases.
Then
we
found
a
problem
in
Ch
CMG,
which
stands
for
a
cognitive.
He
talked
exactly
and
we
end
up
having
to
create.
Another
registry
leads
to
force
the
rollout
of
the
previous
suit.
G
So
that's
three
releases
in
total
in
a
single
week
and
as
well,
the
time
dbgap
I
promise
improvements
were
merged,
both
Gortat
lab
and
the
container
registry
and
I
already
tested
them
in
in
staging
and
I
was
a
bit
scared
because
of
the
bug
that
Nico
just
mention
it.
But
unfortunately
it
was
not
a
problem
and
the
results
look
are
looking
good.
A
Well,
I
think
this
is
probably
ins
item,
but
yeah
all
right
fitting
in
the
action
items
here
is
I.
Think
it's
in
any
way
reminder
if
you
haven't
filled
out
the
jobs
to
be
done
thanks
Haley,
so
they
please
do
so
and
provide
any
feedback
by
end
of
day
today.
Thank
you
and
the
survey,
links
and
feedback
issue.
Are
there
alright.
A
A
E
H
So
everything
is
set
to
go
correctly,
the
of
them
are
around,
it
are
merged.
The
expression
policy
is
still
behind
feature
flag.
So
what
needs
to
happen
is
that
the
older
fixed
production,
we
have
one
successful
round
of
testing,
and
then
there
is
an
already
Mr
ready
to
remove
the
feeder
flag,
but
we
will
be
able
to
merge
that
only
after
we
verify
that
everything
is
working
smoothly
and
the
process
is
a
bit
long
because
aim
is
to
its
production.
Then
one
day
is
mr.
H
H
B
You
keep
an
eye
on
the
releases
channel.
They
usually
kind
of
keep
that
up
to
date,
but
yeah
like
optimally
it'll
hit
dot-com
on
Monday.
When
they
do
be
released,
then,
and
then
we
will
be
able
to
see
whether
or
not
it
worked
by
around
noon
or
blonde
Pacific
time
on
Monday,
because
that's
when
it's
going
to
automatically
run
on
production
and
then
at
that
point
then
we
just
say:
like
hey
maintainer
x',
please,
please
remove
the
feature
flag
and
then
Rob
me.
A
C
A
F
Had
first
wound
of
feedback,
the
thing
is
that
the
first
back-end
maintainer
had
to
hand
off
the
EMR,
since
he
was
going
to
be
unavailable
shortly
and
then
I
received
a
parking
feedback
and
address
it
and
I
received
this
morning.
The
second
one
and
I'd
address
it
again.
As
for
the
database,
I
receive
one
I
address
it
and
the
maintainer
is
unavailable
unavailable
until
Tuesday.
F
Behind
the
the
issue
is
that
the
first
feedback
from
the
database
maintainer
was
kind
of
a
major
flaw
in
the
search
query,
so
I
fixed
it
and
now
I
have
to
wait
for
for
feedback,
and
so
the
this
maintainer
has
the
context
of
the
issue
and
how
the
first
review
has
been
made.
So
since
we
know
that
this
merge
request,
will
sleep
will
sleep
into
twelve
nine
I
guess
we
can
still
wait
to.
A
All
right
cool,
thank
you
for
that
sounds
like
there's,
not
a
lot
to
be
done
here.
You
might
want
to
consider
reassigning
those
reviews
if
you're
getting
like
I
won't
be
able
to
touch
it.
But
again,
there's
mentioned
it's
a
holiday
on
Monday
in
the
US
for
a
lot
of
people,
and
so
you
may
not
get
a
response
from
people
who
are
located
in
the
US.
So
just
keep
in
mind
and,
as
you
said,
it's
not
part
of
the
NBC.
So
it's
okay
I
think
it
was
long
a
bit.
You
know.
A
Obviously
we
don't
want
stuff
sitting
around
too
much
if
we
can
help,
but
so
cool
all
right,
I'm
going
to
stop
the
recording
now
hang
around
for
a
second
everyone
and
just
want
to
say
thank
you
for
everyone.
Who's
been
following
along
at
home
and
I
hope.
Everyone
enjoys
the
rest
of
their
day
and
their
weekend
and
thanks
again
for
everyone's
time.