►
From YouTube: UX Showcase: Deploy Freeze
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Can
you
folks
see
the
full
screen,
Thanks
cool
awesome,
so
hi
everyone
Mahina
finishing
moves
senior
product
designer
for
the
early
stage
release
management
here
in
gitlab,
and
today
I'm
super
excited
to
share
with
you
some
of
the
findings
and
deliverables.
We've
been
working
with
to
what
we
call
deploy
phrases
with
Gitlin,
and
this
is
also
a
super
cool
story
about
how
UX
research,
product
design,
product
management
and
engineering
can
work
together
to
use
user
insights
to
inform
and
guide
our
decisions
so
quickly.
I
know
we're
all
familiar
with
those
screens.
A
Release
management
is
part
of
the
XE
ICT
stage.
We
are
meeting
a
lot
of
cool
features
on
functionality
with
respect
to
continuous
delivery
and
release,
automation
and
the
point
Freitas
falls
into
the
release.
Orchestration
category
we
just
moved
it
from
minimal
to
viable
and
release
orchestration
is
pretty
much
the
ability
to
coordinate
complex
features.
Oh
sorry,
complex
releases
across
projects
in
an
efficient
way
leveraging
of
code
behaviors,
and
some
of
my
goals
for
today
is
to
share
results
for
the
problem
validation
and
to
highlight
the
opportunities
deep.
A
As
for
the
initiative
goes,
the
business
goal
was
to
improve
the
competitive
position
of
gitlab
releases
across
team
fields
by
administrating
deployments
and
environments,
and
none
of
the
ways
that
we
can
achieve.
That
is
by
offering
the
poi
freezes
capabilities
and
for
a
goal
for
users.
The
goal
is
to
be
able
to
specify
windows
of
time
when
deployments
are
not
allowed
for
environments,
we
get
lab
so
that
they
can
interlock
some
internal
policies
with
CI,
CD
and
automation,
but
we're
deployed
freezes.
A
I
think
we
are
very
familiar
with
the
concept
of
culture
ease
right
since
first
the
companies
that
can
be
a
super
scary
thing
and
deploy
resist
and
help
ensure
stability
during
those
periods
of
low
engineering
supporter
activity
such
as
weekend
of
hours
holidays
and
by
stopping
deployments
and
preventing
teams
from
introducing
new
issues
and
from
critical
incidents
to
recurring
and
typically
well.
The
more
automated
unemployment
is
the
safer
it
becomes.
So
the
value
that
we
are
bringing
here
is
to
be
able
to
set
some
specific
timeframes
for
an
mainly
enterprise
and
regulated
industry.
A
So
supporting
the
point
freeze
would
get
lab
would
allow
us
to
erode
some
of
the
release,
orchestrations
capabilities,
the
same
way
as
our
biggest
competitors
and
as
I
mentioned.
This
is
super
common
for
regulator,
industries
and
some
of
the
example
sales
and
Black
Friday
or
January
sales
and
e-commerce
websites.
A
They
need
to
make
sure
that
network
traffic
is
stable
and
internally
forget
lab
our
main
internal
customers
are
production
and
delivery
teams
and
we
want
to
make
sure
that
in
lab
stable,
when
we
have
big
company
announcements,
livestreams
contents
or-
and
we
are
holidays
right
so
quickly,
I'm
going
to
go
over
what
we
learn
from
problem
validation.
It
was
a
lot
full
disclosure
I'm,
just
gonna
highlight
some
of
the
topics
that
really
influenced
the
design
solutions.
A
So
when
we
started
talking
about
the
value
of
being
able
to
restrict
deployments
timeframes
or
product
manager,
Jackie
I
saw
she's
in
the
phone
today.
Thank
you
for
joining
jockey
she's
turned
into
customer
interviews
to
validate
some
of
our
assumptions
and
she
surveyed
more
than
200
participants
and
interviewed
five
I.
Think
a
total
of
five
customers.
Three
external
went
to
internals
to
talk
about
the
point
phrases
and
this
sort
of
alien
cover
that
around
sixty
percent
of
the
respondents.
That's
150
users
need
to
support
this
deployed
winter
freeze
windows
of
time
in
their
companies.
A
So
if
we
assume
that
50%
of
the
midland
users
are
the
point
with
gitlab,
that
would
be
at
least
60%
of
those
users
that
could
leverage
of
deployment
freezes
and
again
regulated
industries.
They
really
need
something
like
that,
and
this
feature
would
really
allow
us
to
reach
tire
organizations
and
really
focus
on
that
specific
market.
A
We
learned
that
managers
and
release
managers
are
the
most
benefitted
from
this
picture,
and
the
parties
that
typically
set
those
free
spirits
are
leadership
of
engineering
of
some
organizations
and
those
responsible
for
enforcing
the
policies
can
include
non-technical
release
managers
DevOps
software
engineers
and
that
team
needs,
so
other
things
I
want
to
highlight
here
is
that
when
we
talk
about
release
manager,
this
role
is
this
role
is
really
it's
really
a
mix
in
some
companies
they're
really
merged
into
one.
So
you
have
the
pops
engineers
that
do
release
management.
A
We
have
release
managers
let's
to
go
and
work
with
the
code.
So
when
we
talk
about
designing
release
management
functionalities,
it's
really
have
to
pay
attention
on
the
expectations
of
familiarity
that
users
have
with
developer
Center
workflows.
So
that's
why
you're
gonna
see
across
the
presentation
two
personas
highlighted.
A
Some
of
the
problems
we
identified
was
that
well
many
users.
They
have
to
set
those
deployment
periods
manually
and
sometimes
they
have
to
do
that
outside
of
the
system.
So
it's
really
like
writing
some
yellow
file,
and
we
don't
really
support
this
out
of
the
box
with
gitlab
the
level
of
pain.
It
causes
when
you
cannot
set
the
point
freezes
easily.
A
Well,
everyone
pretty
much
hates
cold
freezes,
the
level
of
stress
in
teams
when
the
point
who
are
not
deploying
to
production,
so
people
often
just
trust
their
employees
and
they
are
not
going
to
deploy
things,
but
because
you
don't
really
have
anything
stopping
the
deployment
from
happen.
Well,
they
can
see
can
still
happen
right
and
we
also
seen
customers
writing
their
own,
yellow
configuration
and
also
some
users.
A
They
already
leverage
of
similar
functionalities
with
Xenia
labs
and
also
with
github.
So
there
is
a
competition,
so
some
of
the
learnings
that
influence
the
user
experience
when
I
start
working
on
the
design
phase,
which
is
kind
of
funny,
because
there's
never
like
a
single
design
phase
I
break
my
test
into
pretty
much
four
four
steps
right,
so
working
with
the
PM
to
identify
what
is
the
main
user
story
that
we
want
to
focus
for
the
MVC.
A
The
scenarios
in
at
cases
that
we
discussed
with
the
entire
team
the
acceptance
criteria
for
the
main
user
stories
and
the
secondary
user
stories.
We
identify
and
low
fidelity
prototype
if
that's
necessary
and
discuss
and
iterate
the
the
deliverables
and
decisions
with
the
team
and
move
to
high
fidelity,
prototyping.
So
I'm
going
to
highlight
some
of
these
steps
today
and
one
of
the
ways
we
found.
That
is
super
important
for
us
and
it
really
helps
us
facilitate
the
discussions.
A
A
So
by
doing
this
type
of
exercises,
of
course,
we
also
discuss
things.
Asynchronously
I
learned
a
couple
of
things
that
influenced
my
design.
First,
I
learned
that
we
could
specify
deployed
phrases
using
a
chrome
syntax.
That
is
something
that
is
already
being
used
in
get
lab
and
also
that
the
the
CI
file
would
instruct
the
pipeline
and
the
ey
would
be
where
users
could
set
the
freezes.
So
that
imagine
that
you
were
both.
You
have
both
technical
and
non-technical
steps
in
this
process.
A
So
you
I
versus
Midland,
see
the
CI
file
and
we
also
talked
about
how
it'd
be
great
to
automatically
retire.
We
try
the
job
and
continue
the
deployment
process
freeze
when
it
was
over
when
the
phase
was
over
or
to
just
immediately
have
the
ability
to
bypass
other
boy
freeze,
but
we
found
that
this
was
too
large
for
the
scope
of
the
MVC.
A
So
in
my
user
story
the
acceptance
criteria
includes
both
user
and
front-end
requirements,
and
in
this
face
with
these
assets,
we
are
already
able
to
identify,
for
example,
which
people
and
my
wife
components
do
we
want
to
use
here.
Thus,
this
form
is
validation,
so
everything
is
set
for
front
end
and
back
end
to
either
go
with
the
with
the
the
the
status
of
this
user
story
or
break
into
smaller
pieces
and
different
deliverables.
A
So
some
of
the
assumptions
that
were
validated
by
p.m.
ended
up
ganya
decisions
were
related
to,
as
I
mentioned
configuration
on
your
Y
verses
on
the
CI
file.
So
we
assume
that
users
wanted
to
administer
and
manage
the
phrases
/
environment
and,
in
the
end
our
decision
was
that
yeah
they
want
to
set
freezes
mainly
on
protected
environments,
but
that
we
should
have
limited
that
to
our
users,
so
we're
going
to
allow
users
to
deploy
phrases
from
all
environments,
and
this
was
broken
into
a
development
task.
A
So
you
see
here
linked
an
issue
to
the
play
freezes
from
the
API
another.
Finding
sorry
I
forgot
that
previous
slide
here.
This
is
how
I
would
look
like,
so
your
deploy
would
skip
if
you
deploy
fate
escape
if
the
freeze
is
set.
So
nothing
really
bad
happens.
Nothing
really
breaks.
You
should
be
able
to
access
your
latest
deployment
and
then
resume
wants.
A
The
freeze
danger
passes,
and
the
second
exception
that
we
had
is
that
technical
and
non-technical
users
would
be
enforcing
the
deploy
freezes,
and
that
was
correct
and
because
of
that,
we
want
to
inform
those
users
in
the
UI
when
a
freeze
exists
in
gate
lab,
so
that,
even
though
we
are
not
release
manager
for
DevOps
engineer
where
you're
consuming
deployments,
you
can
still
know
that
hey
I
don't
see
my
changes
on
staging
because
a
deployment
freezes
set.
So
this
would
be
a
notification
also
too
large
for
the
embassy.
A
So
it
was
broken
down
into
another
task
and
the
last
one
was
that
there
was
a
comedy
assumption.
That
was
a
conflict
that
people
would
want
to
set
things
and
they
yamo
in
any.
Why
and
in
reality,
as
we
identified
in
the
beginning
two
different
personas,
so
we
will
implement
in
the
demo
and
the
UI
so
that
both
audiences
can
set
the
point
freeze.
A
A
Some
of
the
next
steps,
this
feature
and
being
something
that
yeah
it
has
a
lot
of
possibilities
and
not
everything
fits
in
the
embassy.
So
we
have
an
epic
for
advanced,
avoid
freezes
and
we
are
focused
on
the
expansion
of
the
deploy
freeze
window,
restarting
it
automatically
the
UI
component,
overriding
pipe
freezes
and
a
lot
of
more
things.
So
these
are
all
topics
that
we
still
discuss
in
the
think
accessions.
It
is,
in
a
sequence,
be
a
lot
of
stuff.
A
B
C
A
Let
me
show
my
screen:
I
think
you
just
talking
about
this
one
here
right
yeah,
so
we
do
have
it's
in
the
issue
that
I
say
that
it's
out
of
scope
for
notifications.
So
wherever
we
talk
about
deployments
and
environment,
so
wherever
you
see
that
deploy
face
kit,
we're
going
to
adhere,
deploy
it
and
then
the
reason.
So
one
of
my
suggestions
is
that
the
tool
tip
instead
of
just
saying
scapes,
will
say
skipped.
The
boy
phrase
is
active
so
that
we
provide
more
context
and
also
some
informative
banners
in
the
uie.
B
C
So
Christine,
when
repeating
your
question,
because
I
think
that
right
now
we
have
this
in
the
ammo
file.
So
it
would
be
like
a
manual
action
of
meaning
to
commit
new
code
to
your
mo
file,
but
I
I'm
interested
in
hearing.
If
this
was
more
about
the
UI
interactions
that
were
looking
at
implementing
in
the
advanced
deploy
freezes.