►
From YouTube: GitLab 15.7 Kickoff - Release
Description
Planning Issue: https://gitlab.com/gitlab-org/ci-cd/release-group/release/-/issues/174
A
So
we're
going
to
talk
through
what
we're
planning
to
do
for
the
15
7
Milestone
and
some
themes
that
we're
working
on
for
the
Milestone
are
migrating
to
the
multiple
approval
rules
and
configuration
for
the
deploy
approval
experience.
A
The
next
one
is
API
enhancements
some
work
around
our
apis
and
making
them
work
for
multiple
use
cases,
and
then
some
maintenance
maintenance
worth
planned
as
well.
So
in
terms
of
deliverables.
A
We'll
walk
through
each
of
these
issues
listed
here,
so
the
first
three
Direction
issues
that
were
in
that
table
are
part
of
this
larger.
This
larger
epic
so
support
multiple
approval
roles
from
Project
level,
protected
environment,
settings
UI,
and
what
we're
doing
here
the
goal
is
right.
A
In
general,
you
can
have
separate
configurations
in
multiple
groups
for
who
gets
to
approve
a
deployment
and
versus
who
has
permission
to
actually
execute
a
deployment,
so
it's
more
flexible,
and
that
is
the
direction
that
we
want
to
move
all
of
our
customers
towards,
and
so
this
effort
these
next
three
issues
that
I'll
be
talking
through
will
be
adding
support
for
that
in
into
the
configurations,
because,
right
now
our
configuration
UI
supports
the
the
first
unified
approval
rules.
A
We
want
to
take
a
few
Milestones
essentially
migrate,
make
sure
everyone
is
aware
and
then
eventually
migrate,
all
of
our
customers
and
users
to
that
new
experience,
and
so
what
that
looks
like
specifically,
we
have
specific
iterations
to
handle
each
part
of
that
experience.
So
this
one
is
editing
the
sort
of
the
deployment
approval
rules.
The
next
one
is
talking
about
editing
the
deployment
executed
rules
and
then
the
next
one
here
is
making
sure
we
have
the
right,
alerting
and
messaging.
A
So
when
people
are
going
into
the
configuration
settings
and
updating
or
or
creating
their
to
play,
approval
rules,
they're
they're
notified
that
and
we're
doing
this
change
and
then
specifically,
that
unified
approval
rules
will
be
essentially
removed
from
the
UI
in
the
paper
of
the
multiple
approvals.
At
the
same
time,
those
rules
can
still
be
updated
as
needed
in
the
API,
so
we're
making
sure
that
users
have
a
path
to
be
able
to
do
that.
A
The
next
one
is
graphql
query
for
fetching
environment
deployment
permissions.
So
this
is
part
of
our
overall
effort
to
move
to
graphql,
to
power
a
lot
of
our
environments
and
index
and
details
Pages.
It's
more
performance,
it's
more
flexible,
and
so
this
iteration
is
doing
that
specifically
for
the
permissions
for
users.
A
One
of
the
reasons
again
is
going
back
to
we
know
this
page
is
really
heavily
used
and
has
grown
actually
a
lot
in
the
past
few
months,
which
is
really
exciting.
We
want
to
kind
of.
Can
you
continue
to
enable
to
scale
in
terms
of
actual
performance
of
the
page
and
then
also
in
terms
of
of
Dev
kind
of
velocity
from
that
standpoint
too?
So
we
want
to
take
some
time
here
to
to
do
that
conversion,
but
the
last
one
here
is
a
performance
related
issue.
A
Right
now
we
are
seeing
continue
to
monitor
this,
but
we
are
seeing
some
endpoints
and
queries
related
to
our
feature.
Flags
products
and
feature
kind
of
get
delayed
and
slow
and
effects
are
that
sometimes
it
affects
our
air
budget
and
then
we
want
to
make
sure
that
those
those
endpoints
are
reliable
and
make
sure
to
serve
up
the
necessary
information
for
that
feature.
A
So
those
are
the
major
features
for
p1s.
We
also
have
a
list
of
p2s
and
p3s
that
we'll
pull
in
as
we
complete
our
p1s
and
with
that
I'll
turn
it
over
to.
B
A
To
talk
about
design
and
user
research
work.
B
Sounds
good
I
will
just
share
my
screen,
I
believe
it's
this
one.
Well,
so
we've
quite
a
few
ux
issues
we're
working
on
this
Milestone,
starting
with
deployment
approval,
so
skipping
approvals
in
an
emergency.
This
is
just
the
flow
we
want
to
kind
of
design
around
if
there
is
an
emergency
and
an
operator
needs
to
kind
of
get
something
out
and
skip
the
approval
process,
that's
more
important.
How
is
that
going
to
look
so?
B
We've
had
a
customer
comment
on
this
one
as
well,
showing
some
urgency
so
looking
into
the
design
of
this.
B
We
also
want
to
do
the
third
iteration
of
this
promote
a
deployment,
epic,
we're
kind
of
working
on
right
now
around
improving
promoting
deployments
on
the
environment
index
page-
and
this
is
with
the
decision
to
revert
the
previous
to
the
previous,
promote
Behavior.
Now
users
lost
the
ability
to
promote
a
deployment
to
another
environment,
and
this
is
kind
of
rethinking
the
ux
and
giving
them
that
option
again.
B
The
third
one
we're
looking
at-
and
this
is
spanning
a
few
Milestones-
now-
is
AD
dynamically
populated
organizational
level
environments
page.
So
this
is
looking
at
giving
a
summary
of
all
deployments
or
all
environments
at
the
production
level
at
the
group
level.
So
users
can
really
see
a
summary
of
what's
going
on
their
environment,
Health
and
just
kind
of
have
a
higher
level
summary
where
they
don't
have
to
go
into
each
project
to
get
this
environment
information.
B
B
The
next
one
is
actually
a
issue
that
relates
to
the
usability
benchmarking
so
really
giving
users
feedback
that
they
have
successfully
created
a
release
right
now,
when
you
go
to
creative
release,
there's
not
really
any
feedback
that
you've
successfully
created
one
until
you
kind
of
check
and
it's
there.
So
this
is
just
rethinking
that
feedback
that
we
give
users
when
they've
completed
an
action,
and
then
we
have
a
few
research
issues.
The
next
one
is
finishing
off
the
category
maturity
scorecard
for
environment
management.
B
This
is
really
we've
kind
of
crafted.
Our
scenarios
we're
looking
to
do
our
interviews
and
summary
in
15,
7
and
finishing
this
up
to
see
if
we
can
move
environment
management
up
to
viable,
we
also
completed
the
design
for
the
deployment.
Oh,
this
is
not
the
right
one.
B
Sec
I
think
the
link
to
this
one
is
not
the
right
link,
but
we
have
an
issue
around
the
deployment
Details
page
and
just
validating
that
with
our
users
to
make
sure
they're
able
to
go
through
all
the
interactions
that
they
need
to
on
that
page
and
validating
that.
This
is
indeed
the
direction
we
want
to
go
forward
with
so
really
in
157.
B
We
want
to
validate
the
new
design
for
this
deployment
details,
slash
deployment
request
page
before
it
goes
into
production
and
the
last
one
is
just
a
support
role:
I'll
be
helping
configure
with
any
design
feedback.
They
might
need
for
this
ad
environment,
support
to
the
gitlab
agent,
so
I'll
be
helping
Ali
with
this
and
any
kind
of
questions
or
support.
He
needs
around
working
and
designing
in
the
environment
index
page.
A
The
added
the
link
for
the
deployment
detail
and
solution-
validation-
if
you
wanted
it,
but
I
think
we
spoke
through
it,
so
cool.
Thank
you
for
that
exciting
super
exciting
about
all
those
projects.
A
lot
of
them
are
huge
ones.
We've
been
thinking
about
talking
about
a
lot
for
a
while
for
environments.
A
The
integration
with
kubernetes
and
kind
of
the
cross-caged
shepherd
so
excited
that
we're
collaborating
with
with
our
our
partners
in
configure-
and
one
last
call
out
for
me,
is
that
we
we
did
ship
our
or
are
working
on
shipping
and
Improvement
to
our
environment
search
capability
to
make
it
more
useful.
There
are
some
kind
of
performance
and
scalability
concerns,
so
one
thing
that
we
might
pull
in
for
15-7.
A
We
were
discussing
with
the
team
this
morning,
there's
a
potential
areas
to
help
help
with
that
type
of
scalability
and
monitoring
that
the
scale
of
usage
so
and
if,
if
so,
we'll
pull
those
into
the
plan
throughout
the
milestone.