►
From YouTube: Release Management: UX/BE discuss proposals for Deploy Freezes, Runbooks, and Release assets
Description
Product Design (UX) and Backend discuss limitation and opportunity of current proposals for Release Management. Issues and MR we covered:
* Deploy freezes for environments MVC: https://gitlab.com/gitlab-org/gitlab/issues/24295
* Expose assets filepath URL on UI: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/25635
* Add runbook link to assets in Releases - MVC: https://gitlab.com/gitlab-org/gitlab/issues/9427
B
A
C
So
so
yeah,
so
in
the
gitlab,
see
I
am
all
I
think.
What's
there
is
probably
okay,
where
we'll
have
a
deploy,
freeze,
node
and
then
we'll
have
underneath
the
start
and
finish.
However,
the
issue
with
that,
so
that
will
be
fine,
I
guess
for
the
MVC.
But
the
issue
with
that
in
you
know,
in
a
larger
environment,
is
that
you'll
have
to
go
into
every
project.
If
you
have
a
fruit,
you
know
black
hat
or
freeze
period,
for
example
on
the
weekends.
C
Perhaps
it
would
be
a
good
idea
to
have
in
a
future
version
for
an
admin
to
have
some
type
of
you
over
all
the
freeze
periods
that
have
been
set
inside
all
the
various
projects,
possibly
with
a
button
to
trigger
them
or
override
or
something
and
and
then
there's
also
comment
from
the
infrastructure
team
about
how
they
have
some
type
of
calendar
that
you
know
all
those
public
holidays.
And
so
that
could
also
be
an
upcoming
feature
as
to
you
know,
one
or
more
calendars.
B
A
C
A
It
doesn't
put
some
questions
here
if
an
environment
has
multiple
furious
I
think
those
will
also
be
reflected
in
UI,
but
I'm
also
like
my
last
question
here,
is
about
not
this
one.
If
we
should
display
to
users
only
when
the
deployment
freeze
is
active
so
when
it
starts
or
we
free
shoot
like
have
a
way
to
proactively
tell
people
hey
starting
tomorrow
at
you
know,
APN
this
deployment,
this
environment
won't
be
deploying
to
production,
for
example,.
C
Yeah,
that's
also
a
good
point,
because
you
know
when
you
schedule
a
pipeline,
it
might
take
some
time
to
run
and
then,
when
you
schedule
the
phrase
might
not
be
in
place,
but
then,
by
the
time
it
gets
to
the
deploy
stage
in
the
freeze
could
actually
be
active.
We
need
to
have
an
edge
case
like
that,
so
I
don't
know.
Maybe
we
maybe
we
should
have
some
type
of
icon.
That
indicates
there's
a
phrase
period.
A
A
Yeah,
so
this
one,
for
example,
because
of
first
I,
was
trying
to
understand
from
this
scope
if
we're
going
to
do
for
a
job
or
per
environment,
with
we're
doing
on
an
environment
level
right
the
freeze,
that's
what
jackie
confirm
and
then
let's
say
that:
try
to
understand
how
that
will
translate
to
users
in
the
UI.
So
let's
say
that
we
are
the
NSC
I
filed
a
pipeline
right
deployment.
Freeze
is
active.
A
That
means
that
the
pipeline's,
for
example,
this
is
the
detailed
view,
office,
environment
and
then
here
I
added
an
alert
like
non
dismissible,
so
that
we
can
translate
that
information
from
the
CI
file
from
the
days
and
the
time
start
and
end
of
the
deployment
freeze,
I
added
as
well
the
time
zone,
but
I'm,
not
sure
how
that
will
translate
to
users.
So
is
it
it
signs
on
us,
whoever
activated
the
freeze
or
will
be
Glenn
kind
of
calculate
this
to
the
users?
You
know
time
time
zone,
that's.
C
C
C
C
A
I
think
will
be
intuitive
once
you
set
right
and
the
pipeline
runs,
and
you
update
the
file
that
we
automatically
show
this,
even
if
the
freeze
is
not
active
yet,
but
that
it
will
be.
You
know
at
some
point
in
the
future
to
other
people
that
yeah
this
might
happen
and
not
just
out
of
surprise,
because,
from
my
own
point
of
view,
I
think
it's
best
to
not
use
like
the
global
notifications.
Remember,
like
the
other
tracks,
about
informing
everyone
that
is
deployed
with
this
environment.
C
C
B
A
A
C
A
C
So
I
think
we
can
just
have
a
link
to
the
docs
that
describe
where
it
might
come
become
more
complicated
in
the
future,
as
if
we,
if
we
do
have
have
some
way
to
have
some
type
of
global
freeze
added,
for
example,
a
calendar
that
applies
to
them.
You
know
all
projects
we'd
have
to
you
know,
have
the
two
of
them.
A
C
Me
say:
yes,
okay,
so
good
question.
So
so
actually
just
one
thing
just
sped
this
better
yeah
look
I,
don't
know
if
it
needs
to
be
such
a
big
banner,
because
I
mean
it's
not
red
alert,
I
mean
what
if
we
even
just
now
have
have,
would
have
an
icon
look
similar
to
that.
You
know
next
to
the
other
icons
that
exist
where
it
just
says,
freeze
and
so
the
active
or
inactive.
And
then
you
can
have
a
link
to
the
docks.
C
That's
a
go
and
looking
you
know,
there's
a
there's,
a
freeze,
active
go
and
look
in
your
I'll,
see
how
I'd
say
we're
in
it
is
it's
not.
What
is
missing
is
all
this
information
or,
alternatively,
you
could
just
go
to
a
simple
page.
It
would
have
it
because
I
think
it's
somehow
having
an
hero.
As
this,
it's
almost
like
a
red
alert.
You
know
yes,.
B
C
C
A
C
The
moment
we
might
have
a
configuration
where
that,
where
the
production
involvement
has
to
be
manually
can
deployed
mm-hmm-
and
we
don't
say,
Red
Alert
on
that
right-
we
just
the
users
know
they
need
to
deploy
it,
you
familiar
with
it
but
yeah.
Given
us
a
new
feature
and
it's
it's
almost
like
a
braking
feature.
B
C
C
C
So
so
I
think
that
a
guy
misses
the
NBC
I
think
the
skip,
because
it
will
be
the
simplest
to
implement.
However,
what
we
might
consider
doing
you
know
you
know
in
a
future.
Iteration
needs
to
have
an
option
saying
try
at
the
end
of
the
freeze
period,
but
I
think
that
should
be
specific.
B
A
C
A
C
B
B
C
A
C
B
C
C
I'm,
sorry,
we
let
me
just
I'm
overthinking
this
actually,
because
if
okay,
so
if
it's
frozen
and
it's
the
end
of
the
freeze
period
and
you
want
to-
rather
you
just
have
to
run
the
pipeline
again
and
that's
their
solves
their
problem,
and
so
the
only
the
only
thing
that
we're
not
considering
is
what
happens
if
you
want
to
force
to
be
deployed
during
the
phrase
period,
so
the
in
VA
would
be
well,
you
go
and
change
the
ammo
I,
don't
know
if
it's
a
good
solution.
Yeah.
C
C
C
A
C
C
A
C
C
A
A
C
A
A
C
What
happens
if
we
want
to
during
the
appointment
so
I
think
maybe
we
need
to
have
a
way
to
switch
it
off,
because
what
happens
if
we
want
to
roll
back
and
a
guy
no
I'm
just
I'm,
just
considering
this
from
a
broken
production
issue,
grossing
production
perspective,
so
we
made
it,
we
made
it.
We
made
it
deployment
just
before
the
freeze
period
and.
B
A
C
C
A
B
C
C
C
A
B
A
A
B
C
In
fact
you
can
you
know
you
can
easily
see
such
a
scenario.
Actually
it's
like.
Okay,
we've
got
this
deployment
freeze
coming
up
and
guys.
We
need
to
get
all
this
new
stuff
in
before
then
and
then
some
stuff
gets
missed
and
then
so
people
work
on
it
so
that
it
can
be
deployed
immediately
as
soon
as
the
phrases
lifted.
So
then
they
would
need
access
to
review
environment
for
their
I.
A
B
C
C
Yeah,
so
what's
the
purpose
was
for
regularly
scheduled
for
months
in
takes
hold
deployments
in
off
hours,
but
again,
yeah
I.
Think
we're
really
talking
that
the
purpose
of
this
is
we
don't
wanna
push
something
into
production
when
there's
no
support
available
for
it.
You
know
it's
a
weekend
or
something
the
Deb
doesn't
necessarily
mean
people
couldn't
be
working
on
development
activities.
Yeah.
B
A
C
B
A
A
See
anything
else,
you
can
have
more
questions
and
support,
but
it
is
good
because
yeah
we
can
already
tackle
the
the
small
UI
improvements
and
think
about
how
else
this
thing
is
going
to
affect
the
user
experience.
Because
to
me
that's
that's
the
I'm
gonna
stop
the
chair
was
pretty
to
me.
This
is
the
most
you
know
funny
part
right
now
is
that
I'm,
a
I
just
want
to
make
sure
that
we
don't
miss
informing
people
that
this
thing
is
happening
and.
A
C
B
C
C
C
C
B
A
Me
question:
what
did
Jackie
say:
I
actually
just
say,
confuse
update
the
description
or
carve
out
and
general
issue
yeah?
Okay.
So
what
I'll
just.
C
A
Then
we
can
add
this
as
related
to
this
one,
otherwise
name
you
see
we'll
get
to,
but
I
like
the
a
I
would
like
to
understand
better
like
the
idea
of
the
like
the
calendar
or
how
we
would.
You
know
display
that
to
users
to
understand
this
a
little
bit
so
when
we
get
there.
Yeah
have
this
conversation,
because,
especially
if
we're
gonna
do
this
from
communities
in
a
group
level.
B
A
C
B
B
C
C
A
C
Okay,
so
what
we're
doing
here
is
we're
providing
an
alternate
way
to
to
display
a
link.
So
if
I
go
back,
I'll
go
back
to
the
issue.
So
it's
it's.
This
issue
here
enable
a
direct
link
to
a
release
and
a
release
assets,
and
so
we
might
have
this
link
sitting
over
in
Amazon
and
and
what
we
want
to
do
is
instead
of
displaying
it
with
the
Amazon
URL.
C
C
This
is
the
project,
there's
the
tag,
and
then
this
and
in
the
second
part,
is
whatever
they've
added
into
this
file
path
and
then,
when
they
click
on
it
actually
goes
to
the
real
resource
so
and
in
a
purpose.
This
is
later
on.
Well,
first
we'd
have
to
display
this
ugly
URL,
but
purpose
is
also
later
on.
B
C
We're
now
pointing
to
a
broken
work
with
now
displaying
a
broken
link
and
and
what
we
could
do
and
answer
this.
That
was
my
question
to
me:
am
I
in
the
in
the
EMR.
We
were
actually
displaying
the
link
we
could
over
time.
The
page
is
rendered
check
whether
Sylla
valid
ling
mm-hmm,
you
know,
and
if
it's
not
a
valid
link,
I
would
I
would
say
I'm.
B
C
A
B
C
B
A
A
B
B
C
C
C
Because,
in
fact,
so
when
we
were
doing
the
develop,
when
also
in
the
development
I
was
discussing
with
the
maintainer
about
his
opinion
was
well,
why
don't
we
just
verify
when
we
uploaded,
which
we
could
do?
The
thing
is
that
there's
two
issues
with
that
one
is:
it
might
take
a
very
long
time
to
upload
it.
A
C
A
C
A
A
C
A
C
Front
end
part
is
no,
it
does
it's.
Just
it's
very
simple
figure.
It's
just
it's
just
changing
the
URL
field.
It's
a
single
field,
change,
I,
think
I,
said
I.
Think
it's
one
of
the
topics,
one
yeah
there.
It
is
alright.
So
we
went
from
URL
to
far
path
which
actually
I
need
to
change,
because
that's.
A
A
A
A
Okay,
yeah
I
can
just
quickly
way
around.
It
is
because
if
you
can
inform
users
and
if
the
application
can
validate
ahead
of
time,
we
should
but
I'm
wondering
if
this
would
require
the
component,
because
this
is
about
a
component
to
kind
of
have
a
loading
say.
You
know
like
a
pre
loading
wall
invalidate
or
because
what
happens
when
you
land
on
this
page
is
that
if
there
too
much
data,
these
cards
are
gonna,
have
a
reloading
state.
Yep.
C
A
C
You
could
even
take
the
positive
use
case,
so
you
could,
you
could
just
load
the
page
load,
all
URLs
and
get
it
loaded
as
quickly
as
possible
and
then
go
through
those
and
it
loop
through
them.
In
the
background
you
know
in
the
browser
you
can
go
and
check
if
they're
broken
if
they
are
broken
in
show
it.
Otherwise,
don't
you
think
yeah.
A
A
A
C
A
C
A
C
C
A
C
A
Now
we
have
a
page
and
then
after
we
add
this
for
the
existing
ones,
then
I'm
gonna
be
working
on
creating
a
release
through
the
UI.
Because
that's
my
next
step,
because
now
we
only
support
edits
but
for
create.
You
need
to
go
to
the
API.
You
can
create
a
tag
using
the
UI,
but
you
cannot,
for
example,
and
a
milestone
leads.
You
can
only
edit
that
so
that's
yeah.
B
A
B
A
C
B
B
A
Careless
I
know
that
he
has
a
bunch
of
merge,
request,
still
open
about
the
edits
release
in
the
page,
so
I'm
not
sure
how
he
wants
to
go,
see
who
that,
but
from
from
our
scope,
point
of
view
I'm,
not
sure
if
this
issue
fully
reflects
what
we're
going
to
be
doing
in
the
back
end
like
the
front
end,
I
have
a
proposal
but
I
think
what
I
want.
Also
from
use
to
see.
If
the
proposal
section
this
one
say.
A
C
A
B
A
C
A
B
B
C
A
C
B
B
C
C
That's
just
because
it's
the
source,
that's
just
a
point
that
the
sauce
what's
in
a
source
code
is
not
actually
stored
as
it's
generated.
The
other
ones
are
actually
links,
but
then
the
next
package
is
the
one
that
was
more
worried
about
next
one,
sorry
next,
next,
next,
ok,
so
so
we
have
no
I,
don't
know
why
it's
mandatory,
but
we
have
a
on
the
API.
When
you
create
a
link,
you
must
give
it
a
name
and
then
I
don't
know
if
we
will
do
anything
with
those
names.