►
From YouTube: GitLab 13.11 Kickoff - Release:Release
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
Hello,
my
name
is:
it's
again
bow
I'm
a
senior
technical
marketing
manager
here
at
gitlab
and
also
acting
as
a
pm
in
the
release
stage,
and
today
I
want
to
walk
you
through
some
of
the
features
we
are
planning
for
gitlab
13.11
release.
This
is
the
planning
issue
for
the
release
group
for
13.11..
You
can
find
this
issue
on
the
release.
Group
releases
issue
number
59
and
I
will
walk
you
through
some
of
the
highlights
issues
that
is
this
star
in
the
left.
A
I
will
start
from
a
present
a
lead
time
for
amount
to
deploy
to
production.
This
is
part
of
the
door
for
metrics
and
in
this
metrics
we
want
to
see
over
time
improvement
of
a
team,
and
I
will
show
you
the
design
that
we
are
working
on
and
what
we
measure
here
is
the
time
it
took
between
mr
was
ready
until
it
was
deployed
to
production,
not
including
coding
time.
This
includes
this
may
include
the
testing
manual
approvals
and
the
deploy
tasks.
A
Those
areas
represent
periods
when
there
is
no
data
or
no
deployments
to
present.
So
I
will
move
to
the
next
feature,
and
this
is
a
this
will
be
in
the
research
in
the
13.11.
We're
not
sure
we
will
be
able
to
deliver
it,
because
it's
going
to
be
a
big,
a
big
one.
We
will
create
a
group
level
protected
environment,
all
projects
under
a
group
that
has
a
protected
environment
set
in
the
group
level.
This
ui
will
be
disabled
for
them.
They
will
not
be
able
to
change
anything
and
all
of
the
product.
A
So
as
long
as
projects
under
this
group,
this
will
be
disabled
for
them.
But
if
project
removed
from
a
group,
the
project
level
settings
will
be
returned
and
they
will
and
they
will
be
able
to
use
that
the
next
feature
in
product
guidance
for
a
deployment.
A
release
in
cd
in
gitlab
is
another
job
in
the
pipeline.
A
Many
users
use
custom
ssl
certificate
in
their
private
network.
This
issue
will
help
self-managed
users
to
use
a
custom
certificate
and
use
the
release
cli.
Today,
the
release
cli
is
not
supported
the
custom
certificate.
So
only
if
you
have
a
public
certificate,
you
can
use
it.
So,
with
this
change,
we
will
add
a
new
parameter,
this
one,
that
that
will
allow
users
with
custom
certificate
to
use
the
the
cli
via
the
api
or
via
the
yaml
file.