►
From YouTube: GitLab 15.1 Kickoff - Release
Description
Release 15.1 Planning Issue: https://gitlab.com/gitlab-org/ci-cd/release-group/release/-/issues/131
A
B
A
Product
designer
for
the
release
stage,
so
we'll
review
what
we
have
planned
for
15.1
I'll
start
with
the
goals
for
the
milestone.
The
broad
theme
is
customer
issues.
We've
had
a
lot
of
great
feedback
and
some
requests
in
terms
of
features
for
for
many
of
our
categories.
A
We'd
like
to
start
addressing
some
of
those
in
this
milestone,
so
more
details
on
those.
When
we
go
into
the
issues,
I'm
really
excited
about
tackling
those
as
well
and
then
also
instrumentation.
We've
been
doing
a
lot
more
pi,
nlpi,
anal
analysis
for
our
stage,
and
now
that
we've
also
launched
a
few
features
that
we've
discussed
in
the
past
few
milestones,
we'd
like
to
add
instrumentation,
to
better
understand
how
our
customers
and
users
are
using
those
those
great
new
features
and
where
we
can
make
improvements.
A
Okay,
so
in
terms
of
deliverables
for
engineering,
this
milestone,
we
have
a
good
set
of
lists.
It's
a
good
set
of
issues,
let's
go
into
them,
so
the
first
one
is
create
annotated
tags
with
releases
api.
So
today
what
we
can
do
is
create
releases
right
from
your
ci
jobs.
This
iteration
enhances
that
capability
by
allowing
people
to
allow
users
and
organizations
to
specify
an
annotated
message
for
that
tag
as
part
of
the
release
api.
A
So
this
will
again
allow
users
to
add
additional
info
and
context
for
tags
that
will
also
be
incorporated
into
releases.
A
The
next
one
is
something
pretty
similar:
it's
it's
adding
the
same
sort
of
message
to
the
graphql
release
api
so
again
adding
that
functionality
to
make
sure
we're
consistent
across
our
apis.
A
The
next
issue
here
is
non-members
of
a
project
can
subscribe
to
new
release
notifications,
but
they
will
not
be
sent
to
them.
So
this
is.
This
is
a
bug
currently
in
our
system.
It's
also
a
usability
related
issue,
so
we
want
to
make
sure
we
handle
this
properly
right.
Now,
users
can
check
that
checkbox
in
terms
of
getting
these
notifications,
but
we're
not
actually
sending
them.
So
obviously,
we
want
to
make
sure
that
that
behavior
remains
consistent
and
we
the
system.
A
Then
the
notifications
behave
the
way
users
are
expecting
it
to
behave
all
right.
The
next
two,
as
I
mentioned,
are
instrumentation
related
and
so
we've
released
our
mvc
in
a
few
iterations
of
our
deployment
approval
feature.
Now
we
want
to
make
sure
we're
instrumenting
that
properly
we
get
a
good,
accurate
count
of
the
number
of
approvals,
and
so
we
can
track
adoption
over
time.
A
The
next
one
related
to
that
is
counting
the
number
of
environments
that
are
actually
leveraging
that
deployment
approval
capability.
So
again,
we
want
to
monitor
adoption
usage
usage
patterns
and
and
figure
out
areas
where
we
can
improve
that
capability.
A
Okay,
the
next
one,
this
one
is
one
of
the
customer
issues,
customary
requests
that
I
mentioned
earlier,
and
so
this
is
deploy
keys
api
and
what
we're
trying
to
solve
here
is
allow
that
extend
the
endpoint
to
for
the
user
to
retrieve
all
the
available
deploy
keys
that
they
have
access
to
so
right
now,
it's
not
very
clear
that
they're
not
able
to
do
this
themselves
in
a
self-service
way,
and
rather
they
they
have
to
kind
of
reach
out
and
contact
the
administrator
for
these.
A
For
these
keys,
we
want
to
allow
that
that
workflow
and
process
to
be
a
little
bit
more
streamlined
on
self-service.
A
Okay,
the
next
one
here,
another
customer
issue,
but
also
really
important
for
for
the
environment,
work,
environment,
management,
work
that
we've
been
doing
the
past
few
milestones.
A
This
one
here
is
log,
auto,
stop
environment
actions,
and
so
we
have
capabilities
to
help
users
manage
all
of
the
environments
they
might
have
and
be
creating
as
part
of
their
development
and
deployment
process.
A
Every
we
do
have
capabilities
for
gitlab
to
help
automatically
stop
those,
and
we
want
to
make
sure
that
that
action
is
audited
properly
for
future
auditing,
future
compliance
reviews
and
so
on.
So
we
want
to
capture
those
those
actions.
A
Okay,
that's
it
in
terms
of
highlights
for
the
engineering
work
we're
playing
in
1501,
I'm
going
to
now
pass
it
over
to
hyanna
for
the
design
work
that
we'll
be.
B
Doing
right,
we
are
wrapping
up
the
solution,
validation,
study
for
the
environment,
page
that
we
talked
about
last
kickoff
video.
So
far,
we
had
five
sessions
with
different
users,
different
customers
from
small
to
medium
to
large
size
organization,
and
we
learned
from
these
interviews
that
users
find
it
difficult
to
find
at
a
glance,
information
related
to
their
environments
and
deployments
on
the
environment's
page
overview
right.
What
we
wanted
to
validate
was
the
usability,
but
also
gather
some
insights
about
what's
important
to
them.
B
On
that
view,
just
as
a
quick
summary
participants
found
that
the
process
of
setting
up
the
deployments
and
environments
is
difficult,
but
once
that's
done,
it's
just
a
click
right,
but
and
at
the
same
time,
mostly
due
to
the
amount
of
setup
required
behind
the
scenes
and
the
challenges
with
maintainability
of
their
environment
and
deployments.
B
So,
for
example,
what
pipeline
or
what
job
is
related
to
a
specific
environmental
deployment
who
approved
it
when
what
was
the
state
and
be
able
to
navigate
from
the
environments
view
to
other
places
or
the
pages
of
ci
cd
capability
right
so
in
51
I'll,
be
working
on
making
some
recommendations
based
on
the
learnings
from
these
interviews
and
work
on
the
overall
experience
of
the
page,
so
that
we
can
better
integrate
environments
with
ci
and
cd
features
and
then
improve
the
overall
visibility
of
environments.
B
So
this
is
a
research
issue
is
confidential.
That's
why
we
are
not
sharing
on
screen,
but
you
can
see
here
a
related
issue
about
the
redesign
of
the
environments,
detail
page
and
then
next
up.
It's
also
a
research
issue
that
is
confidential.
B
We
are
working
on
a
benchmarking
for
release
as
a
better
way
to
understand
and
address
some
of
the
user
feedback
we
receive
via
sus
of
your
surveys
and
will
the
ux
researcher
that
works
with
our
team
will
conduct
a
usability
benchmarking
study
to
identify
specific
usability
issues
within
areas
of
git
labs
that
are
connected
to
the
release
stage
and
then
turn
that
into
granular
recommendations.
So
again,
linking
back
the
findings
with
the
work
that
we
are
doing,
that
we
are
planning
for
this
year.
B
So
chris
and
I
in
the
in
the
coming
weeks,
are
going
to
help
will
determine
what
tasks
we
want
to
cover
with
the
study
the
participants
want
to
recruit
and
the
data
that
we
want
to
collect
and
now
to
okay,
our
alignment.
So
that's
the
the
last
two
links
you
see
on
page
this
quarter,
we
start
working
on
the
sus
and
okrs
recommendations
for
for
release.
B
We
have
been
preparing
already
some
of
the
design
issues
and
our
goal
is
to
have
them
ready
for
development
in
q2,
so
that
crits
can
prioritize
and
our
team
can
build
and
this
improvement
into
production.
So
those
are
s2.
Self-Impacting
issues
for
release
there
are
some
of
them
already
scheduled
for
implementation
in
15,
00,
51
and
52.
So
super
exciting
updates
coming
up
in
the
coming
milestones
next
up
for
me
is
the
show
deployment
approval
comment
in
the
ui.
B
This
is
a
a
problem
also
related
to
the
environment
management
that
we
want
to
surface
comments
left
by
users
when
revealing
or
approving
a
deployment
right
now
you
can
add,
approve
or
reject
the
deployment.
Add
a
comment,
but
then
that
comment
is
not
displayed
in
ui,
it's
logged
in
the
api,
and
we
want
to
surface
that
for
the
non-technical
users,
but
also
that
this
information
is
available
for
audit
release.
Events
next
is
group
level
ui
for
protected
environment
settings.
B
There's
lots
of
cool
problem
that
we
want
to
solve
for
large
enterprise
organizations
right
that
have
to
set
specific
permissions
for
their
users
or
and
roles
and
users
in
their
groups,
so
that
that
cascade
to
the
project.
So
we
can
do
that
today
in
the
api,
and
we
want
to
be
able
to
set
that
at
the
group
level
in
the
ui
as
well.
B
So
this
is
a
problem
that
we
already
solving
and
thinking
about
how
to
implement
and
I'm
working
on
refining
the
ui
proposal
so
that
our
front-end
engineer
andrew
can
pick
it
up
in
15-2.
B
The
last
one
is
a
stretch:
it's
the
org-level
environment
management.
The
reason
I
have
been
talking
about
this
larger
problem
of
surfacing
and
managing
environments
at
the
higher
level,
so
in
51
we're
going
to
start
talking
a
little
bit
about
ideation
of
the
problem.
How
we
want
to
tackle
it,
do
a
think,
big
within
team
and
figure
out
how
the
iteration
plan
for
this
problem.
So
it's
a
really
cool
one.
B
It's
going
to
be
interesting
to
see
how
we're
going
to
expand
and
also
continue
to
work
on
environments
and
environmental
management
with
gitlab.
So
that's
it
for
me.
Thank
you.
A
It's
unmute
all
right.
Thank
you,
hyanna,
really,
exciting,
updates,
I'm
excited
all
the
work,
we're
doing
all
the
design,
work
and
partnering
with
you
and
helping
figure
out.
What's
next
for
some
for
some
of
those
big
major
features,
we
have
coming
up
on
our
roadmap,
so
thank
you
all
for
watching,
if
you
have
any
other
questions,
feel
free
to
ping
us
on
the
planning
issue
and
looking
forward
to
next
time.
Thank
you.