►
From YouTube: GitLab 12.9 Kickoff - Release::Release Management
Description
- Executable Runbooks for Releases MVC (https://gitlab.com/gitlab-org/gitlab/issues/9427)/ Edit Asset Links from Releases Page (https://gitlab.com/gitlab-org/gitlab/issues/39472)
- Create a release using the UI(https://gitlab.com/gitlab-org/gitlab/issues/32812)
- Auto changelog (https://gitlab.com/gitlab-org/gitlab/issues/26015)
See our Release Management Direction https://about.gitlab.com/direction/cicd/#release
A
Welcome
to
the
12.9
release
management
kickoff,
my
name
is
Jackie
Michel
and
the
senior
product
manager
over
release
management
here
at
get
lab.
As
a
reminder,
release
management
is
inclusive
of
release,
governance,
release,
orchestration
secrets
management
and
get
LePage's
as
we're
wrapping
up
12.8
we're
excited
to
introduce
some
new
features
for
our
release,
orchestration
and
secrets
management
direction
in
our
12.9
release.
A
After
talking
to
some
of
our
users,
who
are
very
excited
about
release,
we
learned
that
release
is
actually
a
little
bit
difficult
to
use
at
gitlab
4.
We
are
gonna
tackle
one
of
the
biggest
issues
which
is
being
able
to
create
a
release
in
the
front
end
of
gitlab.
Now,
users
will
be
able
to
navigate
to
the
releases
page
and
click
create
a
release
from
that
view,
rather
than
having
to
navigate
to
the
tags
page
to
create
a
release.
A
Another
feature
that
we're
going
to
be
looking
at
adding
in
12.9
is,
in
the
same
vein
of
making
releases
easier
to
use
for
our
release
managers
and
build
managers
out
there,
we're
looking
to
automatically
create
release,
notes
leveraging
get
tagged
annotations.
This
is
such
a
cool
feature
for
those
who
are
used
to
manually
copying
and
pasting,
mr
and
issue
titles
into
the
changelog
and
get
lab
releases.
A
Next,
we're
going
to
begin
our
journey
of
expanding
the
edit
capabilities
on
the
release
page.
The
first
of
this
series
is
going
to
be
allowing
our
users
to
edit
asset
links
on
the
release.
Page.
This
feature
is
really
going
to
unblock
the
executable
run.
Vex
for
release
is
MVC.
The
minimal,
viable
change
for
executable
run
books
is
to
allow
a
user
to
link
a
run
book
to
a
release.
Tag
indicate
the
tasks
in
that
release
and
be
able
to
track
manually
tasks
that
are
completed
out
of
the
tasks
that
are
required.
A
This
will
help
enable
users
at
first
to
see
release
progress
calculated
from
tasks
that
they
have
manually
input
from
there
run
back
in
the
future.
We
will
see
a
little
bit
more
automation
around
run
books,
but
as
a
first
pass,
the
goal
is
to
help
enable
our
users
that
are
working
across
multiple
repos
projects
are
having
to
accommodate
external
approvals
and
processes
as
a
part
of
their
CI
CD
workflow.
Here
at
get
lab
last
but
not
least,
12.9
is
focused
on
building
out
secrets
management
functionality
as
well.
A
Our
infrastructure
team
has
been
hard
at
work,
making
vault
a
gitlab
managed
application,
so
in
12.9
we're
hoping
to
allow
our
users
to
install
Hasek
or
fall
into
kubernetes
cluster
leveraging
the
Hashi
corp
official
vault
helm
chart.
This
will
be
a
really
great
use
case
for
those
users
who
already
have
a
vault
account
and
are
just
looking
to
leverage
vault
as
a
part
of
their
normal
gitlab
CI
CD
process.