►
From YouTube: Release Management Think Big #7
Description
Check out the Release Management Group Page for links to our Direction:
https://about.gitlab.com/handbook/product/categories/#release-management-group
A
All
right
we're
here
for
our
release,
management,
think
big
I
think
it's
number
six
could
be
number
seven
I
think
it's
number
six
good
job,
y'all
kiona!
You
have
the
first
item
and
then
I
added
a
couple
of
different
points.
So
we
can.
If
you
want
to
review
the
release,
page
user
interviews,
I'll,
let
Jeff
yeah.
B
A
C
A
Is
a
really
good
meeting
to
talk
about
this,
because
I
think
nathan
has
a
lot
of
contacts
into
why
we're
going
down
the
route
that
we're
going
down?
But
let's
definitely
tease
it
out
a
little
bit.
We've
decided
that
there
are
places
where
users
would
just
want
to
tag
their
code
and
create
a
release
from
it.
C
D
A
Like
a
pre-release
version
that
they
want
to
call
v1
and
then
they're
going
to
do
more
changes
and
then
they're
gonna
release
the
B
1.1
and
that's
going
to
be
the
one
that
they
want
to
release
and
that's
what
they
want
to
create
their
release
from
so
having
some
sort
of
separation
between
releases
and
tags
was
important,
but
on
the
form.
What
we
wanted
to
show
is
that
people
can
create
their
release
and
then,
if
they
want
to
expand
or
the
collapse,
to
create
a
tag
or
just
a
release.
C
D
B
Then
I
like
what
Jackie
gave
me
I,
really
see
that
stairs
movement,
because
about
25
I
started
filling
the
form
you
might
backstage,
with
beta
related
to
a
release
and
I
collapse
it,
but
then
X
to
create
avenues
right
right
now.
We
should
we're
not
really
thinking
out
for
those
educators
but
think
we
need
to
open
some
investigation
there
to
define
some
workflows
or
revisit
the
experience.
B
A
For
example,
say
that
I
go
in
and
I
create,
AG
I,
expand
it
and
I'm,
like
oh
I'm,
gonna
start
creating
my
release
and
then
I
leave
that
page
and
then,
if
I
go
back
to
their
release
tab,
it
has
the
option.
We
have
the
option
to
keep
that
information
and
that
tag
pre-populated
on
that
and
allow
you
to
save
it.
Or
we
say
that
you
leave
that
tab
and
you
leave
the
releases
page.
We're
not
gonna
keep
that
session
and
we're
going.
D
A
A
C
You
know
this
is
a
I,
wouldn't
say
unique
feature
of
get
laid,
but
it's
something
to
get
labs
got
all
over
the
place.
Right,
like
you,
start
working
on
a
time
any
time.
Sorry
I
start
working
on
a
comment
and
then
you
go
off
some
other
page
and
you
come
back
and
then
bang
here
it
is
right,
which
is
a
not
easy
to
do,
but
secondly,
a
lot
of
products
don't
have
it
actually
lucky
github
doesn't
have
it.
A
That's
why
we
might
want
to
implement
it,
but
it
also
might
not
be
worth
implementing,
because
the
time
and
effort,
if
it
doesn't
happen,
often
like
if
people
aren't
creating
a
tag
and
then
saving
it
and
then
going
back
to
edit
it.
It's
really
comes
down
to
workflow.
So,
as
a
user
do
I
typically
generate
my
tag.
C
A
C
B
B
Feedback
and
receivables
also
that
releasing
notes
are
important.
Then
it's
the
barb,
the
area
and
this
interface
or
the
flow
that
people
go
back
and
forth
because
they
want
to
be
mean
and
the
status
of
the
various
chambers.
From
the
moment
you
create
the
moment,
you
actually
release
it,
so
I
think
that's
a
very
relevant
field
for
how
to
safety
or
storing
the
data.
The
more
I
I
believe
that
people
would
go
to
tax,
for
example,
to
change
it
back
or
to
change
a
milestone
if
they
selected
something
by
mistake.
B
That's
that
also
the
able
to
mean
receiving
that.
It's
not
really
something
all
just
change
the
reset,
maybe
just
grow
up.
We
need
to
start
on
work,
what's
happening,
flexibility
to
have
the
edge.
You
know
the
way
we
do
now,
but
it
was
really
nice
to
hear
a
bunch
of
these
suggestions
and
improvements
and
I
think
in
general
moving
forward.
What
I
want
to
make
sure
is
that
the
page
doesn't
become
a
monster,
because
the
way
we
are
also
displaying
this
data
on
the
release,
you
is
that
we
are
adding
a
lot
of
content
and.
C
B
Need
to
be
mindful
about
how
we
want
to
translate
the
Abia
attributes
to
be
why
and
what
makes
more
sense.
So
one
of
the
users
say
that
you
would
like
to
have
the
banks
that
sorry,
the
the
milestone
a
field
next
to
the
tag,
because
to
me
those
are
related
and
not
at
the
very
ends.
So
that
also
shows
how
the
data
is
displayed
on
the
UI
when
you're,
seeing
your
release,
I've
created.
A
B
A
So,
what's
kind
of
cool
is
that
they're
debating
having
our
major
release
next
month,
so
thirteen
actually
end
up
being
in
June,
which
means
we
would
be
able
to
build
out
a
lot
of
our
stuff
and
twelve
double
Evan.
If
we
decided
to
do
it
in
12
11,
because
right
now,
I
just
have
add
milestones
as
a
release
p1
for
1210
and
then
of
course
adding
the
runs
book
links
so
editing
links,
but
eventually
we'll
need
to
add
all
this
other
features
functionality,
and
that
was
going
to
happen
between
now
two
13.1.
A
C
A
C
A
You
that
was
actually
a
really
good
comment,
because
I
just
posted
in
this
an
hour
think
big
release
management,
the
new
product
metrics
that
they're
starting
that
they're
the
leadership
project
leadership
is
going
to
start
holding
product
managers
accountable
to
and
if
we
look
at
the
top
25
issues,
four
of
them
are
in
our
area,
a
release,
management
and
there's
five
hundred
issues
or
thousand
issues
that
are
in
this
top
customer
requested
issues,
and
it's
a
it's
a
link
in
the
in
the
periscope.
Every
time
I
share
my
screen
with
periscope.
A
And,
what's
what
we
wait?
Vlad
has
posted
in
the
pages.
Without
DNS
valuation
is
kind
of
cool
he
was
like.
We
could
make
this
just
a
page
feature
which
would
be
a
really
great
opportunity
to
either
increase
the
investment
in
pages
by
making
it
a
paid
feature
which
would
be
good.
It's
a
lot
of
our
customers
who
are
asking
for
that
feature
are
also
paid.
Oh.
A
D
D
A
C
C
C
C
A
Know
you're
going
down
a
really
good
tangent.
That's
why
we're
I'm
well
I,
want
it
to
be
like
transparent
as
to
what's
motivating
product
priorities
and
I
just
got
a
new
tidbit
of
information
from
leadership.
Saying,
hey,
I
know
that
we're
telling
you
to
drive
this
revenue
number
and
although
the
pages
category
of
something
with
revenue,
you
have
a
top
requested
issue
from
sales.
So
this
would
suggest
to
me
that
hey
that
means
I
could
potentially
continue
to
invest
in
pages,
because
it's
a
revenue
driver,
yeah.
C
C
A
Different
like
we
have
to
be
differentiated
and
enough
to
to
compel
usage,
and
differentiation
enough
is
to
give
it
for
free
right.
So
there's
a
couple
of
ways
that
we
can
think
about
this
creatively,
but
that's
I
just
wanted
to
give
you
visibility
into
that
perspective.
Mm-Hmm
before
I
talk
about
run
books,
I
wanted
to
check
in
on
deploy
freezes,
given
that
12.10
is
around
the
corner
and
that's
one
of
our
flagship
features
for
1210.
So
in
the
1210
kickoff
I
have
three
flagship
features.
One
of
them
is
deploy
freezes,
NBC
and
I.
D
C
Yeah
I
can't
I
would
really
like
to
do
it.
If
we
could
find
you
know
a
POC,
a
rough
POC
like
I
would
probably
give
it
two
days
maximum,
which
hope
you
know,
presumably
we'll
be
able
to
use
their
code
anyway,
because
I
just
there's
a
few
gray
areas
in
the
backend
that
I'm
not
really
kind
of
Accenture
over
sure
about,
and
particularly
if
we
start
to
use
this.
C
The
resource
groups
thanks
here
because
initially
ARMA
for
this
is
really
good
idea,
but
now
I'm
starting
to
dig
into
it
like
it's
slightly
different
use
case
because,
in
fact,
I
said
at
first
we're
gonna
get.
This
is
great.
We're
gonna
get
the
restart
for
free
but
see
how,
as
I
understand
it.
I
think
the
way
it
works
is
when
there's
another.
When
is
a
blocked
pipe?
And
you
know
when
the
other
pipeline
finishes,
then
it
then
it's
a
trigger
to
unblock
the
other
one.
C
So
that's
why
I
can
restart,
whereas
our
our
use
case
is
different,
there
won't
be
a
blocking.
There
won't
be
another
parallel
process,
so
that
means
we
have
to
have
some
type.
If
we're
going
to
have
restartable,
which
ID
we
said
initially.
No,
so
you
know
we
said
we
don't
we.
You
know
it's
not
going
to
restartable
initially,
but
if
we
start
to
use
a
resource
groups
feature,
it
is
designed
to
be
restartable
and
it's
designed
to
be
triggered
by
another
pipeline
process.
C
So
it
you
know
it
I
think
I
would
just
need
to,
as
I
said,
to
a
Pio
see,
because
maybe
that's
not
the
right
direction
to
go
in,
although
it
does
feel
like
the
right
direction,
because
I
think
that
we'd
have
to
have
some
type
of
independent
process.
Like
a
you
know
about
a
background
process,
it's
kind
of
waking
up
even
now,
and
then
seeing
whether
you
know
we
need
to
unfreeze
this
this
pipeline,
so
that
all
adds
kind
of
a
lot
of
stuff.
C
A
C
A
Okay,
I'm
creating
your
tech
evaluation
issue
right
now,
for
this
we're
gonna
cue
it
up
for
1210
a
release:
P
wine
and
it'll
block
deploy
freezes
MBC
so
that
we
know
we
have
to
do
that
work
first
prior
to
ending
the
deploy,
freeze,
MPC
and
then
after
you
do
the
POC.
If
you
can
update
the
proposal,
I
think
Nathan,
you
can
still
proceed
with
any
front-end.
If
there
is
anything
on
the
on
the
current
proposal,
I
don't
think
there
is.
So
let
me
check
yeah.
B
C
A
C
C
In
fact
it's
not
in
fact
it
was
so
how
in
fact
it's
not
about
so
what
happened
was
you
know
in
the
investigation?
I
think
she
knew
suggested
hey.
Why
don't
you
use
resource
groups?
This
is
actually
kind
of
what
you
need,
and
so
I
had
a
look
at
that
Matt.
Actually
it
does
look
good
because
if
so,
it's
already
handling
stopping
pipelines,
for
you
know
blocking
pipelines
essentially,
but
then,
but
then,
and
then
oh
and
then
it's
like
oh
and
it'll
end
of
restarts
awesome
right.
C
So
so
I
I
definitely
recognize
that
styling
is
not
at
all
in
the
original
MBA
and
and
we
could,
we
should
probably
leave
it
out,
but
then,
if
we,
if
we
start
to
use
this
feature
and
we're
using
it
so
differently
than
what
you
know,
how
it's
already
been
used-
and
you
know
maybe
it's
not
worth-
maybe
we
should
just
build
something
else.
If
we
say
you
know,
if
we
use
resource
groups
in
such
a
different
way
than
what
is
actually
being
designed
for
that's.
C
A
C
Because,
because
because
also
there's
another,
so
there's
another
related
issue
out
in
this,
you
know
in
the
issues
for
you,
which
is
this
one
about
the
evidence.
This
is
the
evidence.
Creation
one
is
actually
related
right,
because
what
what
we're
missing
a
kid
lab
is,
is
this
ability
to
really
share
do
something
in
the
future
and
have
it
reliable?
You
know,
because
we
don't,
we
don't
have
a
we
don't
ever
we
just
we're
just
using
saiki
cryde,
and
so
we
don't
have
a
proper
scheduling
environment
like
you
know
in
queue
series
or
something
like
that.
C
A
I,
like
the
way
your
your
brain
is
thinking
on
that
front.
Connecting
this
to
release
evidence,
cuz,
I,
think
from
an
efficiency
standpoint,
we
would
want
to
try
to
reuse
those
two
components
as
much
as
possible
for
releases,
so
that
makes
sense.
I
am
really
worried
that
we're
detracting
from
the
focus
and
the
value
we're
trying
to
drive
with
this.
C
C
D
C
A
D
From
my
point
of
view,
we've
kind
of
sounds,
like
everyone
kind
of
Gries,
a
option,
one
that
I
posted
originally
is
the
way
to
go
and
there's
some
minor
things
we
need
to
figure
out,
particularly
where,
on
the
syntax,
what
this
is
gonna
look
like
in
the
mo
file.
We
haven't
nailed
that
down
yet,
but
I
think
we
probably
a
settlement
option,
one
enough
that
we
can
move
that
up
for
the
description.
Okay,.
C
C
And
did
we
decide
by
the
way
that
we're
not
going
to
use
named
freeze
periods
for
either
we're
just
gonna
have
whatever
is
on
that
page
gets
applied?
If
you
say,
freeze
period
opt
in
because
it
cuz
I
cuz,
you
could
say
the
future
version
would
be,
they
would
ahead
all
have
names,
and
then
you
could
say
which
names
you
wanted
to
use.
Let.
A
C
D
D
C
D
D
D
C
D
B
C
Because
you
can
argue
both
ways:
cuz
I
did
suggest
the
opt-out.
However,
when
you
think
about
it,
it's
great
if
you've
got
a
site,
that's
got
okay,
they
got
lots
of
projects
right
and
they
don't
have
to
go
into
all
the
em
all.
But
on
the
other
hand,
the
you
know,
the
counter-argument
is
that
once
once
they've
set
up
a
single
freeze
period,
that's
automatically
blanket
applied
to
everything
right
and
maybe
that
that
could
be
a
bit
of
a
shock
if
you
weren't
expecting
it
right.
C
C
A
A
C
A
B
C
Well,
I
think,
there's
I
think
we
went
a
bit
further.
You
know
discussions
a
net
so
that
Yamanashi
turn
into
what
could
turn
into
a
table.
I.
Could
you
know
a
table
of
three
columns,
or
maybe
four
columns?
Are
we
gonna
give
it
I
thought
about
maybe
giving
it
a
name
but
not
actually
using
the
name
yet,
but
yeah.
A
C
So
see,
I
I
initially
thought.
Well,
let's
just
make
it
a
a
text
area
and
to
put
yeah
milena
as
an
easier
step,
but
in
fact
probably
the
the
passing
of
that
yeah
Milan.
Everything
else
is
probably
easy.
If
we
just
had
a
single
rails
table,
you
know,
maybe
maybe
just
do
it
in
Hamel
and
don't
use
you
know
JavaScript
for
the
time
being,
and
then
you
know
because
ultimately
you
can
see
if
we
get
to
some
type
of
thing
with
overrides
and
a
cowl
or
everything.
A
A
Okay,
so
what
I've
done
is
I've
copy
pasted
up
to
the
issue
description,
the?
What
I
think
was
the
final
decided
scope
to
move
forward
with
so
Shawn
and
Nathan
would
love
your
eyes
on
it
to
confirm
that
that
the
issue
description
reflects
what
we've
discussed
and
if
there's
any
other
open
items
that
we
need
to
remove
from
this
and
then
yeah.
D
B
D
D
A
D
D
C
So
so
something
have
got
touched
on
in
this.
You
know
in
the
conversation
in
the
issue,
was
you
know,
so
we
can't
we
can't.
Actually
we
don't
know
it's
a
production,
environment
or
whatever,
and
and
so
do
we
do
we,
whatever
the
whatever
the
syntax,
is
gonna,
be
in
the
CI,
whether
to
opt
in
opt
out
or
whatever
it's
gonna
pay.
Do
we
do
that
at
the
only
in
jobs
that
I
have
an
environment?
Is
that
does
that
make
sense,
yeah.
C
D
A
So
I
think
the
only
action
on
this
is
just
to
review
this
issue
and
then
hi
on
a
you
and
I
can
either
carve
out.
What's
in
this
UX
proposal
for
additional
issues,
because
I
see
like
I,
think
the
tooltip
is
the
only
one
that
we'll
be
adding
in
the
NBC
and
then
where
to
request
view,
and
all
of
this
stuff
will
be
out
of
this
MBC.
Is
that
right?
Okay,.
A
A
A
So
we
have
a
lot
of
the
executive
team
talks
about
us,
a
lot
as
as
a
really
big
opportunity,
because
we
have
a
ton
of
market
share
that
we
are
showing,
as
eroding
already
the
sales
team
likes
talking
about
our
offering
they're
excited
to
bring
me
into
conversations
with
deals
with
prospects,
which
is
good,
so
well
done.
I'm
really
excited
for,
for
it.
I
I
dropped
in
a
dry
run,
recording
here
with
Itzik,
so
he
did
the
demo
presentation
and
if
you
are
interested
it's
an
hour
long
thing
so
I
wouldn't
recommend
doing
it.
A
A
Question
because
this
also
would
include
like
incident
management,
run
books
and
configuration
run
books,
so
we
wouldn't
just
be
supporting
the
foundation
for
release,
run
books.
I.
Think,
though,
when
we
look
at
things
like
running
scripts
and
markdown
files
as
code
and
building
out
the
animal
templates
for
run
books,
all
of
that
can
be
leveraged
by
these
other
teams.
A
So
I'll
start
fleshing
out
the
user
stories
and
requirements
around
those
templates
a
little
bit
more
after
we
deliver
that
visibility,
linkage
and
start
getting
people
like
linking
their
run
books,
because
if
we
get
users
linking
their
run
books,
we
could
then
start
looking
at
the
data
that's
provided
to
us
and
what
people
are
including
and
if
they're
expecting
us
to
support
you
know
executing
Excel
files
or
if
they
were
just
wanting
us
to
support.
You
know
Jupiter
notebooks
right
now.
A
I,
don't
have
a
lot
of
data
on
that,
but
I
have
a
emerge,
request
open
that
mark
pun,
sack,
kind
of
rejected,
but
but
Kenny
just
kind
of
told
me
to
be
the
DRI
over
run
books
and
to
run
with
it.
Even
though
Mark
said
no,
so
we'll
see
we'll
see
how
that
all
turns
out,
but
just
wanted
to
give
you
give
you
an
update,
how
that's
working
and
we'll
be
working
across
three
or
four
different
stages
to
deliver
work
that
would
be
benefiting
five
different
personas.
A
Now
we're
just
gonna
have
to
like
figure
out
a
timing
for
it
and
when
it
makes
sense
to
like
develop
against
it,
because
I
feel
like
we
have
right
now
getting
release
page
viable.
Getting
that
linkage
between
run
books,
setting
deployed
freezes
and
then
secrets
management,
and
then
Wilson
will
end
up
getting
back
to
refreshing.
They
release
this
page,
making
it
lovable
and
then
then
finally,
we'll
probably
get
to
more
advanced,
run
books
and
then,
of
course,
like
I.
A
A
A
A
This
might
be
the
number
of
commits,
or
the
number
of
past
commits
over
the
past
30
days
or
total
number
running
of
releases
across
your
projects.
So
picking
those
five
metrics
I
have
cries,
I
think
assigned
to
that
research
issue.
He'll
just
have
to
look
at
what's
available
and
then
what's
easy
to
aggregate
and
create
something
cuz,
I
really
I
really
just
want
to
see
like
today.
People
aren't
really
looking
at
the
CIC
the
analytics
dashboard,
because
it's
like
not
very
useful
information.
A
D
A
A
Yeah,
what
I
wanted
to
do
was
to
get
the
technical
research
for
what
metrics
could
be
used,
because
in
my
past
life,
I
managed
analytics
across
30,
prod
30
products
and
every
time
I
went
into
a
room
that
showed
somebody
a
dashboard
or
graphic.
They
wanted
to
see
it
with
the
metrics
and
KPI
is
that
they
would
be
getting
so
I
need
to
understand
what
KPIs
are
gonna,
be
relevant
and
then
will
be
able
to
show
them
that.
A
B
A
What
you're
thinking
that
makes
perfect
sense,
I
feel
like
once.
We
filled
out
this
group
level
dashboard
that
the
second
priority
will
be
environment,
because
you'll
start
to
see
people
follow
the
commits
and
the
environments,
like
that's
a
journey
that
they'll
take
that
we
may
link
people
from
the
director
dashboard
to
the
environments
dashboard,
because
that
will
give
them.
You
know,
get
them
into
the
project
right.
B
A
Exactly
I
would
like
I
would
rather
land
them
from
analytics
to
analytics
to
project
rather
than
from
group
analytics
to
new
project,
because
that
will
be
just
such
a
jarring
experience
if
they
start
at
the
group
level
and
they
dive
like
headfirst
into
all
the
details
so
on
well,
we'll
think
through
that
a
little
bit
more,
we
have
two
minutes
how's
it
going
guys
on.
Are
you
exhausted
you're,
like
the
sucks
I,
don't
want
to
come
to
these
think
big
meetings
anymore.
B
A
I
think
I
think
the
opportunity
here
is
to
elevate
Shawn
and
Nathan
as
more
of
our
senior
leaders
in
their
development
spaces.
So
that's
kind
of
the
the
intent
is
to
create
this
cohort
that
then,
can
be
shared
throughout
the
teams.
Chris
smees,
if
you
will
at
least
that's
what
I
want
to
do,
it
makes
it
way
easier
to
like
say:
Shawn
you're,
my
back-end
guy.
Can
you
help
me
out
here
and
then
so.
D
C
B
A
A
B
C
A
The
Edit
capabilities
it
for
me,
it
feels
like
we
do.
Move
slow,
like
I,
have
to
wait
every
milestone
to
get
a
new
edit
capability,
and
it
makes
me
anxious,
because
how
does
the
end
user
feel
when
they're
creating
and
editing
releases
yep?
So
I
completely
relate
to
this
I
love?
This
value
of
iteration,
but
I
do
feel
like
our
iteration
cycles
are,
are
not
as
short
as
yep.
C
A
C
I
mean
because
the
thing
is
I
also
think
the
small
iterations
are
great
for
my
mistake
too,
but
from
the
perspective
of
a
customer,
it's
like
why?
Don't
they
just
give
us
the
whole
thing
already,
you
know
look
well
I
can
we
can
see
it,
but
we
can't
edit
it.
You
know
things
like
that.
You
know
like
a
must
right.