►
From YouTube: GitLab 14.8 Kickoff - Release
Description
Release 14.8 Planning Issue: https://gitlab.com/gitlab-org/ci-cd/release-group/release/-/issues/105
A
This
is
the
last
monster
of
the
quarter,
so
we're
really
eager
to
cover
a
lot
of
ground
and
hit
a
lot
of
our
quarterly
goals,
and
the
first
goal
of
the
milestone
is
to
ship
the
environments
page
redesign.
A
B
A
A
This
will
look
something
like
this.
As
you
can
see
right
within
the
environments
page,
the
user
will
see
some
new
buttons
and
have
the
ability
to
approve
a
rejected
deployment
in
the
spirit
of
iteration.
This
first
nvc
does
not
include
the
comment
functionality,
but
we'll
be
doing
that
next.
I'm
super
excited
about
this
feature.
In
particular,
we
just
spoke
to
a
customer
on
monday
who's
eager
to
implement
a
new
workflow
based
on
this
capability
to
meet
their
strict
security
and
approval
requirements.
A
The
next
issue
is
adding
a
configuration,
a
configuration
setting
in
the
ui
to
set
how
many
approvers
are
required
for
an
environment
as
part
of
the
approval
feature
we
just
talked
about
next
is
to
augment
our
current
deployment
count
with
additional
counters.
A
So
this
is
the
first
issue
of
our
effort
to
improve
our
instrumentation,
so
we
can
better
understand
how
our
users
are
using
release,
features
and
deployments
using
gitlab
right
now,
we're
only
counting
deployments
that
are
using
the
environments,
keyword
and
that
feature
in
their
yaml
file,
and
so
currently,
we
effectively
under
count
the
number
of
deployments
that
are
actually
occurring
within
gitlab.
A
A
B
Thanks
for
that,
chris,
so
for
the
design,
we
have
a
quite
packed
milestone
ahead
of
us.
I'm
actually
start
by
mentioning
this
one
since
there's
a
lot
of
design
work.
This
milestone
that's
supposed
to
support
the
front-end
development
of
deployment
approvals
and
deployment
uis
right
new
environments
page.
So
this
entry
is
supposed
to
open
up
space
for
me
to
create
pajamas
components
out
of
our
new
uis
and
that's
important,
because
these
uis
will
be
reused
in
other
pages
in
the
near
future
in
our
product.
B
So
it's
important
to
have
these
components
as
repeated
was
as
reusable
as
possible
in
other
pages.
In
terms
of
feature
work,
we
have
wrapping
up
the
proposal
for
the
group
environments
page.
This
is
pretty
much
done,
but
we
have
to
split
it
in
two,
so
this
is
what
it
would
look
like
more
or
less.
It's
a
high
level
environments
page
on
the
group
level
at
first
that
contains
all
the
projects
and
all
the
environments.
Within
that
group.
B
From
the
group
environments
proposal,
we
came
up
with
a
more
advanced
proposal
for
a
dynamic
deployments
list.
This
would
be
a
page
that
would
list
every
single
deployment
in
a
given
group
and
let
you
filter
and
basically
set
up
your
view
with,
whichever
deployments
you
need
to
see
it's
still
very
early
stages,
so
part
of
the
effort
listed
here.
It's
also
to
validate
this
new
issue.
B
After
that
we
have
a
preparation
for
a
scorecard
for
release.
The
link
is
coming
soon.
It's
based
on
a
bigger
planning-
that's
that's
still
pending,
but
the
current
status,
for
that
is
an
openmr
that
restructures
our
jobs
to
be
done
for
release.
That's
a
preparation
for
this
scorecard
next
up
support
the
remaining
design
issues
for
deployment
approvals.
One
of
those
is
the
update
project
settings
that
chris
mentioned
is
one
of
our
first
issues
in
the
milestone
in
order
for
it
to
be
to
be
developed.
B
After
that,
we
have
one
issue
about
adding
an
environment
button
to
the
pipelines.
So
in
the
pipelines
page,
you
can
open
the
link
to
your
environments
to
your
review,
apps,
whatever
environments
you
have
being
created
from
the
pipeline
and
at
last,
an
issue
to
display
the
environment
here
on
the
environments
page.
So
it's
an
information
we
already
have
in
the
api,
some
information
that
is
already
on
the
gitlab
yaml
file
so
showing
that
up
on
the
page.
So
in
the
near
future
we
can
filter
by
tier
and
add
more
functionality.