►
From YouTube: 2023-02-02 Container Registry Weekly Retrospective
Description
The Container Registry group has weekly retrospectives to discuss what went well and what was not that good.
Check out the "Who We Are" section of our handbook page: https://about.gitlab.com/handbook/engineering/development/ops/package/container-registry/#who-we-are to learn more about us.
A
So
hello,
everyone
Welcome
to
our
continue
registry
weekly
retrospective
today
is
February,
2nd
and
we're
going
to
start
with
what
we
know
so
well
and
how
we
can
do
it
better
and
I'm,
assuming
I'm
going
to
read
for
the
people
here
they
had
it
their
own,
but
I
think
it's
important
for
us
to
have
it
so
Jaime
mentioned
that
has
been
struggling
with
concentrated
for
long
periods
of
time.
It's
taking
longer
breaks
to
so.
If,
if
he's
blocking
someone,
please
paint
them
directly
and
the
next
one
is
Rahul.
A
Our
LCP
for
package
racing
container
registry
went
down
in
the
past
15
days.
There
is
an
open
discussion.
This
is
not
happening.
Just
to
our
patients
is
happening
too.
Oh
he'd
laugh.
So
there
is
the
discussion
in
there.
If
you
want
to
follow
up
on
that
next
one
we
have
ADI
the
web.
Free
notification
issue
is
bigger
than
is
it
thought
it
got
more
complex,
adding
weekly
and
multimetric
definitions
deploy
tokens
users.
So
it's
taking
a
little
bit
more
in
the
milestone
on
the
bright
side,
she's
learning
and
discovering
a
lot
on
it.
A
Yeah,
that's
a
container
registry
foreign
for
me,
I've
been
since
Monday,
trying
to
figure
out
okay
hours
and
it's
been
quite
difficult.
Our
new
tools
don't
allow
me
to
filter
by
parents,
normally
I
need
to
align
to
what
is
coming
from
engineering.
What
is
coming
from
development
and
yeah
kind
of
hard.
B
Yeah
so
recovering
from
sickness
this
week,
I
felt
like
it
took
me
twice
as
long
to
do
just
basic
stuff,
regular
stuff,
like
catching
up,
for
example,
so
but
I'm
getting
actually
slowly
getting
back
to
full
speed.
B
B
A
For
me,
I'm,
very,
very
thankful
for
the
transparency,
honesty
and
the
truth
that
everyone
put
in
me.
I
really
really
enjoyed
the
one-on-ones
this
week.
It
was
very
insightful
and
also
I
was
missing
all
so.
It
was
really
nice
to
have
all
the
one
on
Wednesday's
week,
Joelle.
B
So
it
felt
great
to
finally
close
the
loop
on
the
database
index
codes,
production
incidents
with
a
major
bolt
production
and
also
document
the
findings
and
the
instructions
for
the
next
occurrence.
Because
we
lost
a
lot
of
time
trying
to
find
out
all
the
Bluetooth
calculated
and
where
the
Met
was
coming
from.
Until
we
finally
found
the
roots.
And
then
it
was
all
easier
on
too
early.
C
Yeah,
so
working
on
the
Toyota
has
been
a
lot
of
fun
and
it
just
feels
like
a
a
little
project
like
when
I
first
started
learning
new
code.
It's
not.
F
A
I
want
to
like
animal
part
of
those
discussions,
but
I
I'm
back
from
PTO,
and
it
was
impressively
amazing
to
see
all
the
issues,
investigations
and
epics
everyone
jumping
and
sharing
ideas
and
proposing
how
to
do
things
like
I
can
put
a
comparison
with
other
teams
and
we
do
like
amazingly
or
how
we
collaborate
they
see
like.
We
can
be
an
example
on
how
we
can
do
those
technical
conversations.
I
think
it
is.
A
It
is
awesome,
so
I'm
glad
that
everybody
engaged
and
provide
ideas
and
don't
feel
worry
to
challenge
others
about
how
to
do
things.
That
is
great.
A
Good
anything
else
that
you
want
to
add
well,
thank
you
for
sharing
and
I
hope.
You
have
a
nice
rest
of
your
life.