►
From YouTube: 2022-01-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).
B
B
Awesome
so
we're
one
minute
pass.
So,
let's
get
started
so
welcome
everyone.
First,
delivery
weekly
of
the
year
so
most
important
one
from
the
announcements.
Well,
no,
not
the
best
one.
So
there's
a
lot
of
announcements
should
we
just
say:
let's
take
everyone
can
take
a
moment
to
read
through
those
and
just
see
if
there
are
any
bits
that
we
want
to
call
out
there.
B
Awesome,
okay,
good,
so
on
discussion
item
so
wednesday
we
have
our
monthly
ama.
It
is
a
little
late
for
some
of
you.
I
know
it's
like
the
middle
of
the
night
for
graham
so
there's
not
much.
You
can
do
about
that.
But
if
it
is
during
your
work
hours,
then
please
do
attend
so
that
we
can
kind
of
answer
questions
and
you
get
to
chat
to
stakeholders
like
it
doesn't
have
to
be
one-sided,
like
we
can
ask
them
questions
and
pose
things
as
well.
B
So
what
I
was
going
to
do
for
this
month
is
just
share
a
few
things
and
people
can
have
a
read
of
them.
So
when
I
announce
tomorrow,
I'll
put
some
links
up
so
a
couple
of
things
I
thought
of
straight
away:
one
is
to
share
the
year
in
review.
Another
one
is
robert's
issue
around
requesting
developer
feedback
on
staging
canary,
but
is
there
anything
else
anyone
wants
to
either
highlight
or
like
request
like
a
broader
set
of
people
read
through
and
potentially
chat
with
us
about
on
wednesday.
B
I
guess
we
could
do
a
high
level
right,
so
I
had
the
reorder
in
last
month's
group
conversation,
so
I
guess
we
could
pull
that
slide
and
then
link
it
with
this
issue
and
they
kind
of
go
together
right.
So
it's
like
the
order
is
the
kind
of
the
reason
behind
this
stuff.
Okay,
yeah.
Let
me
see
if
I
can
pull
that.
B
Cool,
if
you
think
of
anything
else,
then
give
me
a
shout
I'll
send
something
I
usually
try
and
do
it
like
24
hours
before
so
I'll.
Do
it
sort
of
whatever,
like
five
utc
tomorrow,
1700
gtc
tomorrow.
D
B
B
Okay,
so
if
that's
the
camera-
okay,
cool,
okay,
so
release
managers
henry
you
have
an
idea
here,
but
is
there
any
action
we
should
take
based
on
last
week's
mttp
to
improve
things.
A
I
think
we
don't
find
this
doing
a
lot
of
deployment
production
all
the
time
and
this
reflects
in
our
mttp,
but
we
have
kind
of
a
regression
which
I
highlighted
here
at
point
b,
which
is
that
the
package
drop
for
our
omnibus
packages
often
is
delayed,
like
they
seem
to
be
stuck
for
a
certain
amount
of
minutes
in
between
their
jobs
like
for
30
or
40
minutes.
A
Sometimes-
and
this
is
so
long
that
our
coordinated
pipelines
then
just
time
out
and
don't
continue,
and
we
need
to
then
go
to
the
package,
stop
look
if
it's
finished
or
not,
or
if
it
failed
for
some
reason
retry.
It
then
go
back
to
the
coordinated
pipeline.
We
trigger
the
wait
for
him,
job
and
and
so
on,
and
then
we'll
run
through
these
issues,
sometimes
with
bridge
jobs
being
skipped.
So
I
opened
this
issue
with
distribution
team
to
look
into
this.
A
B
Awesome.
Thank
you
for
that
for
the
issue
that
you
linked
and
there
664.
I
don't
know
what
the
correct
labels
are,
but
I
would
assume
there
need
to
be
some
labels
because
I
know
distribution
do
use
those
to
prioritize
their
works.
Would
you
mind
just
checking
in
in
their
slide
channel
about
how
we
should
correctly
label
this.