►
From YouTube: GitLab 13.10 Kickoff - Stage:Release
A
This
is
the
13-10
planning
issue.
You
can
find
this
issue
under
release
warp
release,
issue
number
57
and
I
will
jump
to
the
first
issue.
Currently,
we
don't
have
a
way
to
explicitly
define
the
production
type
if
it's
production
or
a
staging
or
different
environment.
We
assume
that
if
it's
a
if
the
name
of
the
environment
is
production,
this
is
production
environment,
but
in
some
cases
users
can
define
their
production
as
other
names
like
in
this
example,
they
defined
it
as
a
gprd
and
then
we're
in
gitlab.
A
We
cannot
identify,
which
is
the
production,
and
this
is
important
for
us
to
know,
which
is
the
production
for
our
for
some
of
our
features.
For
example,
indoor
4
metrics
we
target
for
now
only
for
the
production.
The
solution
for
that
is
to
define
new
keyword
called
the
environment
type
and
we
can
explicitly
define
if
it's
production,
staging
testing,
development,
etc,
etc.
The
next
issue
create
a
release
from
existing
tag
on
the
new
new
release
page.
A
So
today
you
can
create
a
release
only
when
you're
creating
a
new
tag,
but
we
want
to
add
more
flexibility
to
release
managers
to
create
releases
from
existing
tags.
So
let
me
show
you
the
new
ui
that
we
are
proposing,
so
we
will
be
able
to
create
a
new
tag
or
a
search
for
a
specific
tag,
and
from
that
we
will
be
able
to
create
a
release.
A
The
next
feature-
log,
autostop
environment,
actions,
the
problem
to
solve
here
we
don't
have
a
way
today
to
know
when
environment
stopped
with
the
auto
stop
environment
and
why
this
is
important
thing
that,
for
example,
you
get
your
build
from
your
cloud
provider,
and
you
know
you
want
to
check
it.
But
when
you
don't
have
the
information
when
the
environment
stops,
it
will
be
hard
to
check.
So
the
proposed
solution
is
to
add
this
information:
the
action,
the
target
environment
and
timestamp
to
the
audit
log.
The
next
feature
in
the
mr
widget.
A
You
are
able
to
see
all
of
the
deployed
environments,
but
sometimes
you
have
long
list
of
environment.
Let
me
show
you
an
example:
this
is
very
long
list
of
environment
in
the
mr
and
when
this
is
so
long
list,
it
is
hard
to
see
the
other
content
in
the
mr
page,
so
we
will
have
a
way
to
collapse
or
expand
the
environments.
A
The
next
issue
is
related
to
aws
deployment.
Today,
users
that
deploy
with
gitlab
to
aws
having
hard
time
to
know
what
is
the
aws
results
result
of
that
deployment?
Then
we
need
to
go
to
context
switch
to
another
application
to
aws
console
make
some
other
clicks
and
it's
not
always
so
user
friendly.
We
want
a
way
that
saves
time
to
the
user
and
they
have
all
of
the
information
in
gitlab.
So
in
this
issue
we
will
have
the
deployment
success
log
in
the
job
log
itself,
the
next
issue.
A
So
we
have
a
way
to
define
the
deploy
freeze
period,
but
we
don't
have
a
way
to
remove
some
periods
that
we
defined.
So
we
will
have
a
new
button
for
removing
this
deploy
free.
The
next
three
issues
are
a
plan
for
design.
Today,
if
you
have
manual
action,
someone
with
the
right
permissions,
you
can
go
and
click
here
to
start
the
action,
but
we
don't
have
any
more
information
about
why
you
prove
that
or
there
is
no
way
to
reject
that.
A
So
what
we
are
proposing
to
announce
this
capability
to
have
a
button
approve,
reject
a
way
to
create
a
way
to
add
a
approval
message
or
reject
message,
of
course,
and
also
all
of
this
information
will
be
available
in
the
audit
log
for
auditing
as
well
as
we
will
add,
a
new
job
status
rejected
in
case
user
rejected
the
code.
The
next
issue
automatically
create
a
release,
notes,
form
and
dated
tags.
A
Today
we
have
the
release,
notes,
information
in
the
data
tags,
but
in
order
to
create
a
release,
notes
from
that,
the
user
will
need
to
go
to
the
the
tag
and
copy
it
into
the
release,
notes
all
manually
created,
but
we
want
to
make
the
user
lives
easier.
So
what
we
are
offering
is
a
new
chat
box
use,
annotated
tag
and
if
the
user
click
this
check
box,
this
will
wait
for
it.
This
will
create
for
him
and
release
notes
automatically.
A
This
issue
is
in
product
guidance
for
auto
rollback.
We
want
to
encourage
users
to
use
the
automatic
rollback,
so
we
will
have
in
the
alert
page
when
the
there
is
any.
When
there
is
an
incident,
we
will
have
a
direct
link
to
the
auto
rollback
configuration
settings.
This
is
all
of
what
I
have
for
today.
I'm
sure
it's
going
to
be
another
amazing
release
for
the
release
group.
Thank
you
for
watching
our
planning
for
today.