►
From YouTube: GitLab 12.7 Kickoff - Release:Release Management
Description
Welcome to Release Management's 12.7 Kick off.
API for Protected Environments - https://gitlab.com/gitlab-org/gitlab/issues/30595
Capture Release actions in the audit log page - Release Governance MVC - https://gitlab.com/gitlab-org/gitlab/issues/32807
Allow administrators to disable gitlab pages access - https://gitlab.com/gitlab-org/gitlab/issues/32095
Show issue summary on Releases Page FY20 Vision - https://gitlab.com/gitlab-org/gitlab/issues/31289
Delete an environment via UI - https://gitlab.com/gitlab-org/gitlab/issues/20620
Research Spike: GitLab Pages without DNS wildcard - https://gitlab.com/gitlab-org/gitlab/issues/29841
A
Miss
Jackie
Michel
the
senior
PM
over
release
management,
which
includes
release
orchestration
pages,
release,
governance
and
secrets
management.
Now
they're
wrapping
up
12.6,
we
are
set
to
kick
off
the
twelve
top
seven
milestone
and
I'm
pretty
excited
for
it
automatically.
This
milestone
is
about
delivering
and
enhanced
operational
effectiveness
for
our
users
that
are
leveraging
their
release
functionality
and
get
lab.
This
will
be
seen
and
taking
release
governance
actions
a
little
further
by
adding
our
release
capabilities
to
the
audit
log.
A
We're
also
going
to
be
improving
access
management
across
release
orchestration
and
get
lab
pages,
making
it
even
easier
to
administer
your
get
lab
instance.
We
also
have
a
few
items
going
through
design
and
validation,
12.7,
which
are
centered
around
the
ease
of
use
for
our
release,
page
features
and
even
better
environment
management.
Let's
go
ahead
and
dive
into
our
release
for
12.7.
A
A
Now
that
we've
built
out
all
these
capabilities
to
create
a
release
via
the
API
to
edit
release
content
and
to
edit
a
release
event
as
well
as
download
artifacts
and
a
release,
we
now
need
to
be
able
to
report
on
those
in
an
audit
so
for
our
users
that
are
hoping
to
be
able
to
effectively
leverage
release
actions
and
get
lab
they're
now
going
to
be
able
to
report
on
these
actions
in
an
audible,
auditable
manner.
We
do
intend
to
expand
the
audit
log,
as
we
add
more
functionality
to
releases.
A
So
this
is
just
the
first
iteration
of
that
in
the
same
main,
of
making
gitlab
easy
to
use
and
administer,
we
are
going
to
be
expanding.
The
ability
to
disable
get
my
pages
access
with
a
check
box
in
the
get
lab
pages
settings.
This
is
a
really
exciting
feature
for
our
customer,
who
need
to
be
able
to
administer
pages
access
in
a
in
a
refined
way.
So
this
will
be
exciting
for
our
regulated
industry
customers,
as
well
as
anybody
who
is
looking
to
be
able
to
restrict
access.
A
Another
issue
that
is
a
high
priority
for
12.7
is
this
API
for
protected
environments.
This
will
allow
better
privileges
for
developers
and
maintainer
x'
to
be
able
to
manage
the
access
to
environments
via
the
API.
So
now
we'll
be
expanding
the
environment
API
for
those
people
who
are
currently
using
the
API
to
do
all
other
effort
to
expand
access
permissions.
A
Deleting
an
environment
via
the
UI
is
another
one
of
those
features
about
making
it
more
operationally
efficient
to
leverage
gitlab.
It's
kind
of
interesting,
because
today
you
can
delete
environments
in
it
in
API,
but
you're
unable
to
do
that
in
D
UI.
While
you
can
create
environments
in
the
UI.
So
in
order
to
improve
that
journey,
we
will
be
expanding
that
UI
capability
to
be
able
to
delete
the
environment
in
the
list
and
detailed
views.
A
We'll
also
be
spending
some
time
in
this
release
to
really
be
thoughtful
about
our
gitlab
pages
support
without
a
dns
wild
card.
The
instrumentation
issue,
for
this
is
one
that
has
lots
of
eyes
on
it,
and
several
of
our
customers
are
very
interested
in
getting
that
functionality
in
12.7
going
to
be
researching
what
it
means
to
support
this
capability.
A
We
are
being
thoughtful
about
it
due
to
any
potential
downsides
to
supporting
this
functionality.
So
the
goal
is
that
in
12.8
we'll
be
able
to
actually
instrument
that
feature,
but
this
research
spike
is
dedicated
to
being
thoughtful
and
deliberate
with
how
we
support
those
capabilities
inside
gitlab
in
our
validation,
work
stream,
we're
currently
investigating
blackout
periods
as
well
as
run
books.
So
if
those
are
two
concepts
that
really
excites
you,
please
check
out
our
solution,
validation,
column
and
add
some
commentary
on
either
of
those
issues.
A
We
also
have
heard
that
you're
looking
for
more
information
on
your
releases,
so
we
will
be
kicking
off
a
work
stream
to
get
a
little
bit
more
information
from
end
users
about
what
they
would
like
to
see
in
release
pages
after
we
deliver.
This
show
issue
summary
on
release
page,
so,
if
you're
interested
in
any
of
the
validation
issues
or
any
of
the
work
that
we
have
ongoing
in
12.7,
please
feel
free
to
strike
up
a
comment
and
have
a
conversation
with
us.