►
From YouTube: 2021-05-10 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
A
Yeah
you
joined
like
the
kind
of
like
nightclub
daytime
rave
cool,
that's
a
different
meeting
hello.
So
I
think
that's
only
us
not
today.
Henry
is
taking
his
time
in
lieu
after
pg
upgrade
robert's
off
eurics
on
shouting
this
week
and
graham
is
asleep.
A
So
so
happy
monday,
I
have
just
put
the
link
in
for
mttp.
We
still
don't
have
any
data
coming
through
from
may.
It
should
arrive
soon.
I'm
expecting
it
looks
like
the
lag
is
like
some
days
on
this
stuff,
so
hopefully
we'll
get
that
coming
through
soon.
I
also
haven't
done
any
difference.
I
haven't
done
anything
to
the
mttp
target.
A
So
when
I
go
through
the
blockers
from
last
week,
we
we
may
be
in
a
position
where
we
can
review
whether
we
want
to
put
the
target
back
to
12
hours,
but
I
think,
since
we
haven't,
got
data
for
now,
we'll
just
wait
for
that
stuff
to
catch
up,
and
then
we
can
review
together
and
make
a
decision
so
announcements
scabic.
You
have
the
first.
B
A
B
B
B
I
mean
I
have
a
broken
dishwasher
that
is
doing
beep,
beep
beep
every
two
seconds,
so
I
definitely
prefer
having
weird
chirping
instead
of
this
yeah.
A
Awesome
good,
yes,
take
some
time
off.
In
fact,
quite
a
lot
of
people
have
time
off.
Actually
this
week,
I've
got
them
in
here
so
robert's
out
till
thursday.
So
he's
got
monday,
tuesday,
wednesday
off
henry's
out
today,
tomorrow
and
thursday
myra
you
possibly
have
some
time
not.
D
A
A
Okay,
fair
enough
awesome,
cool,
okay
sounds
good,
so
yeah
I've
put
on
b.
So
just
a
reminder:
we've
got
the
okr
issue
open.
If
you
also,
if
you
want
to
respond
to
anyone's
stuff,
then
please
do
like.
I
will
add
some
henry
and
graham
still
have
some
comments
to
add
I'll.
A
Now
I
was
thinking
particularly
of
following
this
whole
pagination
thing
on
the
on
the
emrs
like,
let's
like
please
provide
some
feedback
on
here.
Even
if
it's
like
you
know,
you
don't
have
a
strong
opinion,
but
I
think
really
great
that
we've
been
asked
on
this
one.
So
please
please
do
schedule
in
some
time
in
the
next
few
days.
D
Is
this
one
associated
with
the
pagination
in
the
compare
section?
No
okay.
A
But
I
think
like
this
is
pretty
much.
I
think
it's
the
first
time
I've
seen
that
we've
been
asked
about
do
a
usability
thing
as
like
a
as
a
customer,
so
which
is
great
so
yeah.
Let's,
let's
invest
in
that,
so
hopefully
we
get
more
of
them
awesome.
So
first
discussion
item,
so
I
thought
we'd
be
useful
for
us
to
just
catch
up
and
make
sure
we've
got
the
rollback
stuff.
A
So
I
know
the
big
kind
of
outstanding
task
we
have
to
do
is
get
our
cr
in
front
of
marin,
so
he
can
approve
it
and
then
once
we
have
that
we'll
be
able
to
schedule
it.
So
a
few
things
that
we
need
to
work
out,
I
think,
before
we
can
get
it
in
front
of
marion.
So
first
one
is
the
discussion
around.
What
do
we
do
following
the
rollback
so
some
options
we
could
just
run
the
post
deployment
migration.
A
We
could
no,
not
that
one
we
could
do
redeploy
which
actually
scabic.
I
liked
your
reasoning
as
to
why
that's
also
a
bad
idea,
so
the
third
option
is
basically
just
deploy
the
next
package.
A
C
I
think,
from
a
technical
standpoint,
once
we
got
the
rollback
completed,
we've
completed
the
test
at
that
point.
It's
just
a
matter
of
what
we
choose
to
do,
use
it
moving
forward.
I'm
trying
to
shy
away
from
using
the
package
we
just
removed
because
that's
not
going
to
be
the
workflow
when
we
recover
from
an
incident.
B
C
So
there's
not
we're
going
to
be
waiting
a
very
long
time
to
have
anything
available
to
us
if
we
want
to
continue
the
test
or
finish
up
the
test
afterwards,
that's
my
concern.
B
A
A
B
Well,
I'm
thinking
that
if
we
want
to
move
forward
for
the
sake
of
moving
forward,
we
can
just
I
mean
thinking
about
today
right,
so
we
promo,
we
promoted
7
a.m
package,
not
the
11
one,
so
the
11
package
is
still
to
be
promoted,
is
in
making
time
right
now.
I
think
yeah.
I
should
be
making
time
right
now.
So
if
we
cancel
post
deployment
migration
for
the
seven
package,
basically,
when
we
complete
rollback,
we
will
be
ready
to
deploy
1120.
B
yeah,
I
mean
say,
11
20,
because
usually
we
tag
around
11
20,
I'm
looking
at
text
time
stamp
of
text,
so
we
create
a
branch
on
11
and
around
11
20.
We
tag
it
so
yeah.
B
Of
the
day
it
could
be
first
of
a
second,
so
we
had
two
deployment
this
morning,
but
because
the
the
there
was
a
failure
in
3am
package,
so
I
promoted
yesterday
evening
package
and
then
I
promoted
directly
the
seven
package.
In
theory
I
could.
If
everything
goes
smoothly,
I
could
promote
3am
and
7am.
A
B
A
A
And
then
we'll
have
the
11th
one
we'll
be
ready
to
deploy
ready,
also
because
tomorrow
robert
will
still
be
out,
which
means
we
actually
can
start
the
rollback
a
little
earlier,
because
we're
all
online
like
a
good
couple
of
hours
earlier
than
robert.
B
B
I
think
it
was
kind
of
so
I
think
that
in
my
first
issue
was
kind
of
stressed
out
that
we
should
roll
back
to
where
that
and
roblox
are
rolling
forward
to
whatever
was
the
state
before.
But
I
think
that
this
is
a
good
point
that
can
help
us
to
let's
say
I
would
like
to
decouple
the
two
things.
So
the
test
is
concluded
when
the
rollback
is
done.
B
There's
no,
so
coming
back
to
so
rolling
back
changes
is
just
putting
cannery
back
in
line,
and
I
mean
canary
cannot
be
back
in
line
because
he's
in
the
wrong
version,
but
yeah
kind.
We
should
work
out
what
we
want
to
do
with
cannery
and
resuming
the
regular
operations.
B
But
I
would
like
to
extend
a
tiny
bit
the
window
in
which
we
are
running
the
rollback
version,
because
during
a
real
incident
we
will
not
have
a
fix
in
a
matter
of
seconds
right,
so
I
think
it
would
be
better
to
leave
it
running.
30
minutes,
one
hour
kind
of
a
baking
time,
so
we
say
yeah
is
it
this
rollback
really
works
and
we
can
reliably
be
in
in
rollback
state.
B
Can
trigger
those
fine
makes
makes
sense
on
the
just
on
the
idea
of
running
post
deployment
job.
This
will
be
a
problem
because
post-deployment
job
are
designed
to
run
after
the
code
is
rolled
out,
but
here
the
code
is
not
rolled
out.
B
B
A
A
B
A
Then
we
have
a
seven
o'clock
branch
that
will
get
promoted
to
deployment
with
a
cancelled
post
deployment
migrations,
and
at
that
point
we
have
a
window.
We
can
roll
back
from
the
11
o'clock
branch
will
get
created.
I
assume
it'll
be
created
before
we
roll
back,
because
it's
still
early
days.
B
A
A
Yeah,
that
makes
sense,
yeah,
cool,
okay
and
then.
A
You'll
probably
have
to
run
them
before
you
can
do
the
seven
o'clock
promotion
right
because
the
pipeline
won't
have
completed,
but
anyway
you
you
can
manage
it.
You
can
like
go
so
then
we'll
do
somewhere
between,
like
I
say,
it'll,
be
like
around.
B
A
Okay,
okay,
so
around
say
like
around
one-ish,
we'll
do
a
roll
back.
We
should
be
ready
and
then
say,
like
whatever
time
like
say,
like
roll
back
completed
and
then
yeah
like
what
should
we
say
like
one
hour
like
30
minutes?
How
long
do
you
want
to
run
this
role?
Yeah.
B
Package,
for
I
mean
it
really
depends
on.
I
mean
it
will
be
two,
so
we
take
around-
let's
say
two
hours
for
running
group,
but
this
is
not
correct.
Probably
we
take
less,
but
let's
consider
two
hours
for
running
the
road
back,
so
from
1am
1pm
we
go
to
3pm,
which
is
five
of
my
local
times.
So
it's
close
to
my
day
I
mean
we
can
we
can
have
another
30
minutes.
One
hour
I
mean
both
are
fine.
C
C
A
C
A
Yeah
we
should
do
that
yeah
and
then
the
deployment
of
like
so
this
will
be
of
the
11
or
later
brunch,
depending
on
time.
A
A
Yeah
would
somebody
mind
updating
the
cr
so
that
it's
got
these
details
so
that
when
we
look
through
the
roll
back
stuff,
we
also
know
like
we're
going
to
execute.
Well,
we
have
the
xqa
task
in
there
and
know
that
we
need
to
run
for
a
period
of
time
and
then
our
next
step
will
be
deployment
of
our
future
package.
D
We
are
just
missing
the
change
reviewer.
A
D
A
A
Would
be
great
to
do
that
today
if
we
can
yeah,
because
also
following
that,
we
once
we
have
marin's
approval.
We
need
to
let
the
engineer
on
calls
know
and
we're
going
to
it's
a
slightly
unfortunate
time
because
we're
going
to
cross
over
the
shift
change.
But
I
think
we
should
just
work
around
that
right
and
just
let
both
the
the
first
and
the
second
know
like
we,
I
mean
we'll,
be
managing
this,
so
I
don't
expect
or
need
very
much
help
from
them,
but.
B
A
Yeah,
so
we
should
let
them
know
as
well
today,
but
we
I
think
we
need
to
get
married
well,
we
can,
I
guess
we
can
let
them
know
with
manager
approval.
Do
you
scrub
it
do?
You
know
who's
actually
on
call
tomorrow.
A
Great
good
stuff,
the
other
thing
I
realized
we
didn't
talk
about
in
timeline
is
what
we
do
with
canary,
so
canary
will
get
drained
at
around
one
ish.
Do
we
want
to
just
let
the
follow-on
deployment
bring
it
back.
C
Exactly
so
let
it
get
deployed
to,
but
then
we'll
have
to
bring
it
out
of
maintenance
mode
ourselves
after
the
last
deployment.
If
we
don't
do
that
at
the
right
time,
we
might
have
to
re-kick
qa
just
to
make
sure
it's
hitting
the
right
servers.
B
B
B
B
I
mean
this
is
a
question
here,
which
is
maybe
so,
which
is
another
question,
I'm
doing
a
statement.
Maybe
it's
better
if
we
cancel
cannery
deployment
as
well
on
that
package
yeah,
so
that
we
are
completely
in
control
of
timing.
I.
B
C
B
A
Just
go
for
it
yeah!
No,
I
think
it
also
this
one.
It's
it's
giving
people
confidence
as
well
that
we've
really
thought
this
one
through.
So
this
is
one
of
the
easiest
ways
to
demonstrate
that
we've
all
the
work
we've
done
is
actually
that
we
know
what's
involved
and
we
know
all
the
steps
and
things
like
that.
So
so
what.
D
A
Yeah,
I
think
we
try,
because
the
only
thing
following
now
is
release
stuff
right,
so
I
think
we
should
try
if
we
like,
we've
got
definitely
this
week,
maybe
monday,
depending
on
how
things
are
going
for
release
prep
right,
but
I
think
we
should
try
and
like
we
have
to
just
repeat
these
steps.
Unfortunately,
every
day,
if
we
don't
get
one
tomorrow,.
A
Awesome,
okay,
well,
just
give
a
shout
if
there's
anything,
that's
unclear
about
like
as
we
prep
the
stuff
today
or
if
there's
any
difficulties,
because
the
main
thing
will
be
to
try
and
get
this
in
front
of
marin
today.
So
we
can,
but
I
mean
worst
case-
we've
still
got
tomorrow
morning
right,
so
we
can.
We
can
do
some
of
the
prep
steps
tomorrow
and
we
just
need
pr
approval
before
like
one
but
be
good
to
give
more
notice.
A
If
we
can
awesome
sounds
good,
so
I
might
move
b
over
to
slack,
so
we
can
do
async
just
because
we
are
running
tight
on
time.