►
From YouTube: Package Retro 7-12-19
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
Tim
I
believe
uh-huh
yeah.
My
first
one
is
a
little
embarrassing.
It's
really
the
first
issue
that
I
helped
collaborate
on
which
was
adding
a
confirmation
modal
for
when
you
delete
an
item
from
the
registry,
and
there
was
a
bug
that
came
up
with
it.
That
I
didn't
see
where
a
modal
pops
up
for
each
possible
item
that
that's
gonna
be
deleted.
Paul
from
the
security
team
jumped
on
it
right
away,
which
was
awesome,
but
the
copy
was
also
not
exactly
accurate.
C
So
today,
specifically
had
a
bunch
of
issues
writing
some
tests
that
I
thought
would
be
really
easy,
the
multi-select
stuff,
but
it
turned
out
to
be
a
lot
more
involved
than
I
was
anticipating,
and
unfortunately
this
meant
that
I
spent
longer
than
I
really
wanted
to
write
in
these
tests,
which
is
a
bit
of
shame.
But
I
have
got
them
now
done
and
they
are
working
so
I'd
say
that's
a
success,
even
though
it
was
a
little
bit
longer
than
anticipated
and
yeah.
C
Unfortunately,
I
haven't
had
much
time
to
look
into
the
issue
about
sorting
the
images
via
date
and
what
performance
implications
that
might
that
might
have,
and
that's
just
because
I
spent
so
long
today,
I
was
planning
on
doing
it
today,
but
I
spent
so
long
longer
than
I
expected
right
in
those
tests.
So
I
just
haven't
had
a
chance
to
really
dig
into
that.
I
would
say
that
what
I
have
had
a
look
at
I
mean
is
fairly
trivial
on
the
front
end
to
sort
sort.
C
D
So
I
got
stuck
for
a
little
while
on
some
refactoring
from
some
feedback
for
one
of
my
merge
requests
and
that
kind
of
just
kept
me
from
really
getting
into
one
of
the
other
issues
that
I
was
hoping
to
get
farther
on
this
week,
and
actually
it
was.
It
was
also
writing
tests
as
well
seems
that
the
tests
are
always
the
tricky
part
right.
D
Additionally,
at
some
point,
I
did
a
GDK
update
and
then
that
caused
some
errors
with
running
the
get
lab
the
rails
app
locally.
So
I
had
to
spend
some
time,
debugging
that
and
that
came
down
to
one
of
the
config
files
was
updated.
So
he
had
to
remove
the
one:
that's
not
in
git
and
then
reloaded
to
be
able
to
get
in
the
new
version.
D
One
other
thing
that
I
liked
just
notice
right
before
this
meeting,
which
is
not
good,
is
that
I
had
a
doc
update
in
a
merger
quest
on
the
C
II
that
relates
to
a
merge
request
on
the
II
project
and
the
doc
request,
got
merged
and
deployed,
but
the
EE
back-end
updates
have
not
yet
been
merged
and
deployed.
So
we
have
some
Doc's
that
are
on
the
website
that
are
not
actually
accurate.
So
that's
not
good
and
I
did
ask.
A
D
It
sounds
like
a
good
practices
if
you
have
a
merge
requests
in
each
project
that
you
need
to
go
out
together
when
you
assign
them
to
the
maintainer
z--,
make
a
note
to
whichever
one
you
think
is
probably
going
to
get
finished.
First,
make
a
note
to
that
maintainer
to
not
merge
it,
but
to
reassign
it
to
the
other
maintainer
in
order
to
make
sure
that
they
merge
them
both
the
same
time,
mm-hmm.
A
Yeah
cool
probably
worth
some
further
investigation
and
what
best
practices
there
are.
It
sounds
like
just
tagging
the
person
you
think
might
end
up
merging.
It
is
probably
a
little
hiddenness
but
yeah,
whether
there's
some
like
WI
quirk
in
progress
tag
or
something
but
I.
Don't
know
people
then
go
on
and
we
basically
do
everything
except
to
merge
it
until
it's
ready,
but
then
does
it
get
done
so
yeah.
It
sounds
like
we
need
to
look
at
this
mod
thanks
for
raising
that's
a
good
one.
They're
all
good
didn't
mean
to
suggest
otherwise.
A
We
have
an
issue
that
comes
in
that
we
need
to
address
because
it's
kind
of
important,
but
as
of
right
now
it
doesn't
look
like
that's
necessary
if
there's
a
architectural
review
channel
in
slack
or
I,
suppose
that
adding
with
Stan
who
and
Andrew
knew
to
gate
and
there's
some
a
lot
of
interesting
extra
stuff
that
I
haven't
seen.
So
if
anyone
has
questions
or
wants
to
see
that
then
go
look
at
that
channel,
it
was
tough,
though
sort
of
working
at
how
I
or
contribute
was
my
struggle.
A
I'm,
so
I
did
ask
around
and
sort
of
Nona
had
a
good
answers
for
me.
It's
I'm
struggling
a
bit
to
keep
a
track
of
moving
parts
information
which
is
a
similar
they
in
there
everything
was
going
on
because
it's
the
fire
hose
situation.
It's
really
hard
to
know
when
to
just
go
nope,
not
relevant,
because
sometimes
I,
look
at
that
stuff
and
I
dig
into
it
a
bit
know
like
oh
okay.
This
actually
is
important
or
this
is
relevant,
or
this
is
interesting,
but
not
relevant.
A
I
I
think
you
know
I'm
I'm
sort
of
passing
on
something
that
came
up
with
one
of
our
meetings.
There's
been
a
lack
of
a
bit
of
a
lack
of
clarity
on
expectations
for
the
engineering
team
on
dates,
as
well
as
the
cultural
impact
of
our
CD
efforts.
The
sort
of
kind
of
CD
that
we're
doing
right
now,
which
is
a
weekly
kind
of
thing,
is
not
really
CD
either
and
I
have
some
positive
comments
to
say
about
this
down
in
the
positive
section.
A
C
A
A
great
job
there
of
working
that
out
in
advance
trying
to
work
out
the
hiring
process
for
go
peeps
has
been
a
bit
of
a
struggle.
The
biggest
blocker
is
that
we,
our
hiring
process,
is
pretty
heavily
focused
around
rails
engineers.
So
if
you
don't
pass
a
rails
test,
you
don't
get
the
job,
but
if
you're
a
go
engineer
you
don't
really
do
you
need
to
pass
the
rails.
A
A
B
Embarrassing,
my
first
onesie
an
easy
one,
but
it's
great
having
Ian
and
Georgina
has
joined
the
team.
This
week
sounds
like
they're,
both
getting
up
to
speed
and
and
really
looking
forward
to
contributing,
and
then
I
mention.
Oh
I
mentioned
this
one
above
but
make
addressing
the
copy
and
and
the
multi-select
I
thought
was
awesome.
It's
super
helpful
having
the
the
gifts
and
the
short
videos
and
the
issues
demonstrating
the
functionality
was,
was
really
great
and
helpful.
B
Although
I
wish
there
was
a
way
to
pause
them
because
I
was
trying
to
read
the
copy
and
I
was
like
I
can't
read
it
fast
enough.
I
can't
head
edit
watch
it
like
seven
times
or
something
like
that
and
I
thought.
The
team
meeting
on
Tuesday
went
really
well.
I
thought
the
efferent
the
time
zone,
Daioh,
probably
like
six
times
this
week
and
I
thought
it
was
great
having
the
extra
structure
with
the
new
boards
that
Dan,
created
and
I
thought
just
going
through
and
doing.
B
The
grooming
session
of
some
open
issues
in
the
backlog
was
great
because
we
weren't
doing
anything
like
that
before
we
were
just
looking
at
issues
in
the
current
milestone,
so
it's
nice
to
feel
as
a
team,
though
we're
getting
a
little
bit
longer
view
of
not
only
what
we're
working
on,
but
what
we
will
work
on
in
the
futures.
I
thought
that
was,
that
was
really
cool.
B
C
That's
all
for
me,
okay,
say
for
me.
Then
I
managed
to
get
free
a
mastery
this
week,
a
couple
of
them
work.
What
pretty
small
like
like
it
wasn't
a
lot
to
them,
but
the
fact
that
they
got
through
and
they
were
all
merged
and
wasn't
any
issues
was
yeah.
I
was
really
shocked.
The
multi
deletion
of
container
images
work,
they
just
stay.
That
seems
to
work
locally,
soups
work
really
quite
well,
and
hopefully
that's
gonna
like
be
a
big
improvement
to
what
we've
got
there
already.
C
So
I'm
quite
excited
to
get
that
out
there
and
get
that
through,
although,
like
the
whole
time,
I
was
working
on
it,
I
was
thinking
about
just
the
design
at
that
table
and
and
how
we
can
that
better
and
I
did
have
to
resist
like
like
doing
that.
So
yes,
there
was
that
but
yeah
I'm
looking
forward
to
when
we
have
the
other
thing.
C
So
it
like
the
pagination
problems
and
the
performance
issues,
and
then
when
we
can
really
go
to
town
on
the
UI
and
just
make
it
really
nice,
some
really
important,
and
then
the
last
one
was
that
I
make
my
first
contribution
to
get
live.
Ui
with
an
Emma
and
I'm,
not
entirely
sure.
If
that's
gonna
go
through
just
yet,
but
it
it
was
nice
to
sort
propose
an
idea
and
that
actually
originated
from
one
of
my
earlier
Emma's
as
well.
C
When
we
were
discussing
a
particular
issue
that
could
have
been
sold
via
a
gitlab
UI
component,
but
then,
when
we
dived
into
it,
actually
that
gitlab
UI
component
couldn't
solve
it.
And
then
my
mr
is
to
change
that
component
to
allow
it
to
solve
that
problem
in
the
future.
So
that
was
quite
a
fun
and
sister,
a
nice
process
to
go
through
of
like
working
across
different
teams
and
basically,
where
an
issue
identified
on
one
side
has
made
it
back
and
made
the
action
base
product.
Better
basically
says
that
was
that's
cool
was.
C
Was
the
issue
that
kept
it
off
yeah,
but
it
was
the
actual
empty
state
component
itself
not
being
able
to
support
the
things
like
code,
snippets
or
or
links
within
the
descriptions
and
stuff
like
that,
so
I've
of
Kayla
NMR.
That
would
allow
that
component
to
support
those
things,
which
means
that
it
could
be
used
in
more
places
and
then,
like
you
more
uniformly
across
UI.
Basically.
D
This
week,
I
spent
some
time
reading
through
a
book
on
docker,
and
it
was
kind
of
like
a
book
that
went
into
some
of
the
more
like
details
of
how
things
work,
which
was
really
good,
so
feeling
a
bit
more
comfortable
with
the
concepts
that
we'll
be
needing
to
deal
with
mentally
in
the
registry,
but
certainly
still
need
to
get
more
comfortable,
just
like
using
docker
in
general,
because
it's
certainly
used
like
everywhere
and
that'll
be
worthwhile.
D
E
So
for
me,
I
Dan
created
the
CI
CD
social
channel,
which
I
think
is
a
really
cool
idea,
so
just
wanted
to
give
that
a
quick
shout
out.
I
also
have
a
similar
note
as
dan
about
the
team.
Doing
really
well
I
just
remove
that
and
+1
is
just
so.
We
didn't
have
any
duplicates
and
then
another
one
and
for
my
side
was
Tim.
Thank
you
so
much
for
prioritizing
and
kind
of
prepping
those
issues
for
Nick
really
quickly.
We
really
really
appreciate
that.
It's
just
wanted
to
call
that
out
over
to
Danny.
A
A
You,
sir
I
appreciate
that
and
I
just
as
John
mentioned
I'm,
just
like
really
stoked
and
have
like
productive
everyone's
thing,
and
you
know
Steve
and
make
both
like
just
doing
such
a
great
job.
So
really,
thank
you.
So
much
I've
also
had
some
really
good
productive
meetings
with
Tim
and
I
really
appreciate
Tim's,
hard
work
and
his
focus
on
the
product
needs,
and
and
and
also
on
an
on
a
focus
on
being
collaborative
and
thoughtful
about
what
you
do
Tim.
It's
super
appreciated.
It
makes
coming
to
work
a
lot
a
lot
better
for
me.
A
Thank
you,
I
think
to
go
back
to
the
Steven
make
killing
it.
You
know
having
a
team
where
everyone's
sort
of
working
really
hard
makes
me
want
to
work
really
hard,
which
has
some
negative
side
effects
of
working
too
much.
But
it's
also
that
feeling
of
like
well
we're
all
really
achieving,
and
it's
such
a
nice
place
to
be
uhm
to
be
in
a
team
with
people
who
are
really
working
on
whether
they
passionate
about
it.
So
thank
you
so
much
for
that.
A
A
Really
I
don't
know
yet
and
I
just
think.
I'm
gonna
be
ejected
from
the
matrix
at
some
point
and
some
other
conversations
we
would
like
some
of
my
peers,
Elliot
and
Gabby,
and
some
other
of
the
managers,
the
manager
lean
coffee
meetings
we
have
in
the
afternoon
where
we
could
just
sit
down
and
talk
about
things
have
been
awesome,
really
really
really
nice
for
me,
I'm
not
certainly
giving
me
a
lot
of
context
around
what
expectations
are
in
what
I'm
doing
so.
A
Those
meetings
have
been
very
helpful
and
I
certainly
encourage
everyone
else,
given
the
opportunity
to
meet
with
peers
and
sort
of
just
to
get
a
little
bit
more
context
about
around.
What's
going
on
it's,
it's
really
helpful
in
this
environment,
I'm
dab,
sort
of
slightly
more
close
connections,
but
yeah.
That's
it
for
me,.
A
E
D
It's
linked
to
the
initial
question
that
I
posed
in
slack
also
the
link
of
that
I
think
I
posted
in
the
development
channel
and
one
or
two
of
the
document,
documentation,
engineers
and
I.
Think
one
other
back-end,
engineer
and
kind
of
commented
on
what
they're
doing,
and
you
know
the
kind
of
the
direction
that
it's
taking
and
different
ways
that
we
might
be
able
to
look
at
it.
So
there's
a
conversation
going
hopefully
be
able
to
get
somewhere
with
it.
A
You,
but
let's,
let's
follow
up
on
that
sometime
soon,
I
want
to
it
feels
like
I,
don't
know
the
merge
strains
functionality
super
well
but
like
it
feels
like
that
is
exactly
what
it's
designed
to
handle
the
merges
that
are
dependent
on
other
merges
and
have
to
go
out
as
one
unit
and
perhaps
in
a
certain
order.
That
might
be
that's
their
release.
A
Teams
working
on
that
that's
Darby's
thing,
so
there
might
be
something
going
on
there,
so
it
might
be
worth
pinging
Diaby
about
that,
and
for
so
dad
is
awesome,
so
I'm
sure
he'd
be
more
than
happy
to
help
out
if
he
could.
So,
let's
follow
up
on
that.
Do
you
like
Monday?
Do
you
want
to
sort
of
follow
up
or
in
the
team
meeting,
just
sort
of
follow
up
on
what
we
got
to
with
that?
I.
Definitely
think
it's
worth
following
through.
F
B
What
about
we
talked
yesterday
a
little
bit
about?
When
do
we
know
something's
released
and
Steve?
You
just
sent
a
note
from
Nathan,
so
the
best
way
to
do
that
is
to
find
the
commit
Shaw
of
one
of
the
merge
requests
that
we
pushed
through
and
then
see
where
it
blab,
C
or
E
is
on
on
that
feels
like
we
could.
There's
gotta
be
a
better
way
for
knowing
quickly,
but
maybe
we
could
keep
following
up
on
that.
D
D
A
A
When
is
the
issue
status,
get
updated
as
the
merge
for
the
Emma's
get
version,
and
no
some
comment
I
think
it
was
you
that
made
it
Steve
around
there
being
potentially
multiple
Emma's
that
get
split
out
and
you're,
not
sure
if
and
then
related
and
like
I
get
that
there
are
education
there.
But
this
feels
like
something
that
we
should
care
about
as
well.
From
a
you
know,
product
functionality,
standpoint.
D
Now
so
I'm
guessing
that
if
something
gets
marriage
and
it
goes
through
the
QA
process-
it
like,
according
to
the
rules,
I
believe
it
should
go
out
with
whatever
that
next
rollout
is
so
that
is
one
way
to
know.
If
something
is
out,
is
that
if
you
see
a
merge,
request,
merge
and
an
issue
closed,
then
we
should
be
able
to
assume
that
it's
going
out
on
the
next
one,
but
that's.
E
F
E
E
Was
just
chatting
with
Nathan
real,
quick
on
merge,
trades,
I
wasn't
speaking
so
I
was
thinking
about
what
you
guys
are
talking
about.
What
you
all
were
talking
about,
yeah
I,
don't
believe
merge
rings
lets.
You
have
relationships
right
now
between
Mr
Nathan's
been
covering
the
front
end
for
that,
so
I
wanted
to
check
with
them
before
I
brought
it
up,
but
it
sounds
really
neat
I
feel
like
you
may
have
stumbled
on
a
really
neat
idea.
They're
saying
this,
mr
shouldn't
be
merged
before
this
Samar
is
merged.