►
From YouTube: 2023-02-08 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).
C
A
B
D
And
show
you
a
few
more
seconds
and
let
a
few
other
people
join.
D
Okay,
I
will
go
ahead
and
get
started
for
a
time,
so
welcome
everyone.
This
is
our
February
8th,
2023
delivery
group
Ama.
So
we
are
here
any
questions.
Anyone
has
about
how
things
get
deployed
to
github.com
or
how
things
get
released
to
our
self-managed
users
and
mechanic.
You
have
the
first
question.
E
D
Yes,
that's
a
great
question
so
so
this
is
going
to
just
pull
the
link
so
mttp
our
our
mean
time
to
production
metric
which
I've
just
linked
into
the
question.
There
gives
us
a
good
way
of
tracking
how
long
it
is
taking
for
a
change
for
that.
You
know,
emerge
change
to
land
on
the
production
environments,
but
it
doesn't
cover
everything
that
we
work
on.
D
So
deployments
is
only
one
part
of
delivery,
so
hopefully
we'll
be
able
to
expand
that
out,
certainly
on
the
plans
to
expand
that
out
this
year,
so
that
we
can
actually
find
a
way
to
track
a
similar
sort
of
firm
performance
metric
that
will
go
around
our
releases
to
self-managed
users.
But
then
the
other
big
piece
is
around
understanding.
Mttp,
so
often
mttp
will
will
vary,
and
that
is
caused
by
the
different
things
that
affect
deployments.
D
So
it
could
be
that
we
may
have
more
incidents
causing
delays
to
deployments
or
it
could
be
that
our
deployment
pipeline
is
running
slower
or
you
know
we
didn't
have
a
release
manager
available
in
a
certain
time
zone.
There's
lots
of
different
factors
that
we
don't
yet
have
a
good
way
of
digging
into
those,
but
that
is
coming
and
I.
Think
someone
from
system
should
give
us
a
bit
of
an
overview
into
the
the
work.
That's
been
going
on
to
actually
understand
deployment
pipelines
to
give
us
a
better
story
about
mttp.
E
I
can
do
it
myself,
sure
for
sure
I
mean
we
are
actually
looking
at
mtdb
from
different
perspectives,
as
Amy
said
so
right
now
we
are
these,
like
big
number,
that
was
measured
in
the
entire
pipeline
end
to
end,
and
we
actually
built
all
these
capabilities
in
the
previous
quarter
as
part
of
our
okrs
to
increase
the
observability
capability.
We
have
in
our
deployment
pipelines,
so
we
have
client
actually
to
go
to
a
higher
level
granularity
there
and
be
able
to
use
that
to
see.
E
If
we
have
like
bottlenecks
that
maybe
are
in
a
particular
part
of
the
pipelines
only
where
we
actually,
we
can
go
there
and
improve
right
because
so
far
we
didn't
have
this
high
level
of
visibility
there.
So
it
was
difficult
to
tackle
which
kind
of
improvement
we
could
do
overall,
because
we
cannot
understand
which
factors
cause
which
impact
right
and
I'm
quite
sure,
that's
everywhere.
E
There
is
a
lot
that
is
80
20,
you
know,
operator,
rule
somewhere,
I'm
quite
sure
that
we're
going
to
find
these
patterns
as
well
there
and
yeah,
hopefully
with
the
new
tracing
capability
that
we
are
trying
to
develop.
We
are
going
to
be
able
to
to
understand
that
and
at
the
same
time,
with
the
new
metrics
collection
understanding
how
we
can
measure
the
effort
in
the
entire
deployment
pipeline,
we
are
trying
to
understand,
which
are
the
actions
that
are
actually
taking
the
most
time.
The
most
effort,
also
from
those
Risk
Managers
itself
themselves.
D
C
F
I
just
want
to
say
hi
to
everyone:
I
am
the
managing
editor
of
the
gitlab
blog
and
I
we're
making
an
effort.
This
I
don't
know
this
coming
quarter
and
onward
to
invite
everybody
to
contribute
to
the
blog
from
their
spheres.
Around
gitlab
and
one
of
the
things
I
wanted
to
talk
to
you
folks
about
is
we're
doing
how
gitlab
uses
gitlab,
how
how
we
build
gitlab
using
gitlab
series.
F
The
name
is
still
under
construction,
but
you
get
the
gist
and
I
wanted
to
invite
anybody
here
who
thinks
that
they
have
an
idea
that
would
fall
under
that.
So
what
we're
using
ourselves
to
help
you
know
that
will
eventually
help
customers
or
already
is
helping
customers
or
how
we're
doing
it
would
help
customers
so
any
of
those
categories
or
if
you're,
just
doing
something
that
you
think
would
be
interesting
for
our
audience.
I'm
always
willing
to
listen,
and
you
can
use
our
template
to
do
a
pitch
and
it's
just
blog
template.
F
If
you
go
in
issues
so
I'm
happy
to
talk
to
anyone
at
any
time
about
your
ideas,
you
can
slack
me
too.
It
doesn't
have
to
be
that
formal
and
looking
forward
to
getting
contributions
from
anyone
who
hasn't
contributed
yet
so.
Thank
you.
D
Awesome
thanks
so
much
Sandra
welcome
and
should
the
old
contributions
just
go
in
that
template?
Is
that
the
yes.
F
Or
or
if
you
want
to
feel
it
out
to
see
like
somebody
just
consulted
with
me
on
an
idea
and
we
weren't
quite
sure
if
it
would
fit
the
blog
or
not
wanted
to
do
a
little
more
sussing
out
so
before
you
do
a
lot
of
work
on
it.
If
you
want
to
talk
to
me
first,
you
can
slack
me
and
I'm
open
to
have
a
huddle
or
via
slack
or,
however,
you
want
to
do
it.
D
Oh,
so
I
wanted
to
just
ask
Myra
I
name
you
at
dri
I
know
that
we're
doing
lots
of
work
at
the
moment
in
delivery
in
preparation
for
the
maintenance
policy
extension.
Could
you
give
us
a
bit
of
an
overview
of
what
changes
we
might
be
able
to
expect
from
that
project?.
G
Yeah
for
sure,
thanks
for
asking,
so
we
are
working
towards
extending
the
maintenance
policy
and
just
for
context.
Currently,
the
maintenance
policy
right
now
allow
us
to
backboard
bug
fixes
to
the
current
stable
version
and
to
back
for
security
fixes
to
the
last
three
versions
with
the
extension
of
the
maintenance
policy.
What
we
want
to
achieve
is
to
allow
two
backboard
block
fixes
to
the
last
three
versions,
so
we
are
going
to
follow
the
similar
model
for
security
fixes
and
for
bug
fixes.
G
Now
what
this
impact
is
also,
how
well,
as
a
consequence
I
was
doing.
This
is
that
we
are
going
to
open
stable
branches
for
developers
towards
to
allowing
them
to
merge
work
fixes
at
wheel,
and
this
is
one
of
our
first
changes
towards
self-serve
model.
G
So
we're
excited
about
that
and
also
impacts
backward
requests,
because
we
commonly
receive
a
lot
of
backup
requires
for
previous
versions,
and
there
is
a
lot
of
friction
between
the
backup
requests
that
at
the
outer
developer,
requests
at
release
managers,
because
once
our
request
is
open,
release
managers
normally
ask
like
hey.
We
need
to
be
convinced
this,
but
progress
is
actually
necessary
and
then
there
is
a
lot
of
back
and
forth.
So
one
of
the
consequences
of
us
also
extending
the
maintenance
policy
is
to
remove
the
friction
of
these
backwards
requests.
B
D
Nice
thanks
for
sharing
and
there
will
be
a
lot
more
announcements,
so
we
are
currently
sort
of
considering
timelines
for
this,
but
most
likely
we
will
try
and
Link
the
sort
of
the
public
usage
of
the
extended
maintenance
policy
with
the
16.0
Milestone.
So
we'll
be
sharing
a
lot
more
about
rollouts
and
things
coming
up
internally
and
externally
in
the
next
few
months.
D
Oh
Jamie,
do
you
want
to
verbalize.
C
Yes,
so
I
wanted
to
introduce
myself
as
the
Evangelist
program
manager
and
I
oversee
the
Global
Meetup
program
in
the
heroes.
Evangel
advocacy
program
here
at
gitlab
I
have
two
things
that
I'm
getting
ready
to
work
on
and
I
feel
like.
This
is
the
great
audience
to
kind
of
connect
with
in
regards
to
trying
to
build
some
code
challenges,
so
we
could
get
an
uptick
in
contributors,
so
I
dropped
the
issue
here.
C
It's
something
that
we
currently
do
at
conferences,
but
we're
trying
to
create
something
that
there
might
be
projects
out
there.
That
can
use
some
contributions
from
the
community
and
they
would
run
maybe
every
quarter.
So
if
you
have
topics
or
ideas,
this
issue
is
a
great
place
to
drop
those
and
then
I'm
thinking
about
doing
the
Meetup
Campaign,
which
is
like
a
meet
up
in
a
box
and
I
would
like
to
align
those
with
the
releases
or
different
features
that
are
coming
out.
C
So
if
y'all
have
ideas,
you
can
slack
me
and
then
we
can
start
building
on
the
next
campaign
for
the
quarter.
So
I
felt
like
this
is
the
perfect
place
to
drop
those
gems
that
we
have
these
things
going
and
I
think
we
could
build
some
great
Partnerships
yesterday.
We
just
did
a
Meetup.
Matt
was
actually
there
and
it
was
is
about
by
ma'am
and
it
was
get
labs
developers
perspective,
which
was
really
nice
and
we
recorded
it.
C
So
those
are
different
ways:
we're
partnering
with
different
folks
within
gitlab
to
do
talks
on
different
features
and
whatnot.
So
just
wanted
to
drop
that
here.
Okay,.
D
When
you
say
we
recently
learned,
I
mean
it's
not
so
much
that
we've
been
keeping
this
a
secret
from
your
scalback,
but
Sam
joined
us
last
week.
So
it's
great
new,
but
it
is
on
the
cool,
hey
Sam.
Do
you
want
to
give
us
a
a
little
intro
to
yourself
as
well.
A
Hey
yeah
I'm,
Sam
I
started
last
week,
so
this
is
fun
and
based
in
the
UK
I.
Think
one
of
the
first
things
we're
looking
at
is
that
back
pop
process
and
extension
of
the
maintenance
policy,
so
giving
a
bit
more
ownership
to
our
stage
teams
to
fix
and
own
their
own
changes
and
not
kind
of
wait
for
us
to
get
through.
Some
of
that.
So
that's
going
to
be
exciting
over
the
next
three
months.
A
Whilst
we,
you
know,
look
at
doing
that
for
the
upcoming
major
release
and
put
the
Power
kind
of
back
in
the
stage
team's
hands
beyond
that
week
too.
So
I've
got
some
of
the
short-term
plan
and
I'll
have
an
update,
probably
the
next
time
we
do.
This.
D
Just
add
a
little
color
to
that
as
well.
I
think
some
of
the
things
which
Sam
will
be
able
to
take
over
or
do
a
much
better
job
of
are
the
sort
of
things
that
I
certainly
am
filling
in
some
of
those
in
delivery
already.
So
it
will
be
things,
for
example,
like
helping
us
figure
out
a
better
plan
for
doing
more
dog
feeding.
So
we
already
do
do
some
dog
fooding,
but
what
we
don't
have
a
great
plan
for
is
actually
how
do
we?
D
How
do
we
bring
the
delivery
process?
It's
a
little
bit
closer
to
the
product
and
having
Sam
be
able
to
actually
connect
us
with
other
product
managers
will
hopefully
make
that
much
easier.
We
also
have
quite
a
lot
of
ideas
in
delivery.
We
have
quite
a
long
backlog.
We
certainly
have
a
lot
of
trouble,
keeping
our
okrs
down
to
a
manageable
number
and
sort
of
picking
the
right
things
to
work
on.
D
So
it's
something
I'm
very
excited
to
have
Sam's
help
on
is
actually
how
we
figure
out
how
to
put
these
things
in
place
so
that
within
the
teams,
but
also
for
people
outside
of
our
teams,
we're
able
to
actually
rank
the
most
important
things
prioritize
the
most
important
things
and
help
other
people
to
you
know
to
fit
in
with
that
process
as
well.
So
I
think
there's
quite
a
lot
of
those
sort
of
changes
that
will
be
really
really
helpful
for
us
in
delivery.
D
No
okay,
in
which
case
thanks
so
much
everyone
thanks
for
joining
thanks
for
the
questions
and
have
a
great
rest
of
your
Wednesday.
Thank
you.
Bye.