►
From YouTube: 2022-07-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
Hello,
everyone.
So
this
is
monday
and
we
have
no
discussion
point,
which
is
a
good
thing
right.
So
there
are
a
couple
of
announcements.
So
people
taking
time
off
for
things
like
that,
so
everyone
can
read
it.
Unless
there
are
some
last
minute
discussion
point
we
can
go
straight
to
the
release
managers
section.
So
no
one
is
speaking
so.
B
Jay,
let
me
share
my
screen.
B
So
I
assume
you
are
seeing
my
screen
now.
If
the
zoombar
lets
me
pick
another
tab.
Okay,
thank
you
very
much.
So
a
complicated
week
we
had
a
lot
of
incidents
plus
we
also
had
family
and
friends
day.
So
deployments
were
very
limited.
Last
week
it
was
family
and
friends
state
last
week,
yeah.
I
think
it
was.
I
don't
really
remember,
but
I
think
it
was
monday.
Last
week.
B
And
was
12
so
that
might
explain
why
we
didn't
have
any
package,
not
that
not
promoted
and
then
well.
We
started
on
the
13
started
a
bit
slow.
We
were
done
in
palaces,
but
I
assume
by
this
time
we
were
starting
the
day
and
then
we
were
stuck
promoted.
So
we
can
see
how
this
is
like
increasing
and
then
this
one
is
sort
of
decreasing.
B
But
when
we
reached
the
14,
we
had
two
s
only
2
s2
incidents
that
prevent
us
from
deploying
the
whole
day.
Basically,
we
had
a
failure
on
pages
and
we
also
had
a
500.
So
we
were,
we
were
not
able
to
deploy
because
we
were
waiting
for
the
fix
and
then
pipelines,
and
it
was
long
and
then
things
improved
the
next
day,
but
also
kind
of
on
friday.
B
On
the
last
day,
they
were
not
that
good,
because
we
also
had
like
we
were
able
to
deploy
in
the
morning
in
miami
or
in
emea,
but
in
amer
we
had
another
italy
incident
that
also
the
deploys,
because
we
needed
to
wait
for
a
fix
that
I
think
it
is
already
done
and
that
basically
block
deployments
like
for
on
my
shift.
B
A
I
think
this
is
the
first
time
we
had
a
weekend
with
so
high
and
number
of
active,
coordinated
pipelines.
So
we
we
didn't
complete
deployment
by
the
end
of
friday,
and
we
had
this
scary
bar.
B
B
This
is
a
bit
low,
but
considering
we
didn't
deploy
on
monday,
nor
on
thursday
and
almost
not
on
friday,
it
seems
accurate,
so
yeah,
I
think
our
best
day
was
this
one
with
knight
deployments
and
then
all
of
the
other
ones
were
well
below
four
so
and
then
lead
time
for
changes
this.
The
median
time
between
america
was
being
merged
and
deployed
to
production.
A
A
That's
the
real
deployment,
no,
no,
no
left
from
where
you
were
so
what
it
was:
the
12th
july
12th.
Okay,
we
have
a
green
dot,
so
a
blue
dot
there.
So
it
means
that
we
deployed,
but
probably
then
we
didn't
deploy
the
day
after
because
of
the
incident.
So
this
is
the
first
time
we
see
the
the
the
dashed
lines,
which
means
no
deployment
for
more
than
24
hour,
one
next
to
each
other.
A
That's
why
I
say:
if
you
look
at
over
the
last
month,
it
makes
more
sense
because
we
see
we
clearly
see
the
weeks.
The
weekend
is
the
dashed
line
where
we
can't
deploy
and
the
the
mttp
goes
higher,
and
then
it
drops
down
on
tuesday,
usually
because
it's
the
it's
the
first
day
that
we
do
continuous
deployment
since
the
beginning
of
the
week
and
then
it
moves
as
it
goes
right.