►
From YouTube: GitLab 14.10 Kickoff - Release
Description
Release 14.10 Planning Issue: https://gitlab.com/gitlab-org/ci-cd/release-group/release/-/issues/113
A
Hi
everyone
I'm
chris,
the
senior
product
manager
for
the
release
stage
here
at
git
lab
I'm
here
with
hayanna
the
acting
product
designer
for
release
and
she's,
also
the
product
design
manager
for
verify
package
and
release,
and
this
is
the
14.10
planning
issue.
A
Okay,
let's
move
on
to
the
issues,
so
the
first
one
is
a
security
issue
that
we're
tackling
for
the
quarter.
We
have
engineering-wide
okr
to
resolve
a
lot
of
these
issues,
and
so
one
of
the
ones
that
we're
working
on
that'll
be
slotted
for
this
milestone.
A
The
second
one
is
is
related
in
terms
of
apis
that
are
exceeding
certain
thresholds
and
error
thresholds.
And
again
we
want
to
resolve
this.
Bala
did
great
work,
so
shout
out
to
bala
on
investigating
a
lot
of
these
and
figuring
out
what
areas
we
should
prioritize
in
terms
of
making
improvements
for
our
air
budget
the
next
one
we've
talked
about
before
it
is
actually
in
progress.
A
But
this
one
is
multiple
stop
for
an
environment,
and
so
today
we
only
support
and
only
actually
execute
one
of
the
onstop
hooks
that
are
defined
for
an
environment
in
the
yaml
file.
This
this
work,
this
issue
will
allow
users
to
buy
multiple
non-stop
hooks
that
will
actually
run
when
an
environment
is
stopped.
So
it
increases
the
flexibility
and
allows
teams
and
users
to
make
sure
that
they
kind
of
take
down
in
for
different
environments
and
support
all
the
different
scenarios
that
they
might
have
for
their
environments
and
deploy
jobs.
A
The
next
one
is
one
of
the
bugs
that
we're
taking
on
right
now
we're
displaying
sometimes
the
wrong
commit
in
certain
scenarios.
So
we
want
to
make
sure
that
we
always
accurately
reflect
the
the
actual
commit
that's
deployed
to
the
environment,
and
so
this
is
one
of
the
the
sus
ux
related
bugs
that
we
want
to
make
sure
we're
solving
and
showing
the
right
commits
for
our
users.
A
The
next
one
is
fixing
some
copy,
but
it's
a
little
bit
misleading
today,
where
we,
where
we
say
that
we
don't
have
any
environments
when
we're
looking
at
the
stops
tab,
we
want
to
correct
the
copy
to
make
sure
that
we're
accurately
representing
what
we're
actually
what
we're
actually
showing.
So
in
this
case,
it
should
say
you
don't
have
any
stopped
environments
right
now.
On
that
stops,
tab.
A
All
right,
the
next
two
are
related
to
instrumentation,
as
I,
as
I
said,
in
the
goals
for
the
milestone.
So
these
I'm
really
excited
about,
especially
as
we
continue
to
learn
more
about
our
users
and
better
understand
how
users
are
using
git
lab
to
deploy,
and
so
this
particular
one
we're
we're
aggregating
the
number
of
users
that
are
triggering
deployments.
So
today
we
have,
we
have
a
counter
that
shows
us
users
and
teams
that
are
deploying
using
environments.
A
This
allows
us
to
be
a
little
bit
more
broad
in
terms
of
capturing
how
many
users
are
using
gitlab
to
deploy
so
now
we're
combining
users
that
are
that
have
stages
that
look
like
deploy
stages
as
well
as
combining
that,
with
the
existing
counter
that
we
have
today.
A
This
will
give
us
a
better
view
across
across
the
different
teams
that
are
using
gitlab
to
deploy,
and
what
we'll
do
in
a
future.
Duration
is
potentially
combine
combine
these
metrics,
so
we
have
a
more
holistic
view
of
deployments
and
then
the
last
one
here
is
instrumentation
for
the
deployment
approvals
so
excited
about
this
feature
that
we've
been
working
on.
For
the
past
few
milestones,
we
want
to
add
instrumentation
to
better
understand,
to
understand
how
users
are
using
it,
and
so
so
that
we
can
make
improvements
over
time.
A
B
Chris,
the
first
item
in
the
design
table
is
a
solution:
validation
for
the
environments,
page
redesign,
so
that's
a
second
round
of
validation
in
14,
8
and
49.
We
designed
and
also
implemented
a
series
of
interface
changes
to
address
usability
issues
in
the
environments
view,
and
we
receive
feedback
from
some
users
and
customers
about
how
those
changes
impact
their
daily
tasks
and
also
the
overall
perception
of
the
page
and
usability.
B
So
we're
going
to
continue
to
iterate
on
this
capability
and
understanding
how
the
future
changes
that
we
want
to
make
in
the
environments
page
will
impact
the
users
the
tasks,
but
also
looking
into
some
different
personas.
So
1410
you'll
be
conducting
a
series
of
user
interviews
to
validate
and
make
these
appropriate
updates
and
move
forward
with
the
environments.
Page,
redesign
and
vision.
B
Second,
is
the
approved
deployment
from
the
detail
view.
So
we
want
to
expand
the
ability
for
users
to
approve
or
reject
deployments
through
the
the
environment
page
and
after
receiving
a
notification,
for
example,
for
a
new
deployment
approval.
We
want
users
to
have
the
ability
to
navigate
to
a
place
where
they
can
see
what
deployment
they
actually
need
to
act
on
or
to
approve,
reject
anyways
to
just
to
review,
and
that's
the
the
design
part
of
this
problem.
B
As
I
mentioned,
this
is
an
important
update
right,
a
continuation
to
the
design
flow
that
will
allow
us
to
iterate
on
the
notifications
and
the
completion
of
the
improvement
flow
in
the
next
iterations
next,
more
environment,
stuff.
It's
the
actual
notification
flow
the
to
do's.
So
we
want
to
understand
we
actually
we
do
understand
how
important
it
is
for
users
to
stay
informed
about
what's
being
deployed
and
where
and
when
they
need
to
approve
when
they
need
to
review
these
items.
B
So
we
are
ideating
on
how
to
deliver
the
notification
to
the
to
the
approver
of
the
spree
deployments
to
production
or
whatever
environments
they
choose,
ideally
or
not,
ideally,
but
initially
through
the
to-dos.
That
will
follow
a
similar
notification
flow
that
we
have
today,
for
example
for
environments.
Oh
sorry,
for
issues
and
more
requests,
and,
lastly,
it's
another
usability
improvement,
also
related
to
environments.
B
This
issue
addresses
ui
copy.
There's
some
confusion
today
when
users
have
to
redeploy
an
environment
and
the
text
that
they
see.
It's
not
clear.
This
issue
is
also
related
to
tech
writing.
So
it's
a
ui
copy
and
it
also
contributes
to
the
current
ux
okrs
for
cells.
So
we
are
addressing
severity
to
ux,
bugs
that
impact
usability
and
working
on
the
proposal
on
the
design
of
this
issue
will
help
us
contribute
to
that
particular
ux
engineering
okr.
A
Thanks
ayana
excited
about
the
all
the
great
work.
That's
coming
up
excited
to
work
with
you
also
part
of
the
team,
and
so
that's
what
we
have
planned
for
14.10,
more
detail
in
the
planning
issue
here,
I'll
link
it
in
the
in
the
summary
for
the
video
and
if
you
have
any
ques
questions
or
feedback.
Let
us
know
thank
you.