►
From YouTube: 2021-11-22 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
Good
morning,
new
glasses.
A
So
I
badly
need
to
go
to
the
opticians.
It
was
one
of
those
things
that
was
like
I
needed
to
do.
Pre-Covert.
A
Yeah,
well,
they
were
closed
here
for
quite
a
long
time
they
opened
and
I
hey
I've
got
like
an
amazing
optician
who
weirdly
I
had
as
a
kid
and
because
I
grew
up
around
where
I
live
and
then
I
moved
away
and
I
came
back-
and
I
was
like
oh
okay,
great,
I
go
back
to
this
place,
he's
a
fantastic
opposition
and
they
do
quite
a
good
job
of
like
when
you
see
them
like
doing
continuations
they're
like
oh
well,
six
months
ago,
we
talked
about
this,
and
so
you
get
great
but
he's
also
slightly
like
he's
a
very
softly
spoken,
very
lovely
guy,
and
I
just
don't
want
to
be
that
close
to
another
human
and
I
just
think
wearing
face
masks
and
everything
is
going
to
be
the
most
awkward
interaction
I've
ever
heard
of.
A
C
A
Awesome,
let's
get
started,
so
thank
you
for
adding
mttp
into
the
agenda.
Scuba.
D
D
A
Yeah
awesome
there's
one
thing
as
well:
I
noticed
we
were
chatting
with
davis
alessio
raised
an
issue
to
question
mttp
and
davis
was
chatting.
One
thing
I
noticed
was
I
I
wonder
if
mttp
is
calculating
first
around
canary
accurately,
so
anyway,
I'm
going
to
take
advantage
of
ptl
this
week
and
and
take
a
little
look
at
that
closely
and
just
see
there
was
some
to
what
looked
to
me
unusual
spikes
on
this
monthly
calculation
versus
the
weekly
one.
So
but
overall
it's
looking
healthy,
that's
our
lowest
mttp
bar.
A
D
The
one
thing
at
least
I
am
not
satisfied
with
this
chart,
is,
I
don't
know
which
of
these
bars
refers
to.
What,
like
you
know,
there's
been.
Was
this
the
third
week
of
november
fourth
week
of
november,
some
ish
there's
one
bar
in
november,
is
right
under
one
bar.
I
don't
know
what
this
chart
is
referring
to.
A
That's
a
great
question,
actually
yeah,
so
actually
what
I'll
do
then
so,
based
on
the
issue
with
seo
rates,
we
probably
understand.
I
say
we
I
I
have
admit
right,
so
I
can
also
see
the
code.
I
probably
understand
70ish
percent
of
the
calculation
going
on
here.
Let
me
run
the
experiments
at
the
end
of
the
week
and
then
I
think
I'll
fully
understand
how
this
gets
calculated
and
then
we
can
write
it
out
because
actually
a
bit
of
a
missing
thing
from
our
docs
anyway.
A
Awesome
so
down
to
discussion
item,
so
I
just
wanted
to
briefly
update
and
check
in
on
release
management
plans.
So
some
of
you,
but
not
all
of
you-
were
in
conversations
on
friday.
A
Because
of
the
urgency
around
this
and
the
importance
around
this,
we
decided
that
what
we'll
do
is
increase
the
number
of
release
managers
that
we
have
so
today.
That
means
henry
and
robert
thank
you
for
helping
out
here
and
then
tomorrow,
ruben
will
remain
in
release
management
and
myra
if
you'd
be
all
right
to
help
out
as
well
to
cover
on
the
america
side.
In
addition
to
henry
and
scarbeck
now
I'll
put
the
link
in
but
fun
twist
on,
the
14.2
back
port
is
after
we
got
that
all
ready.
A
We
realized
they're,
not
actually
ready
to
patch,
so
we're
on
a
little
bit
of
standby
at
the
moment,
but
that
will
be
coming
in
and
when
it
is
ready,
it
will
be
a
good
one
to
get
moving
so
I'll
put
a
link
in.
For
that,
then
the
other
one
I
want
to
just
check
in
on
was
we
have
pcl's
in
place
this
week
and
also
next
monday.
A
It
is
a
soft
pcl,
so
if
we
want
to,
we
can
be
pushing
right
through
up
to
canary,
but
really
as
a
question
of
how
do
we
want
to
manage
this
through
this
week
and
through
monday,.
D
A
So
my
suggestion,
if
no
one
has
any
strong
pendulums,
my
suggestion
will
be
so
during
email
time.
We
have
good
coverage
because
henry
will
be
working.
A
Most
of
us
are
working,
so
my
suggestion
will
be
that
we
leave
the
pipelines
running
this
week
and
allow
at
least
some
of
those
to
run
through
to
canary,
but
perhaps
we
lock
canary
for
the
america's
time
so
that
myra
is
not
just
all
on
you,
because
there
should
be
nobody
working
pretty
much
aside
from
you,
so
it
should
be
quiet
and
then
you
can
get
on
with
your
your
actual
work
and
then
for
monday
we
pause
everything
and
turn
off
all
the
pipelines
like
we
would
usually
do
for
a
family
and
friends
day.
E
Yeah,
I
think
this
makes
sense
because
it's
good
to
not
have
everything
merged
then
next
week,
at
the
same
time,
right
so
at
least
once
deploying
two
canary
in
between.
Maybe
that's
a
good
thing
why
we
have
coverage
during
emea
times,
but
we
shouldn't
do
it
too
often
yeah,
so
we
can
just
disable
them
at
america's
time.
A
Great
okay,
so
let's
see
the
pipeline's
running
and
henry
you
can
decide
when
you
want
to
have
canary
locked
or
unlocked
and
we'll
disable
everything
on
friday.
E
A
Okay
sounds
good
robert
over
to
you.
B
Yeah
sorry,
I
just
added
something
because
we
just
got
pinged
on
this
ongoing
incident,
there's
an
s1
and
they
are
looking
to
do
a
rollback,
but
we've
currently
marked
it
as
not
rollbackable,
because
there's
two
post-employee
migrations.
However
those
post-employment
migrations,
the
engineers
said
that
they're,
independent
I'd
impotent
and
shouldn't
actually
be
blocking
a
rollback.
So
I
don't
know
if
one
of
us
wants
to
hop
off
and
handle
that
now
or
if
we
should
discuss
it.
Some
more.
E
I'm
not
fully
on
details.
The
problem
is
that
we
have
an
s1
currently
incident
because
of
database
performance
issues
and
what
we
did.
We
disabled
merge
requests
to
get
around
this
for
now
and
I
think
at
least
a
few
minutes
ago.
It
still
wasn't
it
wasn't
clear
what
what
is
the
cause
of
that.
So
if
it
was
deployment
related
coming
in
by
a
change
or
not,
I'm
not
sure
if
we
have
an
answer
to
that,
but
I
see
that
stand
suggested
to
roll
back
anyway.
E
E
So
I'm
not
sure
if
you
really
decided
that
we
want
to
roll
back
right
now,
because
I
got
out
of
the
incident
call
for
this
week
to.
E
Yeah,
I
can
just
jump
back
in,
but
what
do
we
do,
then
about
holding
back
ever
supposed
to
deploy
migrations?
Do
we
need
to
stop
the
currently
running
once
then.
E
F
D
F
So
I
was
looking
on
the
two
migrations.
One
is
cleaning
up
a
sidekick
q,
so
I
mean
it
removes
stuff
from
a
queue
is
no
longer
there.
No
no
problem
there.
The
other
one
is
scheduling,
background
migration,
jobs
and
I
don't
know
if
the
job
was
defined
in
the
same
code
that
got
deployed.
If
I
mean
I
was
involved
in
the
incident,
so
I
don't
know
why
they
decided.
This
is
item
potent
if
it's
just
gonna
fail
and
all
the
jobs
will
fail
and
they
don't
care.
So
we
will
reschedule
later.
F
A
E
Yeah,
okay,
then
I
will
go
back
to
the
instrument
and
see
if
we
need
to
do
a
rollback
now.
A
So
henry
just
one
thing:
when
you
go
back
so
go
back
and
see
if
you
can
find
out
like
understand,
what's
happening
if
you
need
a
pair
for
the
rollback
or
if
it's
late
in
your
day,
to
begin
a
rollback
shout
right
because,
let's
not
forget
today,
we
have
four
release
managers.
So
we're
we're
quite
a
privileged
position.
If
people
want
to
pair
up
on
this
getting.
E
A
little
bit
late,
so
if
it's
taking
longer
than
half
an
hour,
then
I
would
ask
for
somebody
else
to
take
over
maybe,
but
I
will
have
a
look
in
the
incident
channel
to
see.
What's
going
on
now,.
D
A
Awesome
great
thanks
for
bringing
that
up
cool,
so
staging
rep.
I
just
wanted
to
mention
this
a
little
bit
because
I
actually
didn't
realize
you're
all
so
involved
in
reviews
for
this
stuff,
so
just
to
make
sure
everyone's
got
enough
context
for
here.
So
the
staging
ref
environment
exists
now,
and
it
is
being
deployed
to
that's
currently
in
parallel
with
staging
canary
there's
a
slight
question
mark
about
whether
that's
exactly
the
right
place
and
that
will
just
be
decided
based
on
how
long
these
deployments
end
up
taking.
A
This
thing
needs
to
conclude,
so
we'll
get
a
sense
of
how
long
this
actually
ends
up
taking
it
is
using
a
get
environment
and
that
is
currently
being
built
with
the
with
the
10k
reference
architecture,
so
staging
ref
got
named
as
it
is
so
that
it's
not
necessarily
locked
to
the
10k
environment
it
may
get
upgraded
later
on,
but
for
now
at
least
it's
using
the
10k
reference
architecture.
A
So
it
doesn't
have
absolutely
everything
that
production
has,
for
example,
it
is
being
used
at
the
moment,
so
quality
have
done
most
of
the
work
to
get
this
created
and
they're,
currently
developing
new
test
suites
to
run
on
this
environment.
So
once
those
things
are
hardened
out,
then
staging
ref
will
be
a
fully
sort
of
fledged
part
about
deployment
pipeline
and
will
turn
into
a
blocking
stage.
A
But
for
now
it
isn't
because
they're
developing
new
tests-
it's
not
really
being
used
for
anything
particularly
right
now,
and
this
will
sit
in
parallel
with
our
rest
of
our
pipeline.
So
this
is
where
the
the
qa
triggers
and
things
like
that,
become
important
to
us,
because
we'll
end
up
with
staging
canary
staging
ref
and
staging
all
running
different
test
suites
and
then
fitting
into
our
deployment
pipeline
at
different
points.
A
So
that's
really
just
an
updated
type
of
thing.
There
are
project
updates
being
added
into
issue
341427
each
week,
mostly
useful
for
quality,
so
they're
doing
the
kind
of
development
on
test.
Suites
and
hooking
things
together,
so
is.
Are
there
any
like?
That's
just
an
update,
but
if
anyone
got
any
questions
on
staging
ref.
A
E
So
they
first
want
to
test
the
effect
of
feature
flag
and
some
look
into
vacuuming.
If
that
doesn't
show
effect,
then
they
want
to
ping
us
for
a
rollback,
so
we
will
get
pinged
and
they
know
that
we
will
just
listen
on
the
release
managers
slackping.
A
One
thing
I
know
that
we
are
missing
is
the
kind
of
all
of
our
extra
stuff
that
goes
on
top,
so
I
know
that
we
don't
have
good
observability
of
staging
ref.
We
probably
don't
have
any
ability
to
lock
or
unlock
or
do
any
of
the
actual
kind
of
environment
management
that
we
do
so
again
before
we
go
to
a
blocking
stage
or
if
there's
blocking,
we
may
want
to
consider
having
some
override,
but
for
now
don't
those
men
if
you
think
of
something
like
oh,
we
should
definitely
think
of
this.
A
Please
feel
free
to
ping
it
somewhere,
even
just
to
me
and
slack
otherwise,
don't
worry
too
much
about
it,
we'll
I'll
spend
some
time
and
actually
like
figure
out
what
we
need
to
hook
this
into
like
proper
delivery,
stuff.
D
Yeah,
just
you
know,
question
one-on-ones
primarily
with
you
are
you
gonna
move
those
to
a
different
week?
Are
we
going
to
move
it
to
early
this
week,
etc?
What.