►
From YouTube: GitLab 15.0 Kickoff - Release
Description
Release 15.0 Planning Issue: https://gitlab.com/gitlab-org/ci-cd/release-group/release/-/issues/114
A
A
But
one
improvement
we
want
to
make
is
to
allow
that
approval
to
happen
within
the
detailed,
the
environment
detail
view
or
also
known
as
the
deployments
page.
So
this
is
another
page
that
can
be
accessed
from
the
environments
page
where
users
might
look
for
or
look
at
a
specific
environment
like
production,
for
example.
So
we
also
want
to
make
sure
they're
able
to
do
this
quickly
and
easily
from
from
that
productive
production.
Specific
view,
the
next
one
again
continuing
on
our
deployment
approval
direction.
A
I'm
really
excited
about
this
one
so
that
we
can
help
even
better
integrate
integrate
these
notifications
right
into
gitlab
and
the
idea
the
goal
here
is
to
make
make
again
make
those
really
efficient
and
really
decrease.
You
know
the
deployment
execution
to
the
deployment
approval
times,
and
so
that's
something
we'll
be
we'll
be
monitoring
as
well
and
seeing
how
this
this
impacts
that
okay,
the
next
one,
I'm
also
really
excited
about
this.
A
A
lot
of
customers
are
actually
sort
of
trying
to
do
this
already
with
jobs,
post-deployment
jobs
or
or
just
reusing.
Some
of
the
other
keywords
that
we
have
like
prepare
so
now
what
we
want
to
do
is
establish
an
actual
keyword
that
more
matches
the
sort
of
the
semantics
and
the
actions
that
they're
trying
to
do,
and
so
initially
this
will
look
pretty
similar
to
what
the
prepare
keyword
does
today.
A
But
I'm
excited
about
potential
future
directions
to
build
up
on
top
of
this
mvc,
which
pizza,
which
would
be
to
potentially
output
the
the
results
from
these
types
of
checks,
build
a
whole
new
sort
of
monitoring,
page
and
so
on,
and
so
because
of
this,
this
is
also
an
mvc
for
our
new
continuous
verification
category.
That
our
monitor
stage
is
this
building
out,
seeing
so
excited
to
collaborate
on
that.
A
Okay
and
then
the
next
one
here
sort
of
related
to
a
customer
issue
that
we've
experienced
recently,
and
what
we
want
to
do
here
is
extend
the
model
for
in
for
inheritance,
allowing
allowing
group
level
protected
environments
to
take
inherited
membership
into
account
so
rather
than
what
we
have
today
is
we
have
direct
users
can
be
specified.
We
also
want
to
allow
inherited
members
and
give
give
customers
the
option
to
do
one
versus
the
other.
A
A
The
next
one
is
allowing
skips
to
created
state
transitions
in
deployment
jobs,
so
this
is
actually
a
bug
and
it's
success.
Related
user
experience
related
as
well.
It's
sort
of
breaking
some
existing
workflows,
because
some
of
the
state
transitions
aren't
behaving
the
way
as
expected.
So
we
want
to
resolve
this
and
allow
this.
This
transition
to
occur.
A
The
next
one
another
related
sus-related
ux,
bug
and
improvement
that
we
want
to
make
so
right
now
we
we
fail
and
silently
when
environments
are
trying
to
be
updated,
but
the,
but
the
the
name
or
the
url
might
be
invalid.
This
makes
it
difficult
to
debug
this
particular
issue,
which
happens
pretty
pretty
frequently.
B
The
first
item
for
15.0
for
for
design
is
actually
the
research
for
the
solution,
the
validation
for
the
environments,
page
redesign,
that's
an
item.
I
talked
about
last
time
so
in
in
the
previous
milestone.
We
were
setting
up
the
the
study,
and
now
we
started
interviewing
people.
So
during
the
interviewing
phase,
our
goal
is
to
validate
what
we
have
today
in
production
and
then
based
on
the
insights,
make
the
appropriate
updates
and
recommendations
for
the
design,
the
interaction
and
also
usability
of
the
environments.
B
Page,
that's
gonna
influence
a
lot
of
our
items
during
this
year.
So
it's
a
very
it's
a
very
exciting
validation
to
be
tackling
now
and
second,
is
the
show
the
deployment
approval
comment
in
the
ui
so
also
related
to
deployment
approvals.
We
want
to
give
our
users
the
ability
to
see
the
comments
that
others
left
right
when
approving
or
rejecting
the
manual
deployment
for
a
protected
environment.
So
this
will
help
to
provide
more
context
to
the
approvers
or
the
people
that
are
managing
the
process
on
understanding.
B
This
is
also
going
to
be
interesting
and
useful
for
organizations
with
the
in
highly
regulated
industries,
because
we'll
be
able
to
collect
information
for
audit
purposes
right
for
the
release.
Events
and
then
the
next
item
is
automatically
create
release,
notes
from
annotated
tags.
So
andrew
our
frontend
engineer
started
working
on
this
in
1410.
B
He
actually
actually
has
a
merge
request
open
for
that,
but,
as
we
were
iterating
on
it,
we
came
up
with
some
ux
proposals
and
improvement
for
this
issue.
So
during
this
milestone,
I'm
going
to
be
pretty
much
documenting
those
decisions
and,
following
up
with
any
other
design
improvements
for
that
that
issue,
this
should
pretty
much.
Allow
will
allow
users
to
add
annotated,
tags,
information
to
the
release,
notes
by
default
or
automatically
right.
B
So
you
have
the
option
for
people
that
want
to
use
their
annotated
text
as
release
notes
to
do
that
from
the
release
page
right
from
while
creating
a
new
release
item,
so
we
are
working
on
the
embassy
and
then
breaking
it
down
as
we
go.
So
that's
the
the
related
to
release
orchestration.
That's
what
I
wanted
to
say.
Yeah
then!
B
So
that's
useful
for
release
managers
for
platform
engineers
that
would
like
to
see
the
status
of
this
multi-project
application
in
cross-production
environments
and
it
will
be
able
to
show
the
latest
changes
in
one
place,
help
them
understand
everything
that
has
been
applied
to
users
from
a
single
point
right,
so
we'll
be
framing
the
mvc
for
that
during
the
15-0
and
also
breaking
down
the
proposal
for
the
next
iterations.
So
that's
the
ux
scope
for
15.
A
Awesome
thanks
hayanna.
We
also
included
some
docs
work
and
technical
writing
work.
We've
gotten
some
feedback
from
customers
and
users
about
creating
a
release,
and
just
just
here's
a
kind
of
a
good
iteration
to
make
on
our
documentation
to
make
sure
we
help
our
users
understand
how
this
feature
works.