►
From YouTube: 2022-09-19 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
Are
you
recording
good
okay?
So
let's
get
started
welcome
happy
monday.
Today
is
the
19th
of
february,
if
or
september,
if
you're
just
waking
up.
Congratulations
like
me,
a
few
announcements,
keep
in
mind
that
we
do
have
a
family
and
friends
day
on
the
26th.
We
have
no
discussion
items
so
myra
good
morning,
and
would
you
like
to
roll
us
through
what's
been
happening
with
releases
and
deployments
and
such.
C
For
sure
for
sure,
so
last
week
was
actually
very
calm.
We
didn't
have
any
incident
that
block
releases
nor
deployments
so
yeah
either
way,
I'm
going
to
walk
you
through
the
perhaps
let
me
share
my
screen
share
awesome.
So
well
soon
doesn't
let
me
move
my
okay
now
you're
ready
so
regular
week
we
have
started
on
the
12th.
We
can
see
that
we
were
waking
up.
C
It
started
to
work
and
well
most
of
the
packages
that
we
talked
were
promoted,
with
the
exceptions
or
one
or
two
which
I
think
it
is
acceptable,
and
then
I
think
something
happened
on
thursday
in
which
we
sort
of
lost
our
metrics
for
some
reason
yeah.
It
was
an.
B
Incident
we
had,
there
are
some
blackouts
in
the
in
the
data
that
we
have.
C
C
So
yeah,
I
think
it
is
like
a
million
of
14
hours,
which
we
discussed.
That
was
like
like
last
week
that
or
two
weeks
ago
that
this
is
the
value
in
the
middle.
So
it
makes
sense
now
to
me,
okay
and
then
the
deployment
frequency
which
is
37
deploys
that's
nice
with
around
four,
almost
five
deployments
per
day,
which
is.
B
C
B
C
C
We
now
have
a
pipeline
schedule
that
is
going
to
be
executed
every
monday
and
it
basically
lists
all
the
release
blockers.
If
we
have
in
this
case,
we
can
see
that
we
didn't
have
any
release
blocker
for
the
week.
So
it's
basically
saying
nothing
happened,
and
it
is
also
giving
us
a
list
of
all
the
incidents
that
were
open
for
release
managers
to
review.
In
case
we
need
to
add
some
deploys
block
label,
so
this
is
handy,
so
we
no
longer
need
to
go
and
fetch
all
the
incidents
from
the
incident
management
channel
or
whatever.
B
Sorry,
yes
sure
so,
let's
say
like
this
one
right:
zero
incident,
zero
blockers
and
then
we
remember
no.
Actually
there
was
one
right,
so
we
opened
the
list
found
something
and
add
the
missing
label.
When
will
the
the
table
up
update
next
week
or
well.
B
C
Be
well
it
will
it.
It
is
supposed
to
be
run
every
monday,
but
for
next
monday,
if
you
add
a
label
for
an
incident
from
the
previous
week,
it
is
not
going
to
take
it
to
consider
it
only
considers
from
previous
weeks.
So
what
you
can
do
in
that
case
is
just
to
add
the
labels.
Let's
say
you
add
the
labels
from
decision
to
this
issue
and
then
just
close
it
and
then
just
schedule
like
trigger
the
bible
schedule
again,
and
it
should
create
a
new
issue.
Okay,.
A
Meyer,
does
this
pull
from
the
release
tasks
issue
tracker
at
all?
Okay,.
C
So
yeah
handy
things
and
that's
it
for
me.