►
From YouTube: 2022-06-29 Delivery team weekly APAC/EMEA
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
A
I'm
gonna,
I'm
not
sure
if
anyone
else
is
coming,
I
think
graham
is
coming,
but
he
said
it'd
be
a
bit
late,
but
whilst
I've
just
got
you
here,
mckelly
like
fastboot,
I
was
having
a
look
at
this
stuff
from
a
quick
search
around.
I
think
either
berlin
berlin's,
probably
the
easiest
or
london
london
is
the
is
better
flights
for
some
people.
But
I
need
to
I'm
going
to
ping
people
and
check
out
on
what
entry
requirements
they
might
need
that
could.
A
A
B
A
Yeah,
it's
not
too
cold
right,
okay,
yeah,
and
that
probably
makes
it
easier
because
I
think
matt
will
be
unable
to
travel.
So
london
would
be
best
for
matt,
but
I
think
he'll
be
unable
to
travel
pretty
much
any
time,
so
it
doesn't
matter
if
it's
september,
so,
okay,
great
okay,
so
I'll
start
pointing
some
stuff.
Hey
reuben,
hi
it'll
be
great!
So
just
yesterday,
well
yeah,
maybe
graham,
I
think
it's
coming,
but
he
said
it'd
be
a
few
minutes
late,
I'm
just
gonna.
A
We
just
had
a
little
chat
about
fastboot,
but
just
I've
mentioned
the
discussion
stuff.
So
we've
got
this
on
the
recording
around
incidents,
so
I
have
been
working
on
switching
over
how
we
use
severities
for
deployment
related
incidents.
A
This
is
coming
because
we're
unable
to
get
accurate
incident
metrics,
because
it's
here's
all
the
stuff
that
affected
users
would
get
like.
Oh
plus,
here's
some
like
times
where
staging
tests
failed
and
they're
like
really
really
different
categories,
so
I've
been
putting
together
what's
making
it
a
little
bit
more
tricky
is
that
we
have
lots
of
different
types
of
deployment
incidents.
So
it's
been
quite
straightforward
when
we
can
just
say
everything
is
an
s2
but
and
then
we're
at
a
point
now
where
we
can
piece
this
part.
A
So
just
as
a
heads
up,
I
am
starting
to
put
this
stuff
in
place
already,
so
we've
already
been
using
the
lightweight
kind
of
incident.
Sorry
lightweight
issue
process
leslie,
I
tried
out
in
15.0,
so
we
keep
going
with
that
and
I'm
adjusting
the
dock.
So
what
I'll
do
is
adjust
all
the
dock
so
that
everything
points
to
the
availability
severities
in
the
handbook
which
at
the
moment
says,
use
an
s2
for
everything.
A
So
we
can
just
keep
going
and
at
the
very
last
step,
I'll
update
the
handbook
with
the
with
the
correct
severities
that
we
should
start
applying
instead,
so
these
things
are
starting
to
come
through
as
of
today,
there
is
no
difference
in
how
we
should
do
things,
but
I'm
I
am
updating
the
docs
and
things.
C
A
An
incident
at
that
point
yeah
and
link
them
together.
So
that's
that's
totally
fine.
We
are
we're
trying
to
avoid
having
incidents
running
where
we
don't
need
our
incident
so
yeah
as
soon
as
you
do
need.
To
be
honest,
I
won't
be
surprised
if
devastation
changes
in
the
future,
but
for
now
this
is
the
process
but
yeah
as
soon
as
you
need
one
just
open
an
incident
and
we
can
link
them
together.
A
It
hasn't
actually
happened
so
many
times
that
we've
needed
that
we
have
quality,
really
engaged
with
this
kind
of
the
release
issues
italy
have
been
as
well,
so
I
think
we're
seeing
a
lot
of
specific
development
teams
being
really
really
engaged
here.
The
only
times
where
we
have
is,
if
we're
investigating,
like
a
test
failure-
and
we
discover
like
staging,
has
gone
odd,
yeah
and
at
that
point
and
an
investigation
into
staging
needs
to
kick
off,
but
that's
the
eac.
A
Cool
okay:
well,
we
don't
have
any
release
managers
on
the
call
so
we'll
skip
three.
Is
there
anything
else?
Anna
wants
to
bring
up
on
this
recording.