►
From YouTube: 2022-09-12 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
A
A
A
We
have
some
announcement.
We
have
our
ask
me
anything
before
this
month:
the
14th
of
September,
please,
if
you
have
any
questions,
bring
your
questions
and
attend
as
much
as
you
can.
So
maybe
you
can
also
be
able
to
provide
some
answer.
If
you
can,
the
agenda
is
already
up
so
I
think
it's
already
be
able
to
add
some
questions
or
at
least
review.
The
question
already
be
added
I
added,
also
as
more
reminder
about
the
Q2
retro
form,
Google
form
that
was
shared
in
the
issue.
A
Last
week,
I
saw
that
we
have
only
four
answers:
I
don't
know
who,
because
it's
Anonymous
but
would
be
great
if
we
can
get
to
close
to
100
participation.
So
we
are
some
a
statistical
significant
based
for
that.
A
Then
there
are
some
people
taking
some
day
off
so
enjoy
those
day
off
that
you're
taking
and
I.
Guess
we
can
move
to
the
discussion
Point
Amy.
Do
you
want
to
realize
yours?
Yes,.
B
Thank
you
so
I
wanted
to
just
firstly
check
up
on
sinus,
but
also
see
if
anyone
had
any
comments
or
questions
I
think
they
want
to
discuss
on
this
call
around
the
proposed
terminology
that
orchestration
have
have
come
up
with
following
kind
of
our
analysis.
So
what
happens?
Sort
of
context
on
where
we
came
to
for
this
is
we
started
analyzing?
How
component
deployments
currently
work
and
we
had
some
difficulties
because
it
turns
out
a
lot
of
our
terms
are
very
overloaded.
B
When
we
say
release
it
can
mean
lots
of
different
things
to
different
people,
for
example.
So
we
started
thinking
about
what
terminology
could
we
use
to
help
it
be
clear
for
ourselves,
but
also
as
we
go
forwards
and
we
get
more
stage,
groups
involved,
how
we
can
make
it
clear
for
other
people.
So
this
issue
has
the
proposed
terms.
B
One
thing
I
do
particularly
want
to
hear
people's
thoughts
on
is.
This
gives
us
a
bit
of
a
switch
away
from
using
self-serve
deployments,
which
is
the
term
we've
been
using
up
until
now
for
sort
of
what
we're
working
towards.
So,
in
this
case,
this
will
move
us
into
using
independent
deployments,
and
the
thinking
behind
that
was.
It
gives
a
bit
more
clarity
around
the
fact
that
we're
giving
people
a
fully
isolated
pipeline
that
would
take
their
component
through
to
production,
we're
not
giving
them
the
ability
to
operate
the
auto
deploy
pipeline,
for
example.
B
B
Does
anybody
have
any
should
I
guess
just
maybe
a
quick,
a
quick
show
of
thumbs
like
overall
I
know
some
of
you
might
want
to
read
but
like
overall,
do
people
feel
positive,
neutral
concerned.
B
A
A
Perfect,
so
we
actually
started
to
have
some
problems
last
week
around
the
eighth,
so
something
to
remind
myself
and
also
probably
feature
release
managers
to
add
a
notation
to
the
graph.
So
when
I
had,
this
call
is
much
easier
to
understand
what
happened.
A
But
anyway,
last
week
we
had
some
incident
and
some
blockers
that
we
had
about
some
pipelines.
They
were
failing
and
we
only
had
like
a
few
promotions
during
the
day,
even
if
it
looks
like
pretty
big
gap,
that
I
would
expect
that
we
had
some
deployments,
but
for
sure,
at
least
in
the
night,
between
the
the
eight
and
the
nine
there
were
no
deployments
at
all.
I.
Remember
gray,
mentioning
this,
because
we
had
a
fixed
Mr
that
actually
was
blocking
everything
we
should
pick
it
up
to
fix.
A
The
problem
fix
the
problem
and
then
we
recovered
later
on
during
the
end
of
the
week
and
then
clearly
we
went
back
down
to
for
the
weekend,
for
we
stopped
the
outer
deploy
and
so
on.
Today
we
I
actually
promoted
one
something
that
they
should
not
promote.
It
I
just
learned
it
today,
I
trust
about
Perry
very
much,
so
we
have
actually
something
more
that
is
coming
up,
we're
going
to
have
a
gap
between
the
type
package
and
the
one
that
we
are.
We
need
to
promote
so.
A
Need
love
deployment,
frequency
deployment,
frequency
more
or
less
looks
the
same
with
the
same
pattern.
Actually,
we
have
an
extra
deployment
during
this
week.
Usually
we
stop
to
eight
nine
looks
like
we
touched
10.
last
week,
so
I
don't
see
any
big
changes
here
and
for
delete
time.
A
A
But
apart
from
that,
the
pattern
looks
looks
more
or
less
the
same.
A
So,
let's
hold
down
for
me,
add
more
annotation
during
my
shift
to
the
grafana
deployment
blockers.
I
still
didn't
do
my
homeworks
for
the
blockers.
For
last
week
married
you
get
the
chance
to
do
that
yep.
They
all
have
labels.
As
far
as
I
know
great
did
you
manage
to
update
the
issue
and
the
Google
sheet?
A
No
I
only
added
the
labels.
Okay,
maybe
and
then
I'm
gonna
Maybe.
We
can
have
maybe
a
sinkhole
I'll
show
you
what
I
usually
enemy
are
doing
on
that
and
then
so
we
can
do
it
together.
B
It's
possible:
could
we
get
that
done
before
around
my
midday
tomorrow,
because
we
have
the
key
metrics
meeting
on
Wednesday
and
because
of
that
PCL
the
mttp
is
super
high.
So
we
want
to
be
able
to
point
to
the
data
that
explains
why
so
that
Steve
has
has
the
information
for
that.