►
From YouTube: Release Management Think Big #5
Description
Check out our Release Stage
https://about.gitlab.com/direction/cicd/#release
Engage with Us on https://gitlab.com/groups/gitlab-org/-/epics/2377
A
B
C
C
C
C
B
A
A
B
B
B
There
you
go,
you
folks,
see
this
pretty
all
right,
I'm,
not
gonna,
go
ahead
and
explain
everything
in
detail,
because
at
this
point
as
soon
we
know
what
we're
talking
about
here
and
yeah.
So
just
a
quick
we
touch
base
on.
Why
we're
doing
this
right?
We
want
to
make
sure
that
we
improve
the
maturity
of
earnings,
orchestrations
and
move
it
from
minimal
to
viable
by
this
year.
B
So
this
effort,
this
team
effort,
it
tends
to
propose
the
bigger
solution,
so
I,
really
designed
I,
think
20,
plus
screams
based
on
the
data
collected
from
user
interviews
and
discussion,
will
be
having
a
sync
AC
and
synchronously
and
pretty
much.
It
covers
usability
for
releases
pages
issues,
the
epic
to
make
release
page
viable
and,
by
consequence
it
touches
also
making
releases
complete.
B
So
what
I'm
presenting
to
you
is
base,
as
I
mentioned
on
user
insights
and
I,
highlighted
here
three
of
the
main
user
insights
that
I
think
are
really
available
and
really
change
how
we
are
dealing
with
release
today.
So
the
first
one
we're
already
working
on
this
is
to
be
able
to
create
and
edit
a
release
using
the
interface.
B
So
for
those
who
are
new
to
this,
this
very
much
of
the
big
effort.
We
moderated
three
interviews
but
also
jackie
and
laurie,
conducted
like
I
don't
know
how
many
other
interviews
with
so
many
different
people
in
stakeholders
about
release,
orchestration
and
release
management,
and
I
documents
a
fifteen
unique
user
insights.
So
those
insights
are
challenges
that
users
currently
have
with
releases
feature
requests
or
answer
to
the
questions
that
we
have
so,
for
example,
do
they
want
more
of
this
functionality?
B
Do
they
have
challenges
from
a
UI
point
of
view
that
affect
the
workflow
and
etc?
So
I'm
gonna
go
ahead
and
get
started
and
I'll
show
you.
Let
me
know
if
you
can
see
this
because
we're
gonna
try
to
zooming
into
a
screen
and
it's
the
first
time
I'm
doing
this
online
so
bear
with
me.
Hopefully
it
is
a
word
for
everybody.
Oops
there
you
go
technology
all
right.
Let
me
reopen
this
Jesus.
B
B
This
one
right
I
want
to
start
from
the
beginning.
Can
you
focus
a
Miskin
if
it's
too
small,
please
let
me
know,
because
it
looks
fine
to
me
so
the
first
you
know
story
in
the
first
task
here
is
to
we're
already
doing
this
allows
us
to
create
a
release
through
the
UI.
You
can
see
here
that
I
made
also
other
improvements
as
in
updating
the
empty
state.
Here
you
right
now
you
have
a
button
that
takes
you
to
the
documentation,
because
this
doesn't
exist.
Wait
in
this
routine.
B
B
It's
a
text
area
and
I'll
have
a
few
complaints
from
users
that
it's
too
much
and
I
just
want
to
either
bypass
this
section
or
have
you
know,
a
simple
input
field,
so
this
is
new,
and
here
it's
all
the
data
that
the
user
can't
currently
added
through
the
API
attitude,
a
release
UI,
so
I'm
going
had
pretends
I'm
creating
release,
don't
mind
the
transitions.
This
is
just
this
application,
so
my
suggestion
here,
I'm
thinking
big,
is
to
allow
users
to
look
for
existing
text
right
now.
B
You
have
to
type
in
and
don't
have
an
autocomplete.
So
we
go
if
the
user
could
see
the
existing
tags
here
and
also
create
new
and
manage
tags
by
clicking
create
new.
Well,
they
just
create
a
new
tag.
Together
with
this
release,
manage
tags
will
take
users
to
the
tax
page
with
the
list
of
tags
and
if
I
click
here
in
12.8
Oh
add
to
my
release.
So
my
release
will
be
based
on
top
update,
great.
B
D
E
D
B
Thanks
for
asking
so
yeah
so
I
had
the
data
related
to
my
tag.
Also,
you
can
see
here
that,
because
most
of
the
items
on
this
form
are
not
required,
I
changed
here.
The
UI
to
make
only
the
required
ones
required
clearly
required.
So
I
can
add
a
title
to
my
release
right
now.
We
don't
have
this
on
the
UI,
but
we
have
on
the
API
it's
from
being
here
you
add
the
release,
notes
and
next
step,
it's
a
milestone,
so
this
ideally
would
work
the
same
way
as
we
associate
a
milestone
with
an
issue.
B
E
B
This
would
work
the
same
way
as
labels
work
for
issues
right.
So
if
you
select
multiple
here
and
then
they
all
stay
selected,
I
have
a
question
here
for
myself
on
the
side
that
I
need
to
investigate.
Would
we
be
sufficient
for
people
to
just
interact
with
this
drop-down
or
do
they
want
to,
as
they
add
milestones,
see
them
on
the
UI?
B
So,
for
example,
labels
under
this
input
field
so
that
they
can
clearly
see
malsu
detached,
but
this
would
be
I,
think
more
sparkles
on
top
of
this,
so
for
now,
I
think
will
be
sufficient
that
you
would
interact
with
this
drop-down,
so
I
select
milestone
is
attached.
If
you
have
more,
you
see
them
here
the
field
and
then
the
news
section
so
completely
new.
It's
also
SS
I
added
a
lot
of
helper
text,
because
I
want
to
evaluate
if
people
need
truly
need
this.
B
This
type
of
information
on
the
interface
a
couple
of
users
commented
that
yeah
I
don't
really
know
what
I
need
to
do
to
add
a
release.
There's
no
links
to
the
documentation,
so
I'm
really
bombard
them
with
with
helper
text
here
and
the
first
one
first
type
of
asset.
We
won't
be
able
to
associate
these
links,
so
this
would
help
us
achieve
the
vision
for
REM
books,
so
the
user
could
add
URL
and
a
link
title
this
field,
also
not
mandatory,
and
by
clicking
here
at
on
another
leaf.
B
You
add
another
little
through
UI
and
this
would
render
on
the
interface
I
also
have
to
check
here.
Can
we
delete
the
first
set
of
like
the
first
link?
Do
the
user?
Do
they
need
to
the
ability
to
remove
the
first
field?
It
is
just
something:
I
need
to
check
with
other
designers
as
well
and
lasting
release
date,
so
you
can
select
a
day
to
the
past
of
the
future
current
date,
and
here
just
also
another
habit
text.
Release
date
will
be
that
that's
in
the
future
will
be
labeled
as
an
upcoming
release.
B
E
B
C
B
I
can
I
just
do
this
prototype
and
then
we
investigated
further
okay
I
can
click
create
my
new
release
and
I
am
sent
to
the
detailed
view
of
my
release
right,
Nathan
and
Jackie.
It's
super
firm,
that's
lucky
once
so.
I
can
see
that
this
is
McCully
release.
I
can
see
here
in
the
assets
the
link
that
I
added
that
I
name
Ron
book
for
it's
all,
got
eight
other
assets
that
are
added
to
the
release.
This
part
just
to
this
fYI
this
this,
the
body
of
the
release.
E
B
A
C
B
That's
what
we
hear
for
anyone
else,
okay,
so
the
release
is
created
and
now
there's
something
like
I
should
have
forgot.
Something
on
my
release.
Notes
I,
want
to
add
this
or
I
want
to
add
a
new
milestone
to
it.
I
click,
the
edit
button
and
then
same
form,
but
now
I
cannot
edit
the
information
related
to
the
tag.
So
this
is
something
new
right
now.
B
I
didn't
at
this
interaction,
but
ideally
would
have
the
option
on
a
model
asking
do
you
want
to
edit
do
want
to
delete
this
release,
and
do
you
also
want
to
delete
the
tag
associated
with
this
release
because
yeah
right
now,
when
you
delete
the
notes
of
Emily,
you
delete
everything
you
remove
it
the
deck.
So
we
don't
want
that
to
do
that.
B
B
E
The
only
reason
I
ask
is
because
the
the
API
does
allow
you
to
move
a
release.
You
can
update
a
release
to
a
different
tag,
but,
on
the
other
hand
like
in
my
gut
feeling,
tells
me
that
that
wouldn't
be
a
super
common
use
case,
so
I
think
it
makes
sense
regardless
to
keep
it
the
way
you
have
kind
of
for
us
as
a
first
iteration
and
then
add
that
ability
later
on.
If
we,
if
we
need
it,
yeah.
A
C
Thank
you,
okay,
so
the
first
one
is
I.
Like
the
just
the
tag
metaphor,
I,
think
it's
great
with
the
milestones
and
you
know
the
way
we're
doing
it
in
in
in
tags
and
labels.
Sorry,
labels
at
the
moment,
I
think
works
perfectly
so
and
then,
with
all
this
text,
there's
a
lot
of
instructional
text
on
on
they
on
the
other
pages.
C
B
C
B
B
C
It's
all
like
well,
I,
guess,
there's
a
I
thought
there
was
a
few
question
marks
and
some
some
issues
are
recently
commented
on.
So
you
know
so
we
create.
The
evidence
at
the
moment
is
I
think
it's
only
one
there's
only
one
evidence,
but
then
we
changed
it
or
we
are
changing
it.
To
has
too
many
evidences
for
a
release.
Yeah.
A
There
should
be
two
evidences
for
a
release:
the
one
at
time
of
release
creation
and
looks
like
here.
If
you
have
an
upcoming
release,
you'd
have
a
evidence,
collection
link
and
then
the
second
snapshot
would
be
at
the
release
at
time
frame.
But
we
wouldn't,
according
to
you
the
most
recent
thing
that
you
added
Shawn.
We
wouldn't
have
like
a
historical
release.
Evidence
right.
Okay,.
C
C
C
B
So
yeah
another
interesting
things
that,
with
this
view
in
particular,
we
want
to
validate
what
data
user
is
watching
consume.
And
how
do
you
want
to
organize
this?
So
here,
for
example,
we
also
got
feedback
from
people
saying
that
yeah
I
need
to
know
who
created
this
release.
I
want
to
see
the
name
of
the
user
right
now
we
only
display
the
editor.
So
that's
a
super
small
change
display
jondells
name
there,
a
link
to
his
profile,
so
that
whoever
is
looking
at
this
so
release
can
see
this
information.
B
B
B
So
I'm
just
gonna
go
ahead
and
go
back
to
the
releases
of
reviews,
so
you
folks
can
see
how
they
look
like,
and
this
is
it
for
releases
I'll
just
quickly
show
you
how
the
interaction
will
work
for
text
use
the
text
page
to
small
changes
here,
so
the
first
one,
as
you
can
see,
is
the
release
that
we
just
created.
12.8
is
shown
here
like
this
label,
and
the
bottom
shows
edit
right.
So
I
can
click
here
and
go
padded.
B
My
release-
and
this
is
the
case
where
Jean
s
before
I-
have
a
tag
that
doesn't
have
a
release
associated
with
it.
Yet
I
would
then
have
the
option
to
create
a
release
for
this,
for
this
tag,
so
I'm
hovering
the
button
with
with
the
rocket
here.
I
cannot
mark
that
in
the
interaction,
but
you
would
have
to
tip
saying
create
release
for
this
tag.
I
click
the
button
I'm
taking
to
this
very
same
form
so
expand
it
with
the
options
for
the
release.
B
I
create
a
release
I'm
taking
to
the
detail
view
of
this
new
release.
So
this
is
a
small
change
on
how
we're
dealing
with
tax.
Today,
and
also
we
want
to
validate,
ok
are
people
happier
with
this
interaction
with
this
separation
between
releases
and
tags,
because,
right
now
you
add
it
both
things
same
way,
but
the
form
is
just
it's
just
very
different.
Any
questions
on
the
on
this
proposal
comments
John,.
D
Think
it's
also
thing:
sorry
if
I
go
ahead
but
yeah
sorry,
thanks
hi
on
a
for
explaining
this
I
was
getting
a
little
bit
mixed
up
in
my
head.
Just
cuz
I'm
used
to
I
kind
of
equate
a
tag
to
a
release
of
one
to
once
and
now.
This
makes
a
lot
of
sense
to
me
if,
for
some
reason,
you're
creating
tags
and
those
aren't
automatically
creating
releases
through
your
gate
lab
see
IMO
file,
then
this
is
a
way
to
add
a
release
to
attack
cool.
Thank
you
so
much
for
explaining
first.
E
One
question
I
had
I'm
trying
to
member
what
it
was:
oh
yeah,
if
you
so
one
of
the
mock-ups
and
I
might
have
been
looking
at
things
that
you
weren't
intending
to
show
in
this.
So
you
feel
free
to
cut
me
off,
but
one
of
them
had
a
toggle
button.
That
said,
create
a
public
release
and
then
the
other
one
had
to
collapse.
Button
so
I'm
to
me.
Those
kind
of
would
serve
the
same
purpose.
I'm
curious
how
those
interact
with
each
other
yeah.
A
B
B
So
that's
awesome
that
you
you
mentioned
this
one,
because
I
wanted
to
show
you
how
I've
been
experimenting.
We
need
your
face
and
also
we
have
so.
This
is
based
on
the
interns
proposal
for
adding
a
toggle
to
the
tax
form
and
then
once
you
on
and
off,
you
would
see
the
the
data
for
the
for
the
release.
B
So
if
I
click
this
off
now,
then
this
whole
section
here
releases
would
just
disappear
from
an
interface
and
then
I
was
experimenting
actually
looking
at
how
we
do
we
do
with
a
circuit
at
this
point
and
I
decided
to
go
ahead
with
a
proposal
for
the
expand
and
collapse
for
two
reasons:
the
first
one,
because
it
aligns
more
of
how
we
are
hiding
and
showing
data.
So
if
you
go
to
project
settings,
for
example,
you
expand
the
collapse
and
I
also
want
to
meet
you.
B
Oh
man,
I
need
to
figure
out
which
one
I
wanted
to
show
you
or
anyways
our
to
be
more
in
context,
so
in
a
way
that
I
can
see
information
about
what
the
release
is.
So
if
I
show
you
this
one
yeah.
So,
let's
assume
that
this
is
the
tax.
This
is
wrong
here
in
the
title,
but
this
is
a
tax
page.
I
can
already
see
more
income
tax
information
about
what
the
release
is
and
go
to.
B
The
docs
and
I'm
curious
I
can
expand
here
and
see
the
data
rather
than
interacting,
with
with
the
taco
itself
that
yeah,
it's
more
like
the
tenets
of
the
requires,
more
effort
for
users
to
discover
that,
but
I
also
want
to
validate
this
Nathan
I
went
ahead
with
this
proposal,
fooling
with
expanding
collapse.
What
I
want
to
put
this?
The
toggle
is
going
front
of
users.
D
B
E
I
was
thinking
if
you,
if
you
expanded,
that
release
section
and
then
you
filled
out
one
of
the
required
fields,
but
not
the
other
one.
Then
do
we
see
attics
yeah
I'm
go
ahead,
an
click
that
expand
I
was
curious.
I
guess
we
only
have
one
required
field,
which
is
the
notes
so
you're
thinking
that
if
you
expand
it
and
then
add
notes,
that's
what
tells
it
to
create
a
release.
Yeah.
B
The
same
one
we
do
now
with
the
Whitacre
in
tax
form,
it's
just
a
release,
notes
that
they're
optional,
but
in
a
way,
if
you
feel
that
in
yeah
I
think,
ideally,
we
should
be
able
to
allow
users
to
that's
how
I
think
yeah
maybe
remove
a
releases
ROM
attack.
Okay,
does
that
make
sense
like
I
like
we
were
talking
about?
If
you
can
associate
change
the
tag
that
you
just
associated
by
mistake,
for
example,
to
overly,
would
you
be
able
to
move
the
release
notes
or
the
release
information
to
a
new
tag?
B
Because
we
had
a
there
was
this
one
participant
of
the
user
interviews.
I
say
that
yeah,
it's
really
awful,
that
I
have
to
manually
copy
paste
all
the
information
when
I
created.
You
know,
if
I
create
a
release
in
the
wrong
tack
by
mistake.
I
have
to
go
ahead
and
copy
paste
everything
into
a
new
form,
so
it.
C
B
E
Another
idea
I
had
this,
isn't
really
just
an
idea:
the
create
release
button
I
thought
we
could
also
dynamically
change
it.
The
text
to
show
what
we're
actually
creating.
So,
if
we're
going
through
the
flow
and
we're
creating
a
new
tag
and
a
release,
we
could
say
create
tag
and
release
or,
if
we're
just
adding
a
release
to
an
existing
tag,
we
could
say
create,
release
or
just
say,
create
tag
for
only
creating
a
tag
that
might
be
some
indication
to
like
as
to
what
we're
creating.
C
C
I,
like
that
I
think
just
a
side
effect
of
this
whole
thing
is
having
this
form.
Is.
It
actually
shows
you
because
at
the
moment
I
would
you
know
the
feeling
in
gitlab?
Is
that
the
relate
you
know
in
the
Gitlow
product
is
that
release
releases
are
very
under
built,
or
you
know,
but
in
fact
just
by
showing
this
form
it's
actually
quite
big.
I
mean
we
have
all
this
stuff
that
we
can
associate
and
connect
and
and
the
form
really
displays
it
to
you
know
to
users
yeah.
B
B
C
B
This
forum
is
gonna,
become
even
more
complex
because
another
thing
as
China
we're
discussing
in
the
previous
call
that
right
now
you
can
link
assets,
but
if
I
want
to
attach
for
just
add
a
package
over
here,
yeah
right
now,
the
only
way
you
can
do
things
is
by
dragging
and
dropping
to
the
release
notes.
But
then
this
adds
it
in
the
description
in
the
release
notes
and
what,
if
users,
to
have
these
in
the
SS
section
right.
A
Like
so,
we
have
this
whole
epic
for
how
to
support
assets
and
releases,
and
that
includes
binary
files
and
images,
and
hopefully
the
the
get
lab
releaser
tool
will
help
manage
how
we
upload
those,
but
in
the
UI
kinda
just
like
github,
where
you
have
that
option
to
add
an
asset
as
an
uploaded
file,
we
will
need
to
support
that
in
the
UI.
Eventually
yeah.
B
Yeah
I
see
this
for
me.
If
we,
if
you
want
to
fully
manage
it,
really
sturdy
why
this
can
become
quite
complex
and
I.
Think
in
the
future
will
be
interesting
from
a
UX
point
of
view
to
experiment
with
how
the
users
will
interact
with
with
this
portal,
yeah
sure,
like
those
boring
fields,
but
have
an
option
to
you,
know
I
know,
maybe
progress
on
disclosure
may
be
a
way
to
that.
B
B
A
We
will
already
be
building
some
of
this
stuff
like
in
this
milestone
and
next
milestone.
So
the
goal
will
be
that
we're
really
not
only
well
I
have
interview
scheduled
with
users
now
and
into
the
future.
But,
like
you
know,
at
the
end
of
12.9,
my
hope
would
be
to
start.
You
know,
tracking
those
actions
that
people
are
taking
in
the
front
end
and
understandings
like
with
that
data
to
just
use
usage
data.
So
we'll
need
to
think
about
yeah
that
for
me,
a
prototype
feel
to
and.
B
For
the
new
things,
I,
here's
a
suggestion
for
the
solution,
validation
that
we
reach
out
to
the
release
managers
like
internal
release
manager,
so
yeah
accident
I,
found
this
page
today
that
it
has
everyone
a
good
lab
that
is
going
to
be
responsible
for
release
in
the
future
or
to
have
being
in
the
past.
So
we
can
reach
out
to
these
people
specifically
and
it's
right
off
the
the
prototypes
within,
but
also
with
the
external
customers.
I
think
this
would
be
very
interesting
to
us
two
different
perspectives.
I
agree.
A
With
looking
even
now
just
scheduling
time
with
like
John's
car
back
because
he
was
resistant
to
implementing
the
release,
functionality
forget
lab
and
get
live
calm,
mainly
because
the
he's
waiting
for
like
the
auto
changed
logs
and
otherwise
that
would
be
like
a
really
manual
process
for
them.
They
don't
want
to
have
to
break
what
they're
currently
doing
for
all
that.
B
And
I
think
in
already
scheduled
the
next
steps,
maybe
for
the
solution,
validation
for
the
things
that
don't
exist
yet
yeah,
but
I
really
try
to
not
introduce
a
lot
of
changes.
Let
me
see
if
I
can
forgiving
a
lot
of
changes
to
the
interface
here,
so
we
should
be
able
to
reuse
components
and
UI
elements
that
we
have
today.
A
One
thing,
mindful
of
is,
as
we
get
more
time
boxes
from
the
planned
stage,
how
we
want
to
associate
releases
more
time
boxes,
so
the
plan
stage
is
going
to
reframe
milestones
into
this
thing
called
the
time
box,
which
will
be
like
a
sprint.
A
milestone
could
be
custom
iterations
for
users,
I
think
it's
on
their
roadmap,
so,
whatever
whatever
we
build
there,
we
kinda
have
to
think
about
what
does
that?
Look
like,
as
other
stages,
begin
to
expand,
yeah.
B
We
can
already
bring
some
of
these
prototypes
into
the
discussion
with
them
to
see
yeah,
so
I
think
the
only
change
on
component.
So
this
is
important
for
Nathan.
It
would
be
that
people
should
be
able
to
select
multiple
milestones
here
on
this
drop-down,
but
also
the
tags
yeah.
This
doesn't
exist
right
now
on
the
release
page,
but
and
I,
don't
think
we
have
I
mean
we
have
this
behavior,
but
I,
don't
think
we
have
anything
related
to
this
drop
it
and
drop
it
down.
My.
A
From
from
some
actionable
next
steps,
I
have
a
meeting
this
week,
scheduled
with
all
of
you
all,
mostly
to
talk
about
the
run
books
functionality
within
this
prototype,
so
that
we
can
understand
what
issues
we
need
to
create
out
of
this
prototype
from
that
segment.
Given
that
that's
our
top
priority
for
12.9
and
then
1210
is
going
to
be
expanding
a
lot
of
the
Edit
capabilities
within
the
release
page.
So
I
would
like
to
really
get
a
graph
on
what
backend
work
needs
to
get
done
to
support
that
front
end.
A
A
They're
like
this
is
kind
of
cool,
but
it's
not
really
not
really,
where
I
need
it
to
be.
For
me
to
stop
using
something
like
github
releases
and
it's
not
where
I
need
it
to
be
in
order
to
support
my
inner
sourcing
needs.
So
a
lot
of
customers
I
have
probably
about
10
or
so
that
I've
spoken
to
are
managing
inter
sourcing
shops.
A
So
they
are
using
git
lab
for
their
developers
to
pull
down
images
and
copy
those
environments
and
then
like
create
and
deploy
code
from
their
machines,
either
in
an
air-gap
environment
or
just
as
a
way
of
sharing
information
and
that's
like.
If
we
can
nail
that
use
case
like
we
will
make
probably
50%
of
our
ultimate
current
customers.
Like
really
sticky.
C
And
just
following
on
for
you,
Syd
checking
I
mean
if
that's,
if
that's
the
case,
I
didn't
realize
that
if
that's
the
case,
then
I
mean
in
a
way.
This
is
a
low-hanging.
Fruit
like
it
seems
complex,
but
in
fact,
if
it's
going
to
give
that
much
value
to
our
customers,
there's
not
that
much
and
if
we
kind
of
as
you
saying
swarm,
we
can
really
kind
of
ale
it
pretty
quick.
There's
not
it's
not
like.
You
know
unknowns.
It's
really
just
it's!
Just
software
development.
A
And
it's
gonna
be
it'll,
be
one
of
those
things
where
we'll
start
to
see,
like
our
staged
monthly
active
users
just
exponentially
increase,
because
this
is
just
such
small
behaviors
that
people
are
expecting
out
of
our
application,
but
they're
gonna
really
delight
them,
because
they're
able
to
just
manage
their
things
and
to
end
from
their
CI
all
the
way
to
their
deployment,
and
you
can't
really
do
that
uninterrupted
today.
So
this
this
is
going
to
be
really
cool
for
us
in
Hyuna.
Your
work
has
been
just
incredible.
Thank
you.
I'm.
B
Excited
to
you,
I,
don't
really
spend
a
lot
of
time
where
you
interface
I,
think
you
know
that
we
usually
work
with
the
acceptance
criteria
or
the
smallest
changes
in
the
UI,
but
it's
nice
to
have
the
discussions
in
CMP.
This
is
everything
that
we've
been
discussing.
That's
how
it
translates
in
the
product
I'm
happy
that
have
a
chance
to
did
that
and.
A
Because
we're
trying
to
create
this
non
technical,
technical
nexus
point
for
our
users.
And
it's
going
to
be
a
really
cool
opportunity
for
not
only
our
customers,
who
are
looking
to
get
off
tools
that
they're
managing
releases
with,
but
for
our
internal
teams
too,
that
are
trying
to
use
gitlab
to
release
their
product.
Gonna,
be
really
cool.