►
From YouTube: 2021-10-18 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
B
B
B
A
I
don't
know
I
noticed,
I
don't
know
if
it's
joining
it's
kind
of
late
for
him,
so
he
may
not
be
so.
Let's
get
started
myra
is
there
any
specific
highlights
you
want
to
share
from
mttp.
C
Yeah,
no,
since
you
know,
or
you
might
know,
I
have
been
experimenting
with
to
deploy
branches
and
I
think
it
is
working.
So
far.
Last
week
there
was
a
day
in
which
we
managed
to
deploy
the
production
seven
times
between
brains,
ruben
and
myself,
so
yeah
it
is
working
nicely
as
long
as
there
are
no
incidents
or
nothing
that
is
stopping
us
yeah.
It
is
working
nice.
A
C
No,
I
haven't
updated,
as
I
mentioned
the
other
day.
This
is
a
schedule
that
works
for
me
because
it
is
kind
of
adjusted
to
my
work
hours,
but
I'm
not
sure
if
it
is
going
to
work
for
scarbec
or
if
it
is
going
to
work
for
robert.
I
think
we
discussed
at
some
point
that
the
schedule
for
auto
deploy
branches
should
be
adjusted
as
for
the
release
manager
schedule.
So
I'm
not
sure
if
I
should
update
yeah.
A
B
Got
it
can
we
also
add
guidelines
for
how
to
decide
what
to
make
those
hours?
Because
last.
A
B
A
B
A
A
Yeah,
it's
a
good
idea.
Actually,
marriage.
Do
you
mind
just
putting
it
doesn't
have
to
be
super
in-depth,
so
maybe
like
just
the
first
pass
of
a
like
a
a
run
book
or
like
a
guide
or
something
you
know
as
a
release
manager.
How
do
you
make
these
decisions
because
I
think
we
we're
kind
of
at
the
stage
where
every
release
manager
coming
into
their
shift
kind
of
needs
to
review
what
branches
exist,
decide
what
works
for
them
with
these
kind
of
guidelines
and
then
make
the
change
and
update
the
handbook.
A
A
He
won't
be
able
to
do
it
every
week
because
of
uncles
so
probably
need
to
find
a
way
to.
Actually,
I
guess,
make
make
flexible
decisions
about
branches.
C
Yeah
for
sure
I
can
do
that,
should
I
do
the
wrong
block
in
the
release
docs
or
in
the
handbook.
A
Release
docs,
I
think,
makes
sense
like
in
maybe
just
unlike
the
release
manager
like,
I
think,
what
we're
going
to
end
up
building
out
is
kind
of
a
rough
set
of
documentation.
That's
a
little
bit
different
to
onboarding
as
a
release
manager
for
the
first
time,
but
it's
kind
of
like
a
I'm,
a
returning
release
manager.
A
What
do
I
need
to
know,
and
we
could
perhaps
just
have
in
there
like
this
like
okay,
you
need
to
set
branch
times,
here's
your
guide
for
that,
and
then
there
may
be
other
things
like
refresher
of,
like
you
know
day-to-day
or
whatever
else,
we're
changing
that
we
could
add
in
got
it.
Okay,
awesome
thanks
mira,.
A
Super
a
great
work
on
getting
the
extra
deployments
through,
like
I
think
mttp
probably
doesn't
have
its
most
realistic.
Look
because
we
had
a
pcl
last
week,
but
it's
super
awesome
that
we're
getting
so
many
deployments
coming
in.
So.
C
Yeah
still,
I
was
expecting
better
results,
but
the
mttp
is
around
eight
hours,
which
is
not
bad,
but
I
think
we
are
at
the
point
in
which
we
are
being
affected
by
the
changes
in
staging
yeah,
because.
A
C
A
They're,
taking
a
bit
longer
yeah
for
sure
for
sure
cool,
okay.
Well,
we
can.
We
can
work
that
stuff
out.
That
is
well
I'll,
get
to
oh,
it's
a
change,
we're
going
to
have
to
make
and
the
the
change
that
we
think
we
have
to
make
for
mixed
deployment.
Testing
benefits
mttp.
So
I'm
not
I'm
not
overly
worried
about
that
right
now,
but
yeah
you're
right.
It
probably
affects
cool.
So
on
the
announcements
thing
mostly,
these
are
read-only
they're,
pretty
much
everybody's
got
some
time
off.
A
So
we're
super
super
light.
This
week
is
going
to
be
kind
of
our
last
particularly
effective
week.
So
last
week
was
really
really
effective.
This
week
was
still
pretty
affected,
so
completely
fine,
if,
like
all
we
get
done
this
week,
is
a
good
14
not
for
release.
Then
fine
we've
completely
achieved
everything
this
week
next
week,
things
should
start
to
get
a
little
better.
We've
got,
hopefully
alessia
I'll
be
back
next
monday.
Henry
is
back
next
monday
as
well.
A
So
we
start
to
bring
in
some
extra
people
and
80
is
joining
us
on
monday
as
well,
so
they'll
be
a
little
overhead.
Rubin
is
going
to
buddy
with
him
to
get
him
kind
of
set
up
inside
delivery,
but
please
plan
to
coffee
chat
with
him
he's
in
emir,
so
you'll
get
just
a
little
bit
of
overlap
each
day.
A
Oh
and
I
skipped
d,
so
I
want
to
just
mention
on
d
so
d
I
am
hopefully
heading
over
to
canada
on
thursday,
so
we'll
see
how
that
works
out.
But
if
successful,
then
I
will
be
around
a
little
bit
thursday
morning
to
help
reuben
if
he
needs
any
help,
but
otherwise
mara
I'll.
Let
you
kind
of
handle
the
bulk
of
the
tagging
friday
I'll
just
be
online
during
the
publish
of
the
release
just
in
case.
A
I
know,
you've
got
this,
but
just
in
case
and
then
I'll
be
out
for
the
rest
of
friday
and
then
for
next
week.
I
will
be
working
eastern
time,
so
I
will
provided
I
get
to
canada,
update
my
calendars
and
things
so
yeah
I'll
be
working
alongside
you
too.
A
Awesome
great
stuff,
so
discussion
items
do
either
of
you
have
anything
that
you,
you
know
you're
waiting
on
alessio
for.
A
No
okay,
good
good.
I
will
have
a
look
through
his
issues
and
things
and
just
see
if
there's
anything
that
we
need
to
hand
over.
I
don't
think
I
hope
there's
not
too
much.
I
know
he's
really
involved
in
the
mixed
deployment
testing
stuff,
so
I'll
pick
up
and
get
things
set
up
there
and
I'm
going
to
work
with
graham
to
actually
pick
the
tasks
up
for
that.
But
let
me
know
if
you
come
across
anything
else
where
you're
you're
feeling
blocked
like
marry
for
you,
like
you,
may
end
up
blocked.
A
I
guess
if
you
need
reviews
like
see
how
reuben
gets
on
like,
but
that's
gonna
be
those
are
gonna,
be
our
gaps
right.
C
A
Yeah,
I
was
gonna
say
like
honestly
like
if,
if
rubin
reviews-
and
you
two,
if
you
two
think
it
looks-
it's
fine-
I'm
completely
supportive
of
us
putting
things
in
and
like
reworking
in
the
future.
If
you
know,
if
we
need
to
like
don't
feel
blocked,
if,
if
we're
like,
oh
we're,
not
totally
sure,
then
let's
go
for
it
and
we
can
always
put
extra
changes
in
later
when
robert
and
alessia
are
back
so
we'll
see
how
it
goes,
but
yeah
it's
going
to
be
a
kind
of
quiet
week.
A
So
let's
say
let's
just
focus
on
the
release
and
see
how
that
goes
cool
and
then
the
other
one
was
on
okay
arts.
So
I
finally
put
together
an
issue.
So
sorry,
I'm
running
a
bit
late
on
this.
Hopefully
it
affects
you
to
a
little
less.
It
affects
the
others,
a
bit
more.
What
I'm
trying
to
think
about
for
q4
is.
We
have
lots
of
lots
of
little
things
kind
of
going
on
and
we
have
quite
a
few
things
that
we
kind
of
need
to
deliver
on.
A
But
from
this
quarter
what
was
really
painful
was
registry,
not
because
the
project
was
particularly
painful,
like
it's
gone,
swimmingly
well,
but
and
really
anticipate
how
much
time
henry
is
going
to
have
to
spend
on
that.
So
that
definitely
was
one
impact
on
our
okrs,
so
we
didn't
have
that
kind
of
built
in
so
the
other
thing
that's
kind
of
been
going
along,
it
hasn't
been
hugely
disruptive,
but
it
has
been
a
little
bit
is
also
the
staging
improvements.
A
So
now
that
we
have
got
to
the
stage
where
we
know
we
need
to
make
fairly
big
changes
to
support
the
mixed
deployment
testing
by
reordering
the
pipeline.
We
are
going
to
have
to
make
that
change.
I
think
it
has
to
be
done
within
delivery,
because
it's
so
close
to
everything
we're
doing
so.
I've
tried
to
write
that
into
an
okr
where
it's
not
like
it
blocks
everything
else,
but
doing
so.
A
I've
kind
of
joined
it
up
with
single
pipeline,
but
also
the
future
post-deployment
migrations
work,
because
honestly,
they're
all
related
in
that
it's
reorder
the
pipeline
basically
to
meet
our
needs,
but
that's
a
reasonable
chunk
of
work.
So
I've
tried
to
screw
that
together.
Let's
see
what
you
think
it
means
we're,
obviously
not
doing
various
other
things
so
have
a
think
about
whether
you
actually
have
other
ideas
that
we
should
be
bringing
in
either.
A
In
addition,
or
instead
of
some
of
this
stuff,
the
one
I
was
perhaps
less
so
clear
on
is
on
the
kubernetes
side.
So
we've
got
we're
making
good
progress
on
pages,
but
I
don't
think
there's
necessarily
a
really
obvious
next
service,
because
at
the
moment
it
looks
like
gitly,
perfect
and
read
it.
None
of
them
are
ready,
so
redis,
there's
no
obvious
operator
that
we
can
use
goodly
and
profit
will
be
tested
by
quality
in
14.5
to
see
what
that
looks
like.
A
But
at
the
moment
I
don't
I'm
not
expecting
that
that
will
come
out
of
that
testing
and
have
a
really
clear,
like
brilliant
italy
is
ready
to
migrate,
like
it's
much
more
likely
that
we
come
out
with,
does
work
for
getaly,
so
at
the
moment.
So
you
think
of
what
I've
suggested
in
there,
but
at
the
moment
I'm
very
open
to
suggestions
on
like
what
we
could
do
there.
That
would
be
useful
stuff.
A
Awesome
and
I'll
leave
that
up,
like
I'm
I've.
I've
set
the
date
kind
of
to
end
of
next
monday
to
give
alessio
and
henry
a
little
bit
of
time
to
hopefully
have
a
look
at
that
on
next
monday,
but
yeah
don't
feel
you
have
to
wait
for
that.
Give
me
a
shout
if
you
have
questions
or
want
to
add
comments
with
suggestions.
A
Awesome
are
there
any
other
discussion
items.