►
From YouTube: GitLab 15.5 Kickoff - Release
Description
Planning issue: https://gitlab.com/gitlab-org/ci-cd/release-group/release/-/issues/158
A
A
The
product
manager
for
the
release
stage
here
at
gilab.
This
is
the
release,
15.5
planning
issue
and
we're
going
to
walk
through
the
goals
and
themes
for
the
Milestone,
the
key
deliverables
and
then
I'll
pass
it
over
async
to
Emily
to
discuss
all
the
design
work
that
we're
going
to
be
working
on
this
Milestone
as
well
all
right
so
in
terms
of
themes
and
goals
of
the
milestone.
A
We
are
making
more
improvements
on
the
environments
page
and
functionality.
That's
that
are
on
those
pages.
We
will
also
be
doing
quite
a
few
updates
and
enhancements
for
our
releases
future
and
functionality,
and
another
highlight
is
that
we're
we're
doing
a
tech
evaluation
for
the
environments
in
git
lab
agent
integration
which
I'm
really
excited
about,
and
so
this
is
what
that
looks
like
in
terms
of
deliverables
across
P1,
P2
and
P3
priorities
and
I'll
go
ahead
and
dive
into
a
little
bit
more
detail
for
the
p1s.
A
So
the
first
one
is
show
tags
related
to
deployed,
commit
on
environment,
detail
page.
This
is
another
iteration
for
something
that
we've
completed
recently
and
so
now,
with
this
update,
you'll
be
able
to
see
the
related
tags
that
are
associated
with
those
commits
that
are
deployed
onto
specific
environments
and
we'll
be
showing
this
in
the
environment's
detail.
Page
show
that
re-environment
has
its
own
page
specific
to
that
environment,
and
you
can
see
all
the
deployments
for
that
environment.
A
A
Is
create
annotated
tags
with
releases
UI,
so
this
is
another.
This
is
the
last
iteration
for
one
of
the
major
epics
we've
been
working
on,
the
Epic
was
create
annotating
tags
and
green
release.
If
you've
done
a
lot
of
the
API
work
and
back-end
work
essentially
build
the
foundation
for
this,
and
now
we're
finally
completing
it
in
the
UI,
and
so
now,
when
you're,
creating
a
new
tag.
A
All
right.
Sorry,
when
you're
creating
a
new
release
in
the
UI,
you
have
the
option
of
also
creating
annotated
tag
and
annotated
tag
being
a
tag
that
also
has
a
tag
message
to
include
information
context
about.
What's
in
that
specific
tag,
so
now
you
can
easily
do
this
in
the
UI.
It's
a
highly
requested
feature
and
I'm
excited
to
be
delivering
on
this
one
foreign.
A
Will
finally
ship
this
is
published
releases
without
giving
access
to
source
code.
So
today
a
lot
of
workarounds
are
are
done
to
be
able
to
essentially
accomplish
this.
But
now
we
want
to
give
you
the
ability
to
do
this
natively
within
us
within
one
project
to
publish
a
release
but
not
actually
giving
access
to
the
source
code
sort
of
decoupling.
A
A
A
And
the
last
one
that
we'll
talk
about
today
is
update,
graphql
API,
to
support
environment,
detail
page,
and
so
we've
been
over
time.
Upgrading
and
migrating.
Our
apis
use
graphql
as
a
sort
of
standard
for
for
our
front
end
in
terms
of
retrieving
data,
and
so
this
one
specifically
is
updating
that
for
the
environment,
which
we
are
also
working
on.
A
B
Hi
everyone,
my
name-
is
Emily
and
I'm
the
product
designer
on
release
and
I'm,
going
to
go
over
the
15.5
Milestone
plan
for
ux.
So
we
have
quite
a
few
ux
issues
for
15.5,
including
some
research
issues
and
some
onboarding
issues
that
are
helping
go
into
our
okr
around
onboarding
users
into
release,
so
I
can
go
through
the
plan
very
quickly,
so
the
two
first
issues
are
really
around
onboarding.
B
We
wanted
to
figure
out
something
basic
that
we
could
really
improve
to
help
new
users
on
board
into
release
and
the
first
one
is
improve
our
empty
State
Pages
for
deployment.
So
this
hits
the
feature
flag,
empty,
State
releases,
empty
State
and
environments.
Md
State,
there's
a
few
reasons
why
we
want
to
do
this.
First
of
all,
we
do
have
a
template
for
empty
States
now,
which
none
of
these
pages
are
following.
So
just
updating
these
empty
states
to
be
the
one
in
pajamas
is
kind
of
the
first
thing.
B
The
second
is
the
ctas
are
up
in
the
right
corner.
We
could
add
a
bit
more
contextual
information
to
help
new
users
understand
and
just
have
the
ctas
in
a
more
expected
place
for
our
empty
states,
which
is
right
underneath
that
text
so
excited
for
this
one
and
getting
started
on
with
onboarding
projects
for
release.
B
So
there's
a
two
reasons
why
we
want
to
go
ahead
with
this.
The
first
problem
is
available.
The
empty
environments
are
useless,
so
this
is
mostly
in
the
review
up
cases
where
user
doesn't
deploy
to
a
created
environment.
At
all.
Most
of
these
don't
have
a
deployment,
so
we
need
a
way
to
stop
them.
The
second
one
is
there
is
no
one.
Click
stop
stop
available,
but
still
environments
at
once.
So
this
is
so.
B
The
next
two
are
around
informing
users
of
pending
deployment
approvals,
so
this
these
two
issues
are
actually
going
to
work
out
of
each
other,
so
the
first
one
is
the
actual
issue
for
the
design
of
how
we
inform
users
of
pending
deployment
approvals.
But
the
second
one
is
the
solution.
Validation
around
validating
that
users
are
okay,
being
pen
notified
of
pending
deployment
approvals
with
to-do's
So,
based
on
what
comes
out
of
this
research.
B
B
A
B
Not
just
project
bubble,
but
seeing
them
across
their
groups,
so
this
is
a
fairly
big
effort.
We
still
need
to
break
it
down
a
little
bit
understand
what
NVC
for
this
is
going
to
look
like
in
1505,
but
I
do
know.
This
one
has
been
on
the
backlog
for
a
while
as
well
and
the
final
one
we
want
to
get
started,
and
this
one
also
goes
into
an
okr.
Is
the
category
maturity
scorecard
for
release
environment
management?
B
So
this
is
really
just
doing
that
research
to
understand
the
maturity
score
for
environment
management.
This
one
may
span
a
little
bit
into
15
6,
depending
on
kind
of
our
recruitment
effort
for
users,
but
yeah.
This
one
really
excited
for
as
well
and
yeah
that
kind
of
ends
off
the
ux
portion
of
the
55
Milestone
kickoff.
Thanks
for
watching.