►
From YouTube: 2023-01-11 AMA about GitLab releases
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
A
We
send
a
reminder
yesterday
on
what's
happening
on
gitlab
channel.
We
have
two
very
interesting
issues
about
the
delivery
era
review
and
they
also
deployment
metrics
that
we
have
so
in
case.
You
are
curious
about
that
or
you
have
some
questions
about
that.
Please
feel
free
to
look
in
the
agenda
and
we
have
the
two
links
there.
A
B
Okay
last
question:
with
the
2020
metrics
review,
when
you
reviewed
the
yearly
metrics,
was
there
anything
that
like
was
surprising
either
good
or
bad
foreign.
A
Trend
on
the
DB
immigration
blockers
shown
over
time,
but
this
is
something
that
is
not
really,
it
doesn't
give
me,
it
doesn't
ring
a
straight
Bell
and
I
can
say:
okay,
I
can
pinpoint
to
something
and
so
on,
but
if
it's
something
you
probably
would
like
to
dig
a
bit
more
into
that
is
that
mainly
because
of
the
trend
that
is
actually
you
know
Uprising
and
it's
not
something
that
is
fully
is
fully
random.
C
Yeah
I
think
it
was
interesting.
I
think
it
was
certainly
interesting
to
see
the
patterns
of
of
things
like
I,
think
I
think
my
surprise
was
often
you're
very,
very
close
to
the
individual
details.
So
you
know,
oh
I,
know
I
click
retry
on
this
job,
all
the
time
or
all
those
sorts
of
things.
So
I
suppose
my
surprise
was
just
simply
that
actually
Gathering
the
data
and
being
able
to
pull
it
into
blocker
by
type
over
the
year
to
actually
show
things
that
I
some
things
that
I
I
didn't
realize.
C
C
I
actually
felt
my
sort
of
personal
feeling
was
I
was
expecting
flaky
tests
to
contribute
more,
but
actually
we
can
see
they've
really
dropped
down
over
the
year.
So
that's
a
great
sign.
Yeah
I
know
there
are
still
some
flaky
tests,
but
I
think
that's
a
really
like
it
was
a
really
nice
sort
of
trending
down
and
I.
Think
the
other
one
was
not
a
surprise,
but
I
was
pleased
to
see,
because
it's
something
which
I
have
suspected
and
believed
will
be
a
bigger
thing
for
next
year
is
change.
C
Requests
so
I
think
we
have
more
sres
working
across
infrastructure.
We're
seeing
more
project-based
things
coming
out.
Almost
all
of
that
work
is
is
implemented
with
change
requests
which
have
to
block
deployments
so
I
have
I
have
suspected
that
this
is
going
to
become
an
increasing
sort
of
an
increasing
blocker,
but
there's
also
manual
work
that
goes
around
coordinating
it.
A
A
So
there
are
no
more
questions.
We
can
conclude
a
call
here,
but
please
I
invite
you
to
to
give
it
a
look,
maybe
to
the
two
issues
that
are
linked
in
the
agenda:
they're,
actually
pretty
interesting
and
actually
showing
like
from
a
very
high
level
the
impact
that
we
had
not
only
like
in
the
effort
that
we
worked
on,
but
also
likely
in
numbers,
I.
A
Think
it's
going
to
be
extremely
helpful
for
everybody
that
if
you
have
any
any
feedback,
also
around
or
any
questions
around
all
the
points
that
were
bringing
up
on
those
situations.
We
can
continue.
The
conversation
also
I
think
there
or
you
can
always
like
engine
delivery,
the
entire
team-
and
we
are
happy
to
provide
any
extra
Insight
that
you
might
want
to
have
on
on
this
or
if
you
have
any
other
ideas,
how
we
can
improve
anything
around
the
releases
and
deployments.
D
The
all
of
the
I
was
just
looking
at
the
what's
coming
up
in
2023
section
in
the
2022
in
numbers
issue,
all
of
those
sound
great
I'm,
particularly
interested
in
that
first
one
where
you're
talking
about
release
managers
and
we're.
We
have
been
improving
mttp,
but
it
comes
as
a
at
a
cost.
So
that
I
think
that's
great
that
we're.
You
know
we're.
Actually
you
know
beyond
the
metric,
we're
also
thinking
about
the
people
behind
the
metric
and
how
what
it
takes
to
lower
that
metric,
essentially
yeah.
A
Yeah
is
a
great
question,
so
in
in
general,
police
management
is
one
of
the
main
duties
of
the
delivery
group.
So
it's
we
have
some
releases
that
have
been
like
smoother
and
other
releases.
It
a
bit
less
move.
There
are
a
lot
of
things
that
are
contributing
to
today.
Let's,
let's
call
this
stress
level,
or
at
least
pressure
level
on
this
kind
of
releases
that
it
could
be
like
I
know,
failures
that
we
have
on
any
part
of
the
or
the
pipelines
or
any
part
of
the
infrastructure
that
can
be.
A
Okay
can
cause
the
blockers
and
when
maybe
we
are
like
not
able
to
deploy
new
changes,
or
maybe
we
have
to
delay
a
release
because
of
one
of
those
reasons.
All
these
are
definitely
are
engaging
for
release
manager,
so
release
manager
needs
to
be
present,
needs
to
be
working
directly
within
both
parts
and
stakeholders,
and
this
is
taking
probably
you
know
at
all
on
the
daily
work
awareness
manager,
because
it's
actually
highly
engaging
and
keeping
a
timely
manner
in
a
timely
manner.
A
A
So
the
actual
there
is
an
issue
linked
to
the
to
the
section
that
you
are
speaking
about
is
how
to
figure
out
a
metric
that
you
can
use
to
measure
the
current
release
management
like
tires
stress
level
engagement
I
mean
we
can
see
it
from
different
perspective
and
how
we
establish
a
vessel,
a
baseline.
That
is
probably
the
most
important
thing
right
now
and
can
see
how
we
can
improve
the
Baseline,
maybe
tackling
like
individual
factors
that
are
coming
coming
into
play,
but
we're
still
working
into
that.
A
If
you
have
any
ideas
how
to
do
that,
we're
still
still
work
in
progress
that
because
the
teachers
went
so,
please
feel
free
to
contribute
to
that.
But
it's
something
that
we
really
need
to
focus
on
not
only
to
improve
the
process,
but
also
improve
the
experience
of
a
risk
manager
and
that,
while
keeping
the
same
level
of
performance
or
even
better
performance
that
we
had,
we
had
so
far.
A
Well,
if
not,
we
can
complete
the
codes
again.
The
links
are
there,
epic
receive
any
feedback
on
those
and
I
hope.
You
had
a
great
start
of
2023
and
to
see
you
again
very
soon.