►
From YouTube: GitLab 15.4 Kickoff - Release
Description
Planning issue: https://gitlab.com/gitlab-org/ci-cd/release-group/release/-/issues/153
A
All
right,
hey
everyone:
this
is
the
release.
15.4
planning
issue,
I'm
chris
bolland
senior
product
manager
for
release,
I'm
here
with
emily
bauman
product
design
and
release.
So
let
me
go
ahead
and
share
my
screen.
The
theme
for
this
milestone
is
working
on
our
environments,
functionality
and
with
a
quite
a
few
enhancements,
and
so
what
that
looks
like
in
terms
of
deliverables
and
p1
issues,
the
first
one
is
search
for
environment
name
and
the
environmental
review
page.
I'm
really
excited
about
this
one.
A
It's
quite
a
popular
issue
and
we've
had
it
in
the
backlog
for
a
while,
but
we're
really
able
to
tackle
it
now,
and
so
the
idea
is,
we
can
now
for
those
of
you
that
have
many
environments,
that
you're
managing
you'll
be
able
to
use
search
functionality
to
more
easily
find
find
those
specific
environments
and
navigate
to
those
as
well,
so
we'll
be
adding
a
search
bar
to
the
environments
page.
It
looks
something
like
this
and
then
you'll
be
able
to
easily
navigate
to
whatever
you're
searching
for
the
next
next
issue.
A
We're
working
on
is
keep
expanded
state
for
details
in
the
environments
page.
So
through
milestones,
you
might
remember,
we
did
a
redesign
and
updated
the
ui
for
the
environments
page.
We
did
get
some
great
feedback
about
how
to
make
this
even
more
useful.
So
this
iteration,
as
you
can
see
here
right
now,
we
have
the
show
details
page
our
show
details
button.
A
Let's
you
see
a
bit
more
information
for
this
deployment,
we'll
actually
be
making
that
the
default
state
and
making
sure
you
can
easily
see
all
of
the
all
the
information
as
part
of
your
deployment
more
easily.
So
you
don't
have
to
do
that.
Extra
click
and
the
next
one
is
create
api
endpoint
to
update
a
protected
environment.
A
So
we
want
to
make
it
more
easy
and
just
configurable
for
settings
for
the
protected
environment,
so
we'll
be
creating
this
new
endpoint
able
to
use
this
put
endpoints
and
configure
those
protective
environments
that
might
be
using
for
special
environments
like
production
or
staging
okay.
A
The
next
one
is
show
tags
related
to
deployed,
commit
on
environment
page.
One
of
the
things
we've
been
thinking
about
in
one
of
our
one
of
our
goals
is
to
more
more
easily
connect
all
the
different
parts
of
our
of
our
features
in
the
release
stage
with
other
functionalities
in
gitlab.
So
this
is
one
of
those.
This
is
an
example
of
one
of
those.
A
So
now
what
we,
what
we'll
do
here
is
show
when
you're
looking
at
deployments
and
environments
page
we'll
also
show
you
any
related
commits
that
are
sorry,
any
related
tags
that
are
related
to
that
commit
that's
actually
deployed
on
that
environment.
So,
and
this
will,
let
you
easily
see
what's
deployed
it
helps
you
know
exactly
what
what
tag,
what
commit,
what
version
that
that's
actually
deployed
to
your
environments?
A
A
The
next
one
is
support.
Variable
expansion
in
the
environment
auto
stop
in
keyword
so
right
now
it
takes
a
literal
string
for
a
time
period.
So,
like
one
hour
one
day,
this
is
really
useful
for
managing
and
just
stopping
those
environments
automatically.
We
want
to
enable
you
to
use
variables
for
that.
So
we're
going
to
add
this
add
support
for
variables
here.
A
And
then
the
last
one
we'll
talk
about
today
is
a
bug
that
we've
we've
seen
users
face
recently,
and
so
we've
reopened
up
this
issue
from
a
bit
ago,
just
to
make
sure
that
we're
providing
release
evidence
when
you're
creating
release
by
the
ui.
So
we'll
get
this
taken
care
of
and
those
are
the
p1
issues
for
the
milestone.
A
We
also
have
p2s
and
p3s,
as
you
can
see
here,
as
we
get
through
the
milestone
and
complete
our
p1's
more
detail
in
this
planning
issue
in
each
of
these
individuals,
individual
issues
here
and
with
that,
I'm
going
to
pass
it
over
to
emily
and
she'll
talk
about
the
design
work
for
the
milestone.
B
Awesome
so
I'll
just
share
my
screen.
C
It's
this
one,
so
I'll
go
over
some
of
the
design
and
ux
research
issues
we're
going
to
be
tackling
this
milestone.
The
first
is
kind
of
a
group
related
to
multiple
approval
rules,
so
the
first
one
we're
going
to
do
is
support
multiple
approval
rules
in
project
level,
protected
environment
cy.
C
Currently
we
are
only
supporting
the
unified
access
here,
so
this
issue
is
going
to
be
around
what
the
ui
looks
like
when
we're
supporting
both
unified
access
and
multiple
approval
rules,
and
with
that
we'll
also
want
to
show
support
multiple
approval
rules
in
the
deployment
approval
ui.
C
So
this
one
will
be
when
you
do
enable
the
multiple
approval
rules
you'll
be
able
to
see
who
has
to
approve
in
the
deployment
ui,
who
has
approved
and
just
a
bit
more
details
about
that
approval
process
versus
currently
what
we
show
is
just
approvals:
zero
out
of
one
so
just
giving
users
a
bit
more
detail
into
that,
and
then
the
third
one
around
this
is
showing
multiple
deployment
approval
comments
in
the
multiple
approval
rules
are
configured,
so
this
one
is
really
in
that
comment.
C
C
So
the
next
one
is
a
solution.
Validation
issue
around
validating
that
users
want
to
be
notified
about
pending
approvals
using
to
do's,
so
I'll,
be
spending
a
bit
of
time.
Flushing
out
this
solution,
validation
issue,
but
the
main
purpose
of
it
is
to
kind
of
go
into
the
informed
users
of
pending
deployment
approvals
using
to
do's
making
sure
that's
kind
of
a
way.
They
expect
to
be
informed
and
a
way
we
want
to
go
forward
with
that
and
then
the
two
smaller
issues,
this
milestone
for
design
are
create
annotated
tags
with
release.
C
Ui,
currently
annotated
tags
can
only
be
created
using
the
tags
creation
which
we
want
to
bring
this
into
the
release
ui
and
then
the
final
one
is
add,
form
validation
when
required.
Approvals
exceed
number
of
users
allowed
to
approve.
So
this
is
in
the
in
protected
environment
settings
page
as
well.
It's
just
giving
users
a
bit
more
context
if
they
selected
too
many
approvals
for
the
amount
of
approvers
in
that
group.
Just
letting
them
know
that
and
yeah.
C
A
You
emily
excited
to
see
all
that
great
design
we're
coming
up,
so
I
also
just
wanted
to
mention
we
do
have
our.
We
have
a
docs
planning
session
section
in
our
planning
issue.
We've
highlighted
one
issue
where
we'll
partner
with
russell
on
just
making
sure
some
of
our
error
messages
are,
are
easy
to
understand
and
useful
for
for
our
users,
so
we'll
we'll
be
partnering
with
russell
in
that
this
milestone.
A
Okay,
so
with
that,
that's
that's
our
milestone
for
fifteen
four,
you
have
any
questions,
please
feel
free
to
reach
out.
Thank
you.