►
From YouTube: Release 3-year vision catch up
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
B
A
C
Live
a
month
ago,
we
met
to
talk
about
this
idea
of
release
through
your
mocks.
So
on
our
operations
section
page,
we
have
this
three-year
target
for
what
we
want
release
to
be
and
out
of
that
discussion
originally
back
in
like
june
or
something
we
came
up
with
two
flows
that
we
thought
would
be
really
good.
The
first
flow
is
like
deployment
approvals
and
then
the
second
flow
or
another
one
of
the
flows
is
deployment
template
plans.
C
So
both
you
hannah
and
dimitri,
worked
on
these
flows
and
you've
come
up
with
really
great
click-through
prototypes.
So
this
meeting
will
be
used
to
walk
through
those
flows
and
then
we'll
recap:
some
next
steps
for
us
to
to
go
through
sound,
good,
I'll,
pass
it
to
you,
hyanna,
to
start
or
to
dimitri
either
one
immediately.
D
D
I
don't
have
the
notes
here
next
to
me.
So
if
I'm
saying
something
that
differs
from
what
this
flow
actually
does
it's
because
I
don't
have
a
reference,
but
here
the
first
page
starts
with
a
notification,
an
email
notification,
so
the
user
receives
an
alert
or
a
request
to
approve
an
existing
deployment.
So
the
pre-deployment
in
this
case
spending
approval
for
gitlab
13.4
on
stage
pre-production.
D
D
So
here
you
see
all
the
steps
for
this
release,
and
I
think
I
couldn't
do
this
with
the
prototype.
But
ideally,
you
would
scroll
to
the
section
where
you
have
to
approve
these
deployments.
D
A
D
No
worries
I'm
just
going
over
the
the
flow
b
on
approving
pre-deployments
for
a
release,
so
when
I
click
on
the
view
app,
I'm
taken
to
the
view
app
of
course,
so
in
this
case
the
project
is
gitlab
and
then
there's
a
notification
here
on
top
that,
maybe
we
can
even
think
about
later
on
changing
the
color,
making
a
little
bit
more
a
little
bit
more.
D
So
the
user
knows
that
they
are
looking
at
a
deployment
for
a
specific,
first
specific
deployment,
and
then
you
have
the
option
to
approve
or
reject
on
this
flow.
If
I
click
approve,
I
have
to
give
a
reason
for
approving
on
this
model.
I
click
approve,
I'm
taken
to
a
merge
request
that
was
created
for
that
specific
deployment.
So
information
here
is
the
same
as
we
saw
last
time.
Pre-Approved
deployment
by
the
comment
is
seen
here
and
then
the
pipeline
is
running.
D
There
are
a
couple
of
other
options
on
this
prototype
if
I
figure
out
how
to
get
to
them
where
the
user
starts
instead
of
approving
here
directly,
you
have
the
option
to
reject.
So
if
I
reject
from
this
page,
for
example,
I
see
the
same
model
give
the
option.
D
You
go
to
your
deployment
and
you
see
that
the
pipeline
did
not
run
or
if
I
am
on
the
view
app
and
there
is
a
feature
flag
enabled
when
clicking
approve
or
reject
the
user
has
to
give
a
sign
off
in
a
sense
of
do
you
want
to
enable
or
disable
this
feature
flag
with
your
approval
of
the
deployment.
So
in
this
case
you
click
approve,
you
approve
and
disable,
and
then
the
feature
flag
is
disabled.
Here
I
think
that's
it
for
the
flow,
a
oh
sorry
for
the
flow
b.
D
The
only
additions
that
I
made
here
were
adding
some
actions
when
the
user
rejects
a
deployment,
so
you
have
the
option
to.
If
you
click
here,
you
might
be
able
to
send
a
notification,
send
a
message
and
send
this
to
someone,
and
I
think
let
me
go
back.
There
is
one
thing
here
in
the
flow:
it's
not
here
I'll.
D
A
A
So
flow
a
is
about
deployments
role
by
other
rollbacks
and
fixing
the
templates
for
those
role
for
those
deployments.
So
for
those
those
run
books,
the
template
stuff
is
in
progress,
but
the
rest
of
the
flow
I
can
show
where
we
begin
with
a
like
an
email
notification
for
the
auto
roll
back,
which
is
in
progress.
So,
let's
let's
jump
right
in
this
one.
A
I
don't
think
you
can
see
it
right
now
because
it
opened
in
the
wrong
view.
Let
me
see
now
we
should
be
able
to
see
it.
Yeah
give
me
a
second
all
right.
So
here
we
are
at
the
email
notification
that
someone
gets
when
there
is
an
automatic
rollback
happen
because
of
a
incident.
A
You
can
see
what
has
happened,
for
example,
this
is
for
the
environment
production.
What
current
deployment
is
what
the
rollback
deployment
is,
and
here
you
can
kind
of
jump
into
the
details,
so
you
can
go
view
the
environment
or
view
the
alert
directly,
but
for
this
demo
we're
going
to
go
into
few
environments.
So
here
we
have
a
different
view
than
what
is
currently
in
the
application
for
an
environment.
A
So
here
we
can
see
all
the
deployments
for
that
environment
and
the
idea
here
is
that
we
can
see
hey,
which
deployments
have
been
rolled
back,
and
can
I
highlight
that,
above
all
others?
So
we
can
see
hey?
Where
are
the
critical
incidents
happening
which
triggered
this
kind
of
rollback?
Here
we
can
see
there's
an
active
deployment
here
currently
at
the
left
top
corner,
and
there
are
some
kind
of
like
some
interesting
details
to
jump
into
for
the
deployment
that
has
been
rolled
back.
So,
for
example,
we
can
see
here.
B
Can
I
stop
you
for
a
minute
sure
the
number
here
next
to
the
auto
roll
back
triggered?
Is
that
going
to
be
the
rollback,
the
id
of
the
current
deployment
or
to
the
one
that
it's
going
to
be
rollback
to.
A
That
one
that's
a
good
question.
Oh
let
me
see.
A
How
to
roll
back
trigger
this
should
point
towards
the
release
that
follows
it
up,
so
the
one
that
is
where
it
is
rolled
back
to.
In
this
case
I
see
this
idea
is
still
the
same,
but
it
should
point
to
the
one
that
is
currently
active,
or
at
least
has
replaced
the
rollback.
A
All
right,
let's,
let's
jump
on
so
when
you
are
looking
at
this
and
there
is
a
red
book
available.
You
can
jump
into
that
runbook
and
see.
Why
and
how
you
know
the
rollout
of
a
release
is
progressing.
This
is
kind
of
relying
on
like
a
template
that
is
still
to
come,
but
we
can
at
least
see
here
kind
of
like
what
happens
in
a
run
book
for
a
certain
release.
A
So
there's
been
certain
stages
already
passed
and
currently
we
are
in
the
rollback
remediation
phase
or
you
can
see
that
hey
there's
been
critical
incidents
happened,
there
are
some
issues
been
created
and
we
can
even
acknowledge
them
here.
For
example
like
like
this,
we
can
say:
hey,
please,
state
your
reasoning
and
confirm
your
acknowledgement
there.
A
A
little
extra
note
here
is
that
we
can
also
see
hey.
Why
did
this
roll
back
happen?
And
how
can
we
edit
this-
and
I
think
this
is
pretty
interesting-
we
can
immediately
go
towards
the
rollback
settings
which
are
in
the
settings
of
the
project
we
can
say
hey
there.
We
have
chosen
for
automatic
rollback
method
which
enables
this
kind
of
like
table,
which
you
are
allowed
to
state
your
rules
for
for
rollback.
So
in
this
case
for
critical
incidents
we
roll
automatically
back
to
the
less
successful
deployment.
A
This
is
something
we
can
elaborate
on
and
kind
of
you
know
and
progress
on
in
terms
of
like
what
is
what
is
inevitable
and
functionality,
and
I
think
this
is
kind
of
interesting
to
see
like
hey
how
many
rollbacks
have
happened
since
I've
been
created
and
some
metadata
that
might
might
make
a
lot
of
sense
so
to
go
back
to
the
earlier
page.
We
also
have
some
slack
modifications,
which
means
like
hey.
A
If
there
is
a
slight
notification,
we
can
see
that-
and
I
don't
have
the
notes
with
me
here
as
well-
we
can
see
hey
a
certain
issue
has
been
created
for
a
certain
incident
to
resolve
that
callback,
which,
in
this
case,
is
this
additional
slack
notification
to
go
back
a
little
bit
earlier.
I
want
to
show
another
slack
notification
as
well,
so
I'm
going
to
go
to
the
first
slide
view
the
environment
and
then
click
here
as
well.
We
can
see
at
the
same
time
that
the
previous
view
is
going
on.
A
A
Let
me
see
this
to
go
back
to
the
original
view.
There's
one
more
thing
to
show
here,
which
is
there,
are
automatically
issues
created,
which
can
also
be
seen
from
the
deployments
view
directly.
We
can
click
on
it.
We
can
immediately
say
hey.
These
issues
are
are
important,
let's
assign
an
assignee
or
a
milestone
to
it,
which
makes
it
that
much
more
actionable
right
within
the
context
where
you
need
it
that
is
kind
of
it
unless
I'm
mistaken.
A
So
let
me
do
a
brief
view
of
the
vision,
markups
here
and
I
think
we've
had
it
all
here.
We
have
the
acknowledgments
and
the
settings
here.
Yes,
so
that
was
flow.
A
the
the
thing
that's
still
to
be
added
is
to
edit
the
runbook,
template
and
kind
of
make
that
part
of
this
flow,
which
allows
us
to
kind
of
you
know,
define
those
rules
within
the
runbook
itself.
Instead
of
referring
back
to
the
project
settings
and
that's
it
I'm
going
to
stop
my
sharing
of
my
screen.
D
D
Sorry
with
the
life
cycle,
yeah
the
part
where
you,
when
you
go
to
you,
click
to
go
to
the
rollback,
and
you
have
some
life
cycle
steps
we
replaced.
A
C
Yeah,
so
I
I
added
a
couple
comments:
there's
one
a
typo
on
that
same
life
cycle,
page
rollback
versus
roll
back.
C
Double
l,
but
otherwise
I'm
very
impressed
with
this.
I
think
it's
highly
actionable.
It
captured
the
high-level
thoughts
that
we
talked
to
you
about,
so
I'm
really
really
excited
and
impressed
by
by
this
vision.
Here,
ori
do
you
have
any
other
topics,
while
we
have
time
here,
if
you
wanted
to
work
through
with
dimitri.
B
No,
I
thought
it
was
awesome.
I
was
also
really
happy
to
see
that
you
incorporated
those
new
comments
that
I
added
in
like
no
time
so
you
brought
us
back
to
the
settings
to
see
the
definitions
of
the
of
the
auto
rollback
because
that
may
be.
You
know
something
that
you're
constantly
auto
roll
backing
and-
and
you
might
want
to
fine
tune
that
so
I
thought
that
was
really
awesome.
C
So
from
a
next
step
perspective
ori,
I
think
you
and
I
have
a
one-on-one
on
our
calendar.
We
can
talk
through
how
we
want
to
position
this
in
like
a
recording
to
present
and
distribute
to
the
field
and
sales
team,
and
then
I've
already
opened
up
an
mr
to
embed
these
prototypes
as
an
iframe
into
our
release
section.
C
So
I
think
that
would
be
a
really
cool
accessible
way
for
people
to
just
see
all
the
work
that
hayana
and
dimitri
have
done
and
they're
clickable,
so
the
people
would
be
able
to
interact
with
them.
I
think
that's
a
really
great
way
to
tangibly
show
sales,
some
some
things
that
we're
going
toward.
C
D
Love
that
I
love
making
the
design
assets
like
the
end
deliverable
I
just
like,
let's
clean
up
that
file,
maybe
a
little
bit
before
yeah.
What
do
you
think.
A
Yeah
we
should.
We
should
just
do
some
cleanup,
also
to
make
it
a
little
bit
more
clear
how
the
flow
inside
of
the
work
file
is
going,
because
what
I've
done
for
prototype
a
or
flow
a
is
that
for
this
slack
notification,
there's
not
a
direct
link
where
you
go
towards
slightly,
because
these
things
are
kind
of
happening
in
parallel.
A
You
can
click
anywhere
in
the
view,
and
it
will
take
you
to
this
absolutely
like
new
context
and
then,
when
you
click
that,
again,
you
go
back
to
the
original
view
kind
of
like
to
be
able
to
jump
through
to
that
in
the
clickable
prototype
yeah
a
little
bit
more
intuitive.
At
least
that's
how
I
was
thinking
about
it.
D
D
I
don't
think
so
when
you
no,
because
maybe
maybe
we
can
just
put
like
an
index
and
say
these
are
the
pages
and
then
people
can
either
navigate
by
clicking
or
just
you
know,
see
the
list.
A
D
All
right
I'll
do
that
since
you're
still
working
on
right,
you
have
some
updates
to
do
I'll.
Do
that
I'll
make
this
the
general
update,
so
we
can
wrap
it
up
julio.
A
Yeah
and
a
bit
of
a
request
towards
jackie
and
orit
on
the
pages
that
have
not
yet
been
created.
Coming
back
from
out
of
office,
I
was
looking
a
little
bit
edited
like
what
was
this
exactly
again.
I
need
a
little
bit
more
context,
so
perhaps
if
you
view
that
step
and
can
explain
right
now,
what
kind
of
like
thing
you're
expecting
or
do
a
small
recording
of
yourself
like
hey?
These
are
my
expectations
for
this
view.
I
expect
from
this
street
to
go
into
that
view
because
of
these.
A
C
So
this
would
be
the
deployment
template
machine
that
I
think
ori
is
in
your
your
vision.
It's
separate
from
a
run
book.
It
would
be
like
I
I
I
could
envision
this
being
since
we,
since
we
have
time
in
this
meeting.
I
think
we
can
try
to
cover
this
off
here.
I
can
envision
it
being
like
a
p.
A
bunch
of
pick
lists
allow
people
to
pick
different
resources
and
then
the
output
is
a
yaml
file
that
they
get
to
copy
paste
into
their
project,
but
I'll,
let
or
it
kind
of
it's.
B
B
B
B
Maybe
I
don't
know
if
it's
that
expensive,
because
the
the
yaml
editor
from
what
I
understand
is
supposed
to
be
like
dragging
different
bits
and
pieces,
you
know
to
create
a
full
file.
This
may
be
just
something
that
we
want
to
add
on
top
of
this
specific
flow,
so
I
wouldn't
go.
C
And
I
could
also
see
this
being
really
focused
on
enabling,
like
review
apps
inside
of
your
project
or
adding
the
release
generation
step.
So
if
we're
really
like
narrowing
in
on
all
the
ammo
activities
in
the
release
stage,
I
can
see
it's
enabling
deploy
phrases
easily,
enabling
so,
instead
of
people
having
to
go
to
the
ci
cd
examples
and
copy
paste,
that's
already
built
into
the
the
front
end
of
gitlab,
so
they're
just
copying
pasting
that
snippet
into
their
ammo
file
or
even
better.
C
A
It
sounds
very
doable.
It
reminds
me
a
bit
of
like
what
github
is
doing
with
actions
yeah
with
actions
where
you
have
predefined,
yaml
snippets,
which
accept
variables,
etc
to
kind
of
personalize
it
and
make
it.
You
know
accepted
within
your
own
yaml
or
you
know,
configuration
sounds
good.
B
I
actually
think
that
if
we
could
add
that
as
part
of
the
run
book
that
could
be
really
interesting,
jackie.
So,
like
you,
have
steps
in
the
run
book
and
that
just
automatically
does
everything
for
you.
So
you
decide
you
have
to
have
a
review
app
and
right
because
we
have
like
different
approval
stages,
but
maybe
also
building
up
the
entire
pipeline
could
be
part
of
the
runbook.
C
C
So
here's
a
flow
to
be
really
explicit
here.
I
would
have
a
single
screen
that
shows
the
mechanics
by
which
you
would
add
an
attribute,
so
you
could
use
release
generation
from
the
yaml
file
or
deploy
phrases
or
review
apps
any
of
those
as
as
an
option
and
then
add
add
a
section
or
a
visualization
on
this
view
for
import
yaml
file
to
project
selector
and
then
maybe
a
check
box.
That
says
add
to
my
run
book
template
and
then
your
click
through
on
that
check
box.
C
It
pulls
into
the
run
book
template
as
a
step
inside
of
the
plan
phase
of
a
run
book,
and
it
adds
that
little
snippet.
It
says
per
review
app,
for
example.
So
if
we
want
to
like
really
dig
in
here,
I
think
we
should
talk
about
enabling
a
review
app
from
from
this
view,
given
that
that's,
like
a
part
of
this
whole
continuous
delivery,
it's
cloud
native,
it
fits
in
with
our
greater
story.
B
I
actually
like
to
take
it
even
a
step
further,
so
you're
talking
a
lot
about
the
plan
or
even
the
beginning
of
the
pipeline.
What
if
we
could
even
add,
like
the
really
nice
functionalities,
like
advanced
appointments,
canary
incremental
rollout
and
have
like
part
of
the
runbook,
be
like
okay,
I
need
to
get
a
feedback
loop.
B
I
start
the
rollout
of
10
now
I
want
to
view
you
know
the
metrics
and
it
can
be
automatic,
but
it
can
also
be
a
manual
approval
where
you
say:
okay
now
expand
this
to
20
to
30
so
like
having
that
also
as
part
of
the
runbook
that,
like
automatically
increases
the
the
audience,
that's
getting
this
functionality
in
this
deployment.
A
Like
the
distribution
is,
is
the
distribution
rules
are
part
like
are
described
within
the
run
book
and
can
be
activated
on
with,
like
a
single
click
like
all
right?
This
this
threshold
has
been
been
crossed.
The
run
book
states
like
40.
We
can
either
say
like
all
right,
we'll
automatically
do
that
or
there's
some
manual
acknowledgement
needed
to
get
to
that
next
step.
C
So
I
think
that
could
be
a
really
cool
part
for
that
deployment.
Builder
machine
screen
like
showing
showing
that
you're
enabling
canary
incremental
rollout
in
that
deployment
builder,
then
that's
what
gets
copy
pasted
into
the
ammo
file,
but
also
is
a
discrete
step
inside
the
deployment
plan.
I
think
that
that's
a
really
great
use
case
and
can
show
the
what
you
were
asking
for
dimitri
was
the
explicit
screen
and
then
the
next
step
for
that.
So
I
think
that's
perfect.
A
C
And
I
love
that
we're
touching
on
all
aspects
of
the
three-year
vision
which
is
like
this
advanced
deployment
perspective,
because
we
have
feature
flags
and
we
have
run
books
included
in
there
and
in
the
other
flow.
I
think
this
one
covers
the
whole
advanced
deployment
and
cd
life
that
we
haven't
really
dug
into.
So
I
think
that's
really
good
to
have
this.
C
All
right,
well
I'll!
Let
you
all
let
us
know
when
you're
up
when
your
prototypes
are
updated
before
I
merge
the
change
to
the
handbook,
because
that
way,
we're
not
merging
something
that's
in
flight
and
making
it
public
before
we're
ready
for
it
and
then.
B
I
think
in
the
spitter
spirit
of
iteration
jackie,
we
could
probably
put
this
out
there.
Even
I
mean
fix
the
typos,
but
but
even
before
we
add
these
all
all
these
additional
things,
because
I
think
in
this
iteration
it
will
definitely
show
the
direction
anyway,
and
I
think
that
people
would
really
appreciate
it.
Yeah.
A
C
I'm
perfectly
fine
merging
it
forward.
That's
great,
I
just
didn't
want
to
didn't,
want
to
merge
it
and
then
have
to
update
the
embed.
If
they
made
changes
in
the
embed
code
changed
because
then
it
would
break
and
people
would
be
like.
I
can't
see
it.
You
know
that
was
my
word.
A
D
D
I
think
I
think
the
only
thing
I
would
ask
for
the
the
embed
is
that
I'm
not
sure
why
they're
like
full
screen-
maybe
we
can
just
see
if
they
can
start
from
a
specific
page,
because
they
just
show
two
different
things
on
the
review
app
like
this.
What
do
you
mean
like
this?
That's
how
they
show
right
now
they
start
from
this.
One
starts
from
this
view,
and
this
one
starts
like
this,
and
it's
not
so
usable.
A
Oh,
you
can
go
into
your
into
the
prototype
settings
in
your
sigma
document
and
there
you
can
select.
Let
me
see,
show
prototype,
there's
a
device
section
at
the
top,
where
you
can
select
like
a
custom,
size
or
presentation,
or
none.