►
From YouTube: 2021-03-29 Delivery team weekly
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
Hello,
so
I
don't
think
robert
can
make
this
because
he
went
off
to
get
his
kovitch
vaccine
so.
A
Of
course
I've
also
shifted.
I
I
have,
I
think,
what
we
do
for
next
week.
It's
got
a
public
holiday
on
monday,
whether
it's
worth
shifting
it
later
in
the
week
or
we
could
just
do
a
delivery.
Lounge
just
do
like
async,
and
we
get
graham
involved
in
that
as
well,
but
we
can
see,
but
for
the
weeks
after
I've
moved
it.
So
it's
this
time
ongoing,
so
yeah,
so
mttp
is
looking
pretty
good.
Actually,
all
things
considered
21.2
is
our
current
value.
A
We
have
changed
the
target
temporarily
so
currently
aiming
at
24
hours
and
once
we've
had
two
weeks
without
significant
incident
impact
we'll
pop
that
back
to
12
hours,
so
the
red
line
is
still
where
it
was
on
12
hours,
but
just
the
next
couple
of
weeks,
we'll
be
tracking
at
24.
A
Cool
and
then
announcements
loads
of
people
out
this
week
so
yeah
just
be
aware
of
that.
Really
things
may
be
a
bit
slower
if
we're
waiting
on
people,
discussion,
items.
B
A
14.0
has
moved
back
to
june
and
there's
a
13.12
has
been
added
in
before
then,
which
hopefully
is
a
good
thing,
and
it
means
that
more
tech,
deck
gets
paid
down
before
everything
gets
sort
of
rolled
out
in
14.0.
A
So
I
don't
think
we
have
anything
we
need
to
do,
but
just
as
a
to
be
aware
of,
and
there's
also
the
link
there
that
to
the
issue,
which
has
all
the
breaking
changes
in
it.
So
I
imagine
that
might
change
a
bit
as
we
get
closer,
but
just
to
share
that.
A
Cool
and
then
b
is
something
I
was
chatting
to
robert
about
actually
last
week,
so
just
as
a
kind
of
a
just
to
make
sure
we're
on
the
same
page,
really
so.
Release
management
is
always
our
top
priority.
Well
incidents
then
release
management.
A
So
if
you
are
a
release
manager
or
when
you
are
a
release,
manager
feel
free
to
ask
people
to
help
you
right
like
it's
completely.
You
know
if
you're
in
a
12
hour
incident,
you're,
surely
going
to
need
some
help
to
step
out,
eat
something
get
some
air
or
whatever.
So
if
people
do
need
help,
please
everyone
else,
like
drop
things.
Worst
cases
everybody's
doing
release
management,
but
still,
if
that's
what
it
takes,
then
that's
what
we
should
be
doing
so
yeah.
If
you.
A
People
please
just
ask
for
for
support
or
second
pair
of
eyes
or
a
cover
or
whatever
you
need
really,
and
then
I
added
in
a
step
into
the
security
patch
process.
So
we
had
a
situation
the
other
week,
where
buric
kind
of
ended
up
bearing
the
burden
of
trying
to
do
a
security
patch,
alongside
preparing
the
monthly,
so
not
to
say
that
we
won't
ever
do
this,
but
just
as
another
step
has
been
added
in
at
step,
one
where
it
won't
be
assumed
that
we
will
immediately
go
into
this.
A
But
the
first
step
will
be
a
conversation
about.
When
should
we
do
this?
So
if
we
are
being
actively
exploited,
of
course,
we'll
need
to
patch
and
take
action,
but
it
basically
hopefully
just
gives
us
a
little
bit
more
of
a
expectation
that
we
should
have
a
conversation
about
when's
the
right
time
to
have
these
things
patched
and
get
them
out
as
soon
as
possible,
but
without
necessarily
risking
you
know,
life
and
limb
and
the
monthly
release
as
well.
A
So
hopefully,
that's
helpful,
but
I
want
you
to
make
sure
people
kind
of
knew
that
this
should
always
be
a
conversation
right.
So
it's
a
the
request
for
back
paw
or
patch
or
whatever
it's
really
always
a.
When
can
we
do
this
and
that's
where
we
should
start
from
rather
than
like
feeling
like
you
have
to
scramble
and
do
it
right
now
or
we
should
never
do
this
thing.
A
A
So
maybe
we
should
put
together
some
little
sort
of
starting
point
templates
if
you
want
to,
if
you're
not
sure
where
to
start
with,
they
could
give
you
a
sort
of
first
point.
B
Yeah,
I
will
say
that
from
my
experience,
usually,
if
you
just
point
out
the
current
plan-
maybe
because
you
have
the
ongoing
release
or
something
like
that,
I've
never
had
someone
pushing
back
on
top
of
that.
Usually
people
are
always
very
understanding
with
release
managers.
Do
you
really
understand?
I
mean?
Maybe
they
don't
think
about
the
pressure,
but
as
soon
as
you
write
down
what
is
happening,
they
usually
back
off
and
say:
okay,
no
problem
we
but
yeah,
probably
having
some
something
written
down,
may
help
yeah.
D
So
I'm
probably
too
grumpy,
but
when
someone
asked
me
about
doing
a
critical
security
release,
I
always
default
to
know.
Unless,
of
course
there
is
an
incident
and
of
course
there
is
fire
in
the
slack
channels.
A
Yeah-
and
I
mean
I
think,
if
we,
if
we
weren't
things
right,
that's
totally
right
like
as
long
as
we
leave
it
open,
say
like
hey,
no
and
here's.
Why,
then
I
do
find
that
quite
often
when
you
start,
even
if
it's
not
as
saying
a
yes
or
no,
if
you
engage
people
in
the
conversation
of
the,
why
it's
interesting,
how
many
people
backtrack
themselves
and
suddenly
like
are
the
ones
saying?
A
Oh
actually,
you're
right,
it's
not
that
important,
so
you
don't
ever
have
to
actually
say
no,
but
just
like
yeah,
like
maybe
like
calencia,
says,
like
laying
out
like
here's
what
we
got
going
on
this
week.
Here's
what
you're
asking
for
are
you?
You
know:
okay,
let's
see
if
we
can
get
some
more
resources,
because
I
think
that's
one
of
the
things
we
go
through
kind
of
like
monthly
releases
and
stuff
is
it's
like
when
we
have
to
post
about
hey
this
release
is
out
or
this
one
is
our
last
commit
right.
A
A
Cool
okay,
I'll
see
what
I
can
do
there
cool.
Is
there
anything
else
anyone
wants
to
talk
about
either
on
the
release
management
priorities
or
on
that
process
and
pushing
back.
E
Yeah
thanks
yeah,
so
this
weekend
we
have
the
easter
weekend
monday,
for
most
people
will
be
a
public
holiday
friday
for
some
here
in
the
netherlands,
for
example,
both
are
technically
public
holidays,
but
a
lot
of
companies
will
only
give
you
off
on
monday,
when
I
kind
of
curious
first
of
all,
who
else
is
going
to
be
out
and
then
second
yeah
we
need
to,
depending
on
who's
out
figure
out,
a
sort
of
replacement
for
those
release.
E
E
But
it's
yeah,
let's
see,
there's
some
people
writing
so.
A
Yeah,
I
just
wanted
to
add
in
so
I
will
be
asking
tomorrow
whether
there
is
going
to
be
pcl
for
monday
anyway,
like
whether,
certainly
on
that
day,
there
could
be
if
there's
lots
of,
or
maybe
john
already
knows,
actually
jobs.
There
are
loads
of
people
out
over
over
the
weekend
from
reliability.
F
A
F
Don't
know
yeah
sorry,
but
it's
not
like
a
u.s
thing
to
take
time
off.
So
I
assume
that
u.s
people
will
be
around
friday.
A
Okay,
awesome
so
yeah
I'll
check
in
on
whether
it
was
actually
going
to
be
a
pcl
over
the
weekend.
It's
possible
certainly
on
monday,
but
the
friday
sounds
at
least
we're
good
to
cover.
So.
E
Yeah
yeah
that
case
yeah,
so
I
put
mine
in
pto,
but
that's
just
preliminary,
I
think
is
the
word
mostly.
So
I
don't
forget
about
it
myself,
because
otherwise
it'll
be
framework.
Oh
yeah
wait!
Yeah!
Let's
then
wait
for
monday
alessio
stated
he
could
take
over
friday
and
then
monday
depends
like
if,
if
there's
no
pcl,
if
they
figure
something
out
there.
E
C
A
Yeah
as
it
stands
right
now,
robert
doesn't
have
time
off
in
peter
in
roots,
so
I
I
mean
worst
case
we
like
robert,
like
you
know,
we've
got
a
little
bit
of
cover
on
monday,
so
that's
that's
fine
cool.
We
could
also
relax
in
our
revel
in
our
24-hour
target.
A
It's
a
little
bit
it's
going
to
look
a
little
bit
less
brutal
this
time
around
awesome
cool,
so
yeah
I'll
confirm
tomorrow
on
whether
there
is
a
plan
for
pcr
and
then
we
can
get
that
logged
in
so.
D
Myra
yep
thanks,
so
the
scenario
for
tomorrow's
rollback
demo
is
outline.
It
is
about
rolling
back
when
the
servers
are
in
a
drain
state,
so
everything
is
described
in
that
part
of
the
issue.
We
just
need
someone
to
drive
this
one
so
who
wants
to
volunteer.