►
From YouTube: 2021-06-01 Delivery team weekly EMEA/AMER
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
For
a
moment,
then
robert,
I
thought
that
was
your
new
house
and
now
I'm
really
disappointed.
I
hope
this
is
like
interior
decor
or
like
ambitions.
That'd,
be
amazing,
awesome,
so
welcome
everyone
find
the
agenda
cool
so
say:
mttp
is
in
there,
like.
I
think
it's
looking
pretty
healthy
incident
related
stuff,
obviously
going
on
we'll
keep
mttp
at
24
hours
until
we
have
two
weeks
without
incidents
which
we
have
not
had
yet.
A
So
the
reason
for
doing
that
is
just
to
make
it
really
clear
is
when
we
go
to
the
key
meetings
each
month
and
we
talk
about
the
department
performance
indicators,
there's
often
questions
about.
Why
is
mttp
higher
or
lower
this
month,
so
by
setting
that
target
a
little
bit
higher,
it
makes
it
very
clear
that
at
the
moment
we're
seeing
incidents
impacting
things
awesome,
so
I
won't
read
all
the
announcements,
but
I
do
want
to
say
thanks
maira,
he
got
a
super
fun
handover
cover
shift.
A
So
thanks
for
dealing
with
all
of
that,
but
also
thanks.
Everyone.
A
I'm
getting
more
superstitious
as
the
months
roll
on,
but
also
thanks,
everyone
for
everyone
who
got
involved
last
week
and
helped
out
all
the
incidents
and
change,
vlog
work
and-
or
things
like
that,
like
I
said
to
alessio
earlier,
if
all
we
do
in
14
in
this
month
in
june,
is
get
14.0
out
safely.
We've
you
know
we've
achieved
so
thanks
for
for
jumping
in
and
helping
out
just
visibility.
Tomorrow
we
have
a
hard
pcl
in
place.
A
I'm
gonna
use
the
notify
to
broadcast
that
out,
so
that
developers
are
also
aware
that
they're
not
gonna
get
a
staging
update.
They
won't
be
able
to
join
with
feature
flags,
but
we
should
also
pause
auto
deploys
at
the
end
of
this
today.
A
Oh
there's
a
change.
I
need
to
dig
out.
This
is
a
half-finished
sentence
because
I
didn't
get
around
to
finding
the
change.
There's
a
terraform
change
going
out
that
if
anything
else
changes
at
the
same
time.
D
A
Or
I'll
put
it
in
the
notified
message
as
well,
so
just
to
make
it
super
safe.
It's
actually
not
happening
until
quite
late
in
the
day,
but
I
think
it's
fine,
we'll
just
play
it
safe
and
then
we'll
at
least
know
that
git
lab
was
fully
stable
before
this
change
started
in
case
they
do
stay
stuff.
A
A
Awesome-
and
I
just
see
it's
just
literally-
for
visibility-
I
just
read
this
issue
today
and
found
this
slack
channel,
but
basically
it's
it's
going
to
give
some
visibility
into
things
that
are
using
the
release.
Runners
so
hopefully
we'll
be
able
to
start
graham's
working
on
pushing
these
things
away,
blocking
them
from
access
so
that
we
hopefully
won't
keep
having
this
problem.
Where
we
end
up
queuing
deployments.
A
Awesome
so
number
one
as
I
mentioned
so
I
manually
track
deployment.
Blockers.
Apologies
because
I
haven't
had
time
in
the
last
couple
of
weeks
to
do
this,
so
this
is
also
out
of
date,
so
I
will
catch
this
up,
but
it
is
a
bit
of
a
pain
to
pull
the
data
together.
So
the
bit
that's
tricky
really.
A
Is
it's
easy
enough
to
find
the
incidents,
but
what's
tricky
is
trying
to
calculate
like
how
long
and
which
environment
ended
up
becoming
blocked
as
a
result
of
these
just
because
it
requires
going
through
several
slat
channels?
A
So
there
are
a
couple
of
ideas
on
the
bottom
of
that
issue
already,
but
I
was
wondering
like
how
can
we
make
this
more
automated?
It
doesn't
have
to
be
100
automated,
but
is
there
a
way
to
somehow
automate?
I
guess
the
the
fact
that
things
have
become
blocked
so
like
hey,
staging
a
spot
for
two
hours
or
productions,
but
for
three
hours
and
just
have
some
way
of
accessing
that.
B
So
this
is
something
then
we
have
to
be
good
in
giving
up
today
right
because
the
the
template
can
be
there,
but
if
we
don't
feel
it
all
right.
So
this
is.
C
I
think
this
is
a
long
standing
issue
with
tracking
times
for
incidents
right.
This
is
not
only
for
us,
but
in
general,
I
think
the
idea
was,
you
know,
using
labels
putting
in
certain
texts
places
like
started
here,
stop
there
or
in
the
it's
in
a
review
section.
C
If
you
have
a
review
to
put
in
a
summary
of
for
how
long
something
customers
were
impacted
and
that
oil
fields
not
really
nice,
and
then
there
was
this
idea
of
coming
up
with
automation
around
incident
management
started
by
arma
at
this
time,
which
later
then
was
replaced
by
what
is
now
called
woodhouse
yeah
woodhouse,
and
I
think
if
we
have
a
way
to
automate
this
in
a
better
way,
then
I
think
you
should
look
into
woodhouse,
maybe
because
this
is
the
thing
which
is
creating
incidents
from
slack
and
and
so
on.
C
But
I
don't
know
if
we
how
we
could
track
these
metrics,
because
in
most
cases
it's
really
a
manual
assessment
to
figure
out
how
for
how
long
something
something
specific
was
blocked.
Even
if
you
declare
an
incident,
it's
not
clear
when
it
really
started
right
so.
B
Can
we
check
deployment
pipeline
instead,
so
I'm
trying
to
think
to
think
around
the
problem
right.
So
the
effect,
so
we
are
tracking
for
how
long
something
was
blocked
and
blocked
mean
that
we
were
not
able
to
deploy.
B
B
B
D
B
E
B
Columns
which
are
gprd
blocked
and
gstg
blocked.
This
could
be
just
labeled,
so
we
search
for
incident
that
have
the
deployment
related
label
and
then,
if
they
they
may
or
may
not
have
gprd
blocked
and
gstg
blocked.
And
then
we
we
pull
out
this
information
track
for
how
long
things
were
blocked.
B
E
B
Can
just
we
can
go
into
finer
details
like
one
hour
and
a
half
or
things
like
that?
Otherwise
we
need
thousands
of
labels,
but
maybe
I
mean
it's
more
than
enough.
I
don't
know
and
it's
easier
to
how
to
label
than
just
filling
in
the
details
and
because
it's
like,
when
I
open
one
of
this,
then
I
say
I
have
to
do
the
review
and
you
have
to
open
it
and
edit
and
re-read
the
template
and
things
like
that.
But
if
we.
E
B
C
Could
we
maybe
more
often
run
the
production
check
task
to
see
when
we
are
blocked
because
of
production
checks
and
then
maybe
correlate
this
with
ongoing
incidents
at
the
same
time
or
just
just
if
we
are
blocked
on
production
deployments,
but
we
can
differentiate
between
incidents
and
change
requests
right.
Can
we.
A
A
Okay,
how
about
I
summarize
these
approaches
and
sort
of
there's
a
couple
of
ideas
on
that
issue
already
how
about
I
summarize
these
out
into
in
that
issue?
We
see
you
see
what
graham
thinks
as
well
get
this
async
scalpex
turned
into
a
kitten.
This
is
amazing.
A
Cool
and
then
for
b,
so
I've
created
an
issue
to
announce
14.0,
there's
nothing
too
drastic
in
there.
Just
what
I'm
going
to
do
with
this
is.
I
want
to
make
sure
people
are
aware
that
we're
starting
the
prep
a
little
bit
earlier,
and
then
we
use
this
we'll
link
this
into
a
broadcast
message
we
can
send
around
just
this
is
going
to
be
such
an
interesting
release.
If
anyone
misses
the
release,
they
potentially
have
to
maintain
a
feature
for
12
months.
A
So
yeah
thanks
myra
I'll
add
that
I
was
going
to
look
it
up
and
then
you
can
tell.
I
didn't
so,
have
a
look.
If
there's
any
thoughts
on
either
additional
stuff
we
should
put
in
there
or
if
you
can,
if
you
can
think
of
any
ways
to
make
it
easier
to
read
or
clearer,
whatever
feel
free
to
edit
and
suggest
stuff.
A
Awesome
henry.
C
C
You
know
mental
mapping
right,
because
the
documentation
is
excellent,
but
it's
composed
of
so
many
different
pieces
and
when
I
started
I
didn't
have
enough
context
to
really
or
put
all
the
pieces
together
and
with
drawing.
I
try
to
just
do
that
and
it
helped
me
a
lot
to
do
it,
but
I'm
not
sure
if
this
is
helpful
for
others,
I'm
not
sure
what
I'm
missing
and,
of
course,
it's
incomplete.
It's
just
containing
the
most
basic
parts
for
me
to
be
able
to
understand
how
our
deployment
and
release
management
works
in
ways.
C
It's
missing
a
lot
of
details.
Of
course,
I
can't
put
the
full
security
release
workflow
into
that
one
picture.
That
would
be
a
little
bit
too
much,
I
think,
but
I
hope
it
helps
just
to
get
started
so
looking
for
feedback
or
corrections
where
I
missed
something
that
would
be
great.
We
can
discuss
this
in
vmr
async.
A
C
You
caring
about
it
directly
in
the
drawing
if
you
want,
but
also,
if
you
think
something
could
be
changed
which
I
can
do,
then
this
can
be
discussed
in
the
mr,
as
you
feel,
I
mean
it's
anywhere.
You
get
a
google
draw
drawing,
so
it's
not
really
a
version
managed,
but
doing
this
in
memory
or
something
that
would
be
a
little
bit
too
much.
I
think
so.
I
think
this
works
better.
A
Cool
sounds
good
thanks.
A
lot
awesome
is
there
anything
else,
and
I
want
to
bring.