►
From YouTube: GitLab 15.9 Kickoff - Release
Description
Planning issue: https://gitlab.com/gitlab-org/ci-cd/release-group/release/-/issues/203
A
Hi
everyone,
my
name-
is
Chris
I'm,
a
product
manager
for
the
release
stage
I'm
here
with
Emily
product
designer
for
the
release
stage,
and
so
this
is
the
release.
15.9,
planning,
issue
goals
and
themes
for
the
Milestone
are
usability
improvements
from
a
recent
Benchmark
study
that
we
did
to
improve
our
the
usability
of
our
workflows
and
finishing,
deploy
approval
configuration
migration,
so
I'll
go
into
a
little
bit
more
detail
on
that
and
then
some
specific
issues
that
we're
taking
on
this
milestone.
A
So
quite
a
few
deliverables
across
the
different
priorities.
You'll
just
notice
in
the
P1
list,
quite
a
few
issues,
but
a
lot
of
them
are
carryovers.
Actually,
so
we've
made
a
lot
of
progress
on
those
and
we're
planning
to
wrap
those
up
this
Milestone
and
then
quite
a
few
new
ones
as
well
for
the
Milestone.
So
I
won't
go
over
all
of
these,
but
I'll
touch
on
just
kind
of
the
major
features
that
we're
planning
to
work
on
and
a
lot
of
them.
A
The
ones
that
were
carrying
over
I
won't
go
over
it
because
we've
discussed
them
already
in
the
in
the
previous
call
all
right.
So
the
first
first
of
the
three
P1
usability
issues
that
we're
taking
on
this
is
give
users
more
feedback
when
they
have
successfully
created
release.
So
one
of
the
major
pieces
of
feedback
and
findings
that
we
found
during
The
Benchmark
study
is
that
users
were
a
little
confused
in
terms
of
making
sure
that
they've
actually
created
a
new
release
as
part
of
the
creative
release
workflow.
A
We
want
to
make
this.
We
want
to
improve
this
and
give
them
more,
essentially
more
feedback
and
kind
of
positive
feedback
in
terms
of
creating
the
release
successfully.
So
we're
hoping
to
complete
this
soon
next
one
is
provide
a
way
to
easily
navigate
to
the
protected
environment,
setting
through
the
environments
page.
So
this
one
is.
A
It
came
up
again
also
in
the
Benchmark
study,
and
what
we
found
is
that
today,
if
you
we're
looking
at
an
environment,
that's
protected
it's
a
little
difficult
to
connect
or
to
even
know
how
to
actually
protect
it
or
change
settings
about
the
protected
status,
including
adding
approopers
or
setting
up
deploy
approvals.
So
we
want
to
make
this
a
lot
clearer
for
our
users,
so
they,
if
they're
in
environments,
they
can
kind
of
get
help
and
easily
be
able
to
navigate
to
the
right
page.
A
And
so
what
that
looks
like
for
NPC
is
now
in
the
edit
environment
page,
which
is
an
action
that
they
can
click
from
an
environment.
We'll
have
this
message
that
says
protective
to
protect
this
environment.
You
can
visit
the
protected
environment
section
within
the
cicd
settings,
so
MVC
changed
to
at
least
to
surface
this
and
to
help
them
navigate
over
to
that
page
right.
So
the
next
one
is
allow
Json
evidence,
collection
files
to
open
up
within
a
separate
tab,
it'll
be
used
as
web
browser.
A
So
we
found
this
again
from
The
Benchmark
study
and
users
were
surprised
when
they
clicked
the
link
or
the
release,
evidence
that
it
actually
downloaded
the
file
opened
it
up
in
another
application.
So
we
want
to
change
the
behavior,
make
it
something
a
little
bit
more
intuitive
and
in
which
case,
or
in
this
case
I
actually
had
the
link
open
up
in
a
new
tab
and
then
display
it.
So
something.
B
A
Little
bit
more
intuitive
and
kind
of
natural,
and
so
they
won't
be
surprised
by
some
of
this.
This
download
as
it
as
it
currently
paves
today,
all
right.
So
the
next
one
is
rename
file
path,
parameter
and
release
rest
API,
so
minor
updates
to
our
release.
Api
we're
changing
simply
changing
the
name
from
the
field
name
from
file
path
to
direct
asset
path,
something
just
a
little
bit
more
clear
to
understand
and
consistent
with
some
of
our
other
apis
and
how
file
paths
and
asset
paths
are
referred
to.
A
Okay,
next
one
is
download,
install
gitlab
release
binary
by
by
a
private
homebrews
app.
So
really,
this
is
a
use
case.
Super
interesting,
where
a
lot
of
our
customers
and
users
are
essentially
downloading
the
release
binaries
that
are
published
as
part
of
a
release
and
incorporating
into
whether
it's
another
workflow
or
a
an
easy
integration
with
Homebrew,
just
as
part
of
like
a
a
more
beyond
the
release,
workflow,
and
so
what
we
want
to
do
here
is
actually
enable
an
authentication
right
now
it
it.
A
If
you
try
to
do
or
navigate
to
an
the
private
projects,
release
binary,
URL
it'll,
actually
redirect
you
to
a
login.
We
want
to
be
able
to
support
actually
authentication
for
this.
For
this
resource
right.
The
next
one
is
improved
logging
around
Resource
Group
acquisition,
so
we
haven't
really
been
working
on
resource
groups
too
much
in
the
past
few
Milestones,
but
one
change
that
we
can
make
pretty
quickly
and
to
help
all
of
you
that
use
resource
groups
today
has
improved
the
logging
and
so
a
lot
oftentimes.
A
We
hear
questions
about
what
resource
or
project
or
pipeline
is
actually
taking
up
the
resource
Group.
Just
even
adding
some
belonging
information
about
when,
when
a
group
is
acquired,
it's
a
sister
failure,
exceptions
and
so
on.
We
want
to
log
that
to
be
able
to
help
you
debug
those
Resource
Group
issues.
A
Right
and
the
last
one
is
some
work
around
validating
the
environment,
tier
field
and
and
all
of
the
environments
that
are
existing
today.
We're
just
doing
this
because
we
want
to
make
sure
this
tier
field
is
populated
because
it's
actually
a
key
part
of
enabling
environments
and
being
able
to
visualize
deployments
so
we're
doing
some
back-end
and
maintenance
work
to
be
able
to
make
sure
the
migration
is
completed
and
that
those
that
that
field
is
is
populated
throughout
all
of
the
environments
that
exist.
A
Okay.
So
that's
a
quick
summary
of
the
highlights
of
the
issues
for
engineering
that
we're
working
on,
so
you
can
check
out
more
p1s,
and
then
we
have
quite
a
few
ptus
and
p3s
also
just
note
that
two
additional
usability
issues
are
scheduled
for
P2
and
we're
hoping
to
make
as
much
progress
towards
that
okr
as
possible.
B
B
B
The
next
two
are
related
into
the
benchmarking
study.
This
first,
one
being
creating
a
new
tag,
is
not
clear
on
the
new
release.
Page
we've
had
some
feedback
about
this
for
quite
some
time.
We
also
partially
worked
on
this
a
little
while
back,
but
we're
waiting
on
a
new
component
to
finalize
it
up.
So
looking
to
complete
this
usability,
one
in
59
as
well.
B
Another
benchmarking
study
we
want
to
handle
is
linked
to
environments
from
Project
home.
Oh,
this
is
an
onboarding
one,
so
link
to
environments
from
Project
home
empty
state.
So
this
is,
if
you
don't
have
any
environments
seeing
if
we
can
take
advantage
of
the
project
home
to
kind
of
encourage
you
to
set
up
environments
through
some
sort
of
entry
point
there.
So
this
will
be
an
onboarding
experiment.
We
test
out
in
that
milestone.
B
B
The
other
stretch
issue
we
have
that
is
related
to
the
benchmarking
is
allow
users
to
preview
the
release,
evidence
Json
file
displayed
from
the
release
page.
So,
like
Chris
mentioned,
we
have
one
where
it
opens
up
in
a
new
tab.
This
one
is
being
able
to
preview
it
directly
on
this
page,
so
this
is
kind
of
a
next
iteration.
Of
that
previous
benchmarking.