►
From YouTube: 2022-03-21 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
Awesome
so
I've
added
a
couple:
they've
got
got
a
few
announcements
most
important
one
family
and
friends.
It's
coming
up
on
friday.
Also,
I
do
think
some
other
people
have
got
vacations
coming
up
in
the
next
sort
of
few
weeks
and
months.
If
you
wouldn't
mind
adding
these
in
here
like
for
next
week,
so
we
get
a
bit
of
visibility
of
like
what's
coming
up.
That
would
be
helpful,
so
I'm
gonna
go
for
a
release
managers
happy
monday.
What
do
you
need
us
to
help
you
with.
B
Yes,
let's
discuss
so
when.
B
So
background,
there's
an
incident
today
related
to
staging
and
how
artifact
uploads
from
not
artifact
uploads
job
trace
uploads
is
not
occurring
properly.
B
B
B
The
other
option
is
to
quickly
release
14
9.1,
I'm
personally
leaning
towards
1491,
because
that
goes
well
with
our
procedures
that
enables
us
to
do
an
appropriate
incident
review
on
this.
Without
rushing
feeling
stressed
allowing
the
developers
to
figure
out
what
we
missed
during
testing
that
allowed
this
to
show
up
in
the
way
it
did
like.
I,
I
don't
want
to
dismiss
all
of
that,
but
being
that
this
also
impacts
people
that
use
geo.
C
A
Yeah,
I
agree,
I
I
think
with
the
I
guess,
with
the
options
we
have.
I
I
wasn't
I'm
I'm
sad
that
we'd
have
to
manually
delete
the
tag
in
order
to
re-tag.
I
think,
given
that
we
we
have
to
go
through
those
steps
that
feels
high
risk.
B
So
there
is
two
things
that
come
to
my
mind
is
one:
I
wonder
if
we
should
consider
building
a
process
that
enables
us
to
retag,
potentially
like
project
level
work
that
would
go
through
and
say
hey
if
we
already
tagged,
1490
go
through
all
of
our
projects
delete
those
tags,
and
then
we
could
start
fresh
from
day
21
tasks
or
whatever
day
it
was
that
we
start
the
tagging
procedure.
A
A
So
I
think
your
option,
your
suggestion
is
great
scopic,
let's
stick
with
our
process
and
let
someone
else
tell
us
our
process
is
not
good
enough.
It
doesn't
meet
the
needs.
I
think
we
have
a
few
options
right.
I've
seen
that
the
team
avoided
discuss
the
plan
for
the
release
post.
We
should
probably
suggest
to
them.
We
can
do
it
in
the
start
channel
like
that.
They
add
something
onto
the
upgrade
docks
as
well
for
the
upgrade
path.
A
A
A
Yeah
one
thing:
so
we
do
need
them
to
like
get
themselves
organized
for
that,
so
we
we
have
everything
ready
to
go,
and
then
we
can
just
start
preparing
that
quite
rapidly.
Tomorrow,.
A
B
A
So
aside
from
this
fun,
is
there
anything
else
that
really
is
managing
neat.
A
B
B
C
B
We
just
need
to
kind
of
work
together
at
some
point
to
figure
out
what
the
new
target
dates
for
those
would
be,
and
we
could
let
them
know
when
we
start
the
process
back
up
again.
C
A
B
A
B
C
B
A
B
A
A
A
If
there
is
give
us
a
shout,
it's
been
a
fun
year
so
far.
C
See
it
yep
thanks,
so
just
as
a
reminder
that
we
are
currently
working
about
removing
the
blocking
nature
of
the
post
deployment,
migrations
and
I
have
recorded
a
kickoff
video
which
presents
the
problem,
the
solutions
and
the
steps
that
we
are
going
to
take
to
hopefully
achieve
it.
For
those
that
don't
know,
we
are
basically
removing
the
post
migrations
from
the
coordinated
pipeline
up
to
a
new,
independent,
coordinated
pipeline
that
is
going
to
be
only
for
the
post-deployment
migrations.
C
And
well
yes,
as
a
reminder,
we
have
a
large
metric
on
the
release
manager,
dashboard
that
tells
you
like.
Okay,
there
are
two
or
three
or
four
pending
possible
migrations
on
staging
or
on
production
and
yeah.
That's
it
if
you
see
any
failure
with
this
plan
or
if
you
have
a
thought
or
something
else,
please
please,
please
let
me
know
and
thank
you.
A
And
we're
making
great
progress
on
actually
picking
up
the
issues,
so
they
will
be
they're
continuing
to
be
on
the
delivery
board.
If
people
are
looking
to
pick
up
work
for
this
stuff,
then
please
look
there.
A
Awesome
so
mttp
is
looking
very
nice,
so
great
work,
everyone
there
great
work.
Getting
the
deployments
out.
You
can
see
that
we
have
a
lot
of
deployments
hitting
actually.
B
A
A
So
I
would
suggest,
look
on
the
monthly,
so
the
monthly
one
is
the
one
with
the
the
best
sort
of
like
the
one
that
I
I
suspect,
the
one
that
you
were
looking
at
garbage.
I
don't
think
it
has
the
current
month
on
it,
so
I
think
it
will
always
lag.
I
think
there's
a
slightly
I
I
have
to
dig
into
how
they're
set
up,
but
this
is
the
one
that's
the
most
current
for
sure,
and
I
think
what
we
see
is
mttp
is
looking
amazing.
A
A
Couldn't
find
any
incident
with
any
deployment
blocking
labels?
However,
I
do
have
the
impression
that
last
week
was
not
a
super
great
week.
So
do
we
have
some
incidents
that
need
block,
don't
need
labeling.
A
A
You
mind
like,
if
I
plan
to
do
that
tomorrow
afternoon.
Does
that
give
you
two
each
like
a
data
to
review
things?
What
I
want
to
use
these?
What
I'm
trying
to
use
these
labels
and
events
for
is
to
go
and
request
kind
of
improvements
or
highlight
gaps
like
I
noticed
today,
ahmad
that
you
you
had.
You
had
a
delay,
probably
in
getting
hold
of
quality,
because
there's
actually
no
one
from
emia
available.
A
This
week
seems
like
a
bit
of
a
gap
actually
on
a
release
week,
and
I
see
we
have
the
same
setup
in
april,
so
I'm
going
to
go
and
actually
have
a
chat
with
quality
and
see.
If
we
can
plan
that
in
around
I
know
they
don't
have
full
24
hour
cover,
but
on
release
weeks
it
would
be
really
helpful
to
have
like
emus,
almost
certainly
when
we're
going
to
hit
qa
problems
on
the
on
the
monthly
release.
A
A
Is
there
any
other
stuff
like?
I
know
you
have
lots
of
lots
of
stuff
sort
of
it
feels
very
hands-on.
There's
lots
of
incidents
and
we're
seeing
lots
of
stuff
from
the
deployments
reordering
the
pipeline
reordering,
but
are
there
any
other
things
that
actually
it
feels
like
a
sort
of
a
systemic
problem
in
either
our
process
or
our
tools
or
setup
that,
if
we
could
fix,
would
make
release
management
easier.
A
Okay,
have
a
think
about
that,
like
I
think,
and
maybe,
if
you
as
well
like
matthias,
you
come
out
of
there.
As
you
finish,
your
shift
have
a
think
about,
like
you
know,
looking
back
over
the
last
couple
of
months,
so
there
are
other
problems
in
the
system
that
actually
make
this
aside
from
just
there
are
lots
of
incidents
or
lots
of
things.
Like
other
things,
we
should
be
trying
to
to
change.