►
From YouTube: 2021-09-27 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).
B
B
C
I
don't
think
so.
We
should
probably
have
less
incidents,
but
I
don't
know
how
to
do
that
and
it
looks
healthy
so
far.
So,
okay,
nice.
B
I
wanted
to
briefly
share,
I
added
a
just
a
rough
like
manual
chart
onto
the
deployment
block.
I
think
it's
very
struggling
with
the
controls
of
the
zoom.
B
And
so
I'm
going
to
make
this
more
real,
but
I
just
put
in
a
draft
one
because
I
wanted
to
link
it
on
something
else,
but
this
is
really
interesting.
I
thought,
which
is
that
the
shape
of
deployment
blockers
over
or
like
deployment
disruption
over
the
last
few
months
you
can
see
is
the
kind
of
exact
mirror
against
the
number
of
deployments
we
go.
So
we've
been
seeing
week,
30
is
kind
of
early
august,
so
you
can
see
here,
like
the
the
disruption
we've
been
experiencing.
B
The
last
few
months
was
considerably
lower,
which
matches
up
well
with
the
number
of
deployments
going
up
and
mttp
coming
down.
So
that's
kind
of
the
interesting
thing
about
having
this
deployment
block.
Our
data
is
we'll
start,
hopefully
we'll
start
to
see
some
nice
patterns
coming
in
from
this
stuff.
B
Awesome
so
I've
dropped
in
a
selection
of
announcements.
I
don't
think
there's
anything
too
much
to
go
through
there
unless
anyone
specifically
wants
to
discuss
any
of
those
announcements.
B
Awesome,
okay,
great,
so
one
thing
I
wanted
to
just
talk
about
or
discuss
briefly
was
something
that
robert
and
I
were
chatting
about
a
bit
a
few
a
few
weeks
ago,
maybe
and
perhaps
didn't
really
in
a
way,
gets
missed.
I
suppose
in
360
feedback
is
the
teamness,
the
collaboration,
so
I
want
to
just
like
actually
call
out
like
thanks
so
much
for
all
of
you
like
for
collaborating
like,
even
just
in
the
last
week
alone.
You
know,
like
it's
been
really
rare.
I
think
that
we've
been
on
a
zoom
alone.
B
There's
usually
been
a
couple
of
you
or
if
we've
had
incidents,
there's
been
a
few
of
you
working
on
it
or
putting
up.
Mrs.
So
thanks
for
doing
that,
and
please
keep
that
up
like
it
would
be
way
better
for
us
to
work
on
half
as
many
things
and
deliver
half
as
many
things,
but
to
have
like
continued
support
and
being
able
to
help
each
other
out.
So
thank
you
very
much
everyone
off
the
back
of
that.
Does
anyone
actually
need
any
help
this
week,
because
I
know.
D
E
I
signed
up
for
something
that
is
going
to
stress
me
out
very
badly
for
the
next
few
weeks,
so
I
might
put
on
one-on-ones
for
various
people
spread
out
multiple
times
over
the
course
the
next
few
weeks,
if
you
can't
make
the
101
just
reschedule
it,
I'm
not
going
to
look
at
you
calendar,
I'm
just
going
to
throw
something
on
there
and
then
I'm
going
to
sit
there
and
talk
your
ear
off
for
the
next
30
minutes.
B
Awesome
go
for
it.
Does
anyone
else
need
any
support
this
week.
B
Yep,
okay,
super!
If
you
come
across
anything,
please
just
shout
myra
over
to
you.
C
Oh
yes,
so
I'm
going
to
be
out
of
the
office
for
next
monday
and
I
see
that
robert
kindly
offered
to
be
available
as
a
religious
manager.
So
thank
you,
robert.
B
Do
you
want
to
ruby?
Do
you
want
to
share
your
screen
and
roughly
walk
us
through
what
your,
what
you've,
what
you're
thinking
of
putting
in
then
we
might
be
able
to
give
the
kind
of
like
first
situational
feedback
quickly
now.
G
It
would
be
cool
to
maybe
also
see
somewhere,
which
version
is
in
which
environment,
maybe
if
that
is
possible,
just
as
a
number
somewhere.
Maybe,
and
also
one
comment.
I
think
the
playground
is
the
one
which
is
getting
deleted
after
I
write,
so
it
could
be
that
this
dashboard
is
vanishing.
C
B
And
on
your
comment
there,
henry,
like
is
the:
does
the
release
manager
dashboard
already
give
you
what
you
need
so
like
be
good
for
this
one,
to
sit
like
we're
good
for
release
manager
to
be
the
sort
of
deployment
dashboard
and
the
rollbacks
dashboard
to
be
the
kind
of
parallel.
G
G
B
D
D
Probably
just
bring
you
on
the
issue
tomorrow,
maybe
so,
once
we
have
the
list
of
things
that
we
look
at
then
it'll
be
more
clear
what
is
required
on
this
dashboard,
but
for
now
I
was
just
thinking
that
we
can
sort
of
see
the
trends
of
what
packages
got
deployed
to
staging
and
production
and
how
many
packages
we
actually
created
in
auto,
deploy.
C
F
There
is,
there
is
a
catch
now
that
we
are
all
here,
I'm
just
I
want
to
give
you
the
the
catch
that
there
is
here.
So
if
we
look
at
the
main
stage,
either
cannery
or
production,
this
data
is
accurate,
is
always
true.
If
we
look
at
the
canary
stage,
because
we
never
run
post-deployment
migration
on
canary,
that
number
is
lagging
behind.
F
So
basically
it
gets
updated
only
when
the
next
package
came
into
the
environment
and
gives
you
the
status
after
the
the
current
deployment,
which
means
that,
let's
assume
you
have
a
package
which
has
three
post-deployment
migration
and
previously
nothing
is
pending.
So
you
install
the
package
in
the
cannery
environment,
the
number
bumps
up
to
three
in
production
canary
and
is
still
zero
in
production
main
because
production
main
is
running
the
older
version.
F
We
have
no
no
easy
way
at
that
point
in
time
to
also
bump
the
the
canary
number
back
to
zero.
So
canary
would
just
have
his
number
refreshed
on
the
next
package
installation
which
in
case
it
has
no
positive
migration.
It
goes
to
zero
if
it
has
two
possible
migration,
for
instance,
then
it
goes
from
three
old
version
to
two
new
version,
and
this.
E
E
Perhaps
and
then
maybe
if
we
choose
to
stray
away
from
a
line
graph,
because
I
don't
think
a
line
graph
makes
really
much
sense
for
this,
maybe
like
a
a
gauge
or
I
forget
what
they
call
just
the
number
graph.
I
think
we
could
do
a
single.
E
Yeah,
I
think
we
could
do
a
better
query
just
to
like
get
both
pieces
of
information
and
show
like
the
max
number
or
something
to
that
effect
per
environment.
Again,
because.
D
F
A
F
But
it
gives
you
an
idea
what
is
coming.
That's
the
reason
why
I
mean
it's
there,
because
it's
the
same
script
that
we
run
on
the
fleet.
But
if
you
also
look
at
the
number
it
gives
you
an
idea.
If
the
things
that
you
are
going
to
promote
will
roll
out
something
includes
post
deployment,
migration.
G
C
Do
we
need
to
see
the
regular
migrations
for
rollbacks?
I
know
it
is
informative,
but
perhaps
it's
only
better
to
see
the
post-deployment
migrations,
because
regular
migration
doesn't
imply
anything
for
rollbacks.
C
F
C
F
B
Okay,
one
thing
I'll
put
it
on
the
issue,
because
maybe
a
slightly
bigger
is
whether
this
we
should
make
sure
we
have
a
kind
of
separation
of
the
reporting
and
kind
of
decision
making
information,
because
I
think
some
of
these
are
like
number
of
packages
being
tagged
feels
more
of
a
reporting
thing,
whereas
perhaps
the
migrations
is
more
of
a
like
a
decision-making
tool
so
perhaps
which
is
fine
like
it
they
can
be,
but
let's
just
make
sure
that
dashboards
end
up
being
clear,
clearly
kind
of
their
intent.
B
A
D
Yeah,
the
dotted
line
is
the
number
of
tagged
packages
yeah.
B
Calculate
is
how
many
packages
are
suitable
to
roll
back
and
from
there.
We
can
then
calculate
how
big
a
problem
are
the
post-deployment
migrations,
so
we
kind
of
have
two
parts
right.
One
is
the
data
to
show
to
build
the
kind
of
business
case
behind
let's
deal
with
post-deployment
migrations
and
unlock
all
our
packages,
and
then
the
other
side
is
the
kind
of
compliance
side
to
rollbacks,
which
is
showing
off
how
frequently
we
roll
back,
which
was
the
point
of
bringing
in
the
kind
of
recurring
practice
and
tracking.
D
I
think
we
need
two
additional
metrics
for
that.
One
is
the
counting
the
number
of
rollbacks
and
another
is.
F
F
It
is
not
really
accurate
because
we
can
only
see
when
it
changes
and
it
changes
only
if
we
deploy
something
that
has
post
deployment
migration.
So
it's
it's
a
subset
of
the
number
of
impossible
deployment
that
we
did
the
packages
that
are
not
possible
to
roll
back,
but
it
already
gives
us
an
idea
that
we
tend
to
have
post
deployment
migration
daily.
D
Yeah,
so
the
only
thing
that
makes
a
package
non-rollbackable
is
presence
of
a
post-deployment
migration.
D
F
D
B
Cool
yeah:
let's,
let's
follow
up
on
the
issue,
because
I
think
we've
got
a
few
further
things
but
nice
to
see
this
dashboard
coming
together.
Ruben.
So
thank
you
for
showing
us
up
awesome.
Is
there
anything
else?
People
want
to
bring
up
on
the
recording.