►
From YouTube: 2021-03-08 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
A
Hello
welcome
so
happy
monday,
everybody,
I'm
gonna,
start
dropping
in
the
mttp
in
the
top
of
the
agenda
each
week,
but
this
week
is
super
good
news.
Well,
on
europe,
robert,
I
was
very
happy
to
see
this
number
drop
back
into
central,
sensible
realms
again
today.
So
last
week
it
was
looking
super
hairy,
so
nice
work.
I
have
actually
done
some
kind
of
digging
through
last
week
and
the
some
of
the
things
that
factored
into
that.
A
So
I
write
that
up,
like
mostly
just
of
interest
and
nothing
totally
shocking,
just
like
just
how
painful
it
is
when
we
have
early
morning
like
master
failing
and
that
sort
of
unsurprising
right
but
yeah.
So
nice
work
there
on
the
announcements
front.
So
I
just
want
to
make
sure
this
new,
family
and
friends
days
have
been
announced.
A
I'm
also
going
to
follow
up
and
see
if
we
can,
although
they
are
awesome,
I'm
going
to
follow
up
and
see
not
to
change
these
ones,
but
in
the
future,
if
we
cannot
put
them
right
before
the
22nd,
because
it's
quite
painful
so
we'll
see
if
we
can
actually
push
them
out
further
down.
But
still
these
are
good
to
have
in
the
calendar.
You
can
look
forward
to
those
and
then
I
want
to
make
sure
everyone
had
seen
this.
A
The
changes
to
the
equity
refresh
policy
emma
have
a
read
through
it.
Have
a
read
of
the
comments.
Please
add
a
comment:
if
you
have
a
question
or
thoughts
you'd
like
to
share
it's
a
manager
mention,
mr
so
ping
me
on
that
one
and
we
will
make
sure
you
get
an
answer,
but
that's
going
to
move
quite
quickly.
I
think
so.
If
you
haven't
read
it
already,
then
you
know
prioritize
it
earlier
in
this
week,
oh
alessio.
A
Whichever
you
throw
something
you
want
to
highlight
in
the
announcements,
go
for
it
if,
if
not
or
henry,
as
well
like
yeah,
if
there's
anything
you
want
to
highlight
in
your
announcements,
go
for
it.
B
Well,
well,
let's,
let's
go
with
it
this
time
and
we
see-
maybe
we
get
better
over
time
with
this,
so
these
are
the
first
epic
is
the
single
pipeline
and
basically
myra
and
I
scope
part
of
the
work
for
triggering
every
single
environment,
so
she's
picking
up
this
type
of
work-
and
this
is
something
that
we
provide
us
some
booking
point
for
the
for
rolling
back.
So
then
the
next
agenda
item.
B
So,
regarding
the
rollback
I
just
went
through
some
of
the
issues
I
created
some
follow-up
items
for
the
chat
ups
command,
also
based
on
the
introduction
of
tracking
running
deployments,
and
so
this
is
a
link
of
items
and
things
like
that.
I
closed
some
issues,
so
just
that's
it!
Every
next
item
is
your.
C
Yeah
I
just
wanted
to
update
you
that
I
did
some.
I
committed
some
stuff
of
the
readiness
review
for
the
api
move
to
kubernetes.
I
looked
into
this
a
while,
but
I
didn't
commit
much
because
I
was
still
reading
about
it,
and
so
there
are
a
few
draft
marks
out
now,
but
they're
not
fully
finished
yet
so
maybe
don't
start
reviewing
it
already
now,
but
there's
something
at
least
to
look
at.
C
If
you
are
interested
in
and
to
get
this
as
complete
as
possible,
I
could
copy
a
lot
of
the
already
existing
web
sockets
and
and
get
https
identifiers,
but
I
also
wanted
to
add
a
little
bit
to
the
api
service
on
itself.
C
That's
why
it
took
a
little
bit
longer
because
we
don't
have
any
run
books
for
specific
for
the
api
service
or
architectural
overviews,
or
things
like
that.
It's
more
spread
over
all
other
documentation,
so
that's
included
in
the
first
for
the
the
second
amount
for
for
run
books
there
yeah,
that's
the
only
thing
I
wanted
to
say.
A
Nice
thanks
for
sharing
cool
alessia.
B
Thank
you
so
something
that
I
realized
with
amy.
Today
we
were
discussing
about
this
rollback
check
and
there
was
kind
of
confusion
about
terms
because
we
always
refer
about
rolling
back.
B
We
have
two
versions
in
mind
so
current
and
previous,
but
then
we
realized
that
if
there
is
an
ongoing
deployment,
then
we
have
three
version,
so
we
want
to
so
the
idea
here
behind
this
issue
is:
we
should
think
about
how
we
want
to
the
name
of
those
things
and
have
a
common
vocabulary
around
this,
so
that
we
always
refer
to
what
is
being
deployed
at
the
moment
or
the
last
successful
production
deployment
and
the
one
before
that
with
the
same
term,
so
that
we
always
understand
what
we
are
talking
about.
B
So
I
mean
please
chime
in
in
the
issue
or,
if
you
want
to-
and
my
proposal
was
about
ongoing
for
the
things
that
started
but
is
not
yet
completed,
then
current
for
the
last
successful
production
deployment,
which
in
case
of
an
ongoing
deployment,
will
not
be
the
whole
fleet
because
it's
getting
updated
and
previous
is
the
success.
Last
successful
deployment
brief
before
the
current
one.
A
B
A
D
So
I
I
may
be
thinking
too
far
ahead
here,
but
in
a
model
where
we
have
multiple
versions
running
in
production,
I
think
are
still
a
couple
years
ahead
from
this,
but
at
that
point
the
the
term
current
or
ongoing
even
becomes
even
more
ambiguous.
That's
something
we
perhaps
want
to
take
into
account
here
or
just
shelf
that
until
it's
an
actual
concern.
D
I
I
don't
have
right
now,
but
then
in
kenya
there's
only
two
difficult
things
in
programming
naming
being
one
of
them.
I
think
it
by
saying
that
I
answer
my
own
question,
as
perhaps
just
you
know,
ongoing,
etc
might
be
the
the
best
choice
for
now.
E
Yeah,
I
think
the
term
current
is
problematic
because,
if
something's
rolling
out
and
then
it
switches
where
the
majority
is
now
the
upcoming
version
and
the
minority
is
what
was
previously
running,
I
think
maybe
upcoming-
I
just
lost
the
word.
I
was
going
to
use
I'll
come
back
to
you
running
stable
life
latest.
C
A
I
mean
what
about
if
we,
if
we
did,
take
your
extort
a
little
bit
further
right,
so
in
an
ideal
world
like
in
the
future,
something
we're
always
going
to
be
deploying
right
like
because
we'll
be
moving
so
fast.
So
what
about?
If
we
assume
that
this
version
is
always
changing,
and
you
have
kind
of
like
incoming
outgoing,
I
mean
it
means
the
number
changes.
That's
super
confusing,
but.
B
A
B
B
A
What
about
income
you
have
like
incoming
outgoing
or
something
that
just
kind
of
implies
the
the
movement?
Those
are
not
the
right
names
really.
B
The
yeah.
D
A
You
know
well
enough
to
decide
if
we
do
a
rollback
and
also
to
talk
about
when
we
are
doing
a
rollback
like
what
what
are
we
changing
this?
I
think,
as
long
as
we
had
words
to
describe
those
two
scenarios-
probably
I
guess
it
doesn't
matter
too
much
what
they
are.
We
should
just
consistently
apply
them.
A
Yeah,
okay,
shall
we
because
this
is
going
to
be
one?
I
guess
that
we
don't
have.
There's
no
perfect
answer
right
so
should
we
all
have
a
think
about
it,
and
then
we
could
just
finalize
it
in
the
demo
meeting
tomorrow.
B
So
I
had
a
proposal
here
so
in
that
issue
there
is
another
one
linked,
because
I
I
was
trying
to
explain
an
issue
which
involved
the
tree
version,
so
I
wrote
it
out
in
bold
with
with
those
german
balls,
so
I
think
the
good
example
would
be.
Could
you
explain
the
same
concept
with
your
own
words,
so
you
you
can
try
to
write
the
same
sentence
and
does
it
make
sense.
A
Okay,
that's
a
great
one,
okay!
So
for
tomorrow's
demo
meeting
I
have
a
it's
like
a.
I
feel
like
we're
school
homework
right,
so
rewrite
the
scenario
in
your
own
words.
A
A
Also,
just
a
small
update
on
rollbacks
and
production,
so
alessio
and
marion.
I
have
had
various
chats
today
and
we're
going
to
add
in
some
we're
going
to
try
and
identify
like
possible
failure
scenarios
of
what
might
go
wrong
when
we're
doing
rollbacks,
and
then
we
can
work
out
we'll
probably
want
to
test
some
of
these
on
staging
before
we
try
and
prod.
B
Yeah,
there's
also
an
extra
actionable
item
from
that
meeting,
which
is
we
would
like
to
test
production
with
a
dry
run
deployment,
but
before
that
we
want
to
test
staging
with
a
drive
around
deployment
to
make
sure
that
it's
actually
a
dry
run.
A
A
A
I
completely
forgot
to
put
in
the
announcements,
there's
an
ama
on
wednesday,
so
what
I
would
suggest
I'd
like
to
share
like
announce
it
and
share
anything
we
have
to
share
tomorrow,
like
24
hours
ahead,
so
I
will
put
together
a
bit
of
an
empty
slide
deck
like
a
skeleton
slide
deck
similar
to
what
I
did
last
month.
A
If
you
want
to
contribute
something
like
an
mri,
you
had
a
couple
of
suggestions
like
if
anyone
wants
to
actually
like
put
together
a
short
video
or
put
together
a
topic
that
we
could
share.
Please
go
ahead,
just
drop
it
in
there
and
then
tomorrow,
around
my
lunch
time,
I'll
like
fill
in
any
gaps
and
make
sure
we
have
like
say
three
slides
that
people
could
have
a
read
through
ahead
of
the
ama
if
you're
doing
a
chance.
That's
also
totally
fine,
like.
A
I
think
what
we
can
also
do
is
have
like
a
fairly
regular
ama
people
turn
up
ask
questions
and
we
can
use
that
to
decide
like.
Oh
here
are
the
gaps
like
we
had
three
questions
about
this
topic,
so
that's
clearly
a
gap
and
we
can
we
can
feed
it
off
that
way,
but
if
anyone
does
want
to
go
ahead
and
create
a
video
or
so
then
please
do
that
today.
F
A
Yeah
I
mean
it
it
I
think
we
should
review
like.
Yes,
it
would
be
fantastic
to
have
you
both
there.
Really.
I
think
it's
totally
fine
like
we
can
see
how
we
go
this
month.
If
there
are
any
questions
that
we
can't
handle,
that's
fine.
We
can
come
back
to
people
later
with
an
answer.
That's
okay!
A
C
A
I've
been
kind
of
deliberately
avoiding
kubernetes
discussions
the
last
month,
or
so
just
so
that
you
know
we
don't
go
hey,
let's
have
a
big
chat
about
kubernetes
and
then
you're
not
there
to
like
join
in
basically
cool
cool
and
then
the
other
one
is
exciting.
Graham
will
be
joining
us
next
monday,
so
graham
is
moving
over
from
core
improv.
He
is
fairly
familiar
with
some
of
us
at
least,
and
some
of
our
work.
He
does
quite
a
lot
of
delivery.
Sort
of
tasks,
like
you
know,
he's
very
interested.
A
Kubernetes
he's
helped
us
a
lot
with
the
migration,
so
it'll
be
super
to
have
min
here,
and
he
is
in
apac,
which
is
also
very
exciting,
because
it
gives
us
some
release
manager
coverage
from
the
apec
region.
So
we
should
find
that
incidents
that
run
out
beyond
america's
days,
which
won't
be
so
painful
early
morning.
Problems
hopefully
won't
be
so
painful.
A
The
main
thing.
So
there
are
a
couple
of
things:
he'll
be
a
special
type
of
release.
Manager
we'll
have
to
work
out
the
exact
details,
that's
going
to
be
because
only
graham
is
out
in
aipac
he's
also
going
to
be
on
cool,
so
it
won't
be
quite
the
same
rotation
as
we
have
any
other
time
zones,
but
certainly
he
should
be
able
to
ease
our
lives
a
bit
there
and
the
other
one.
The
bigger
challenge
is
we
no
longer
have
a
time
where
the
whole
team
is
online.
A
So
what
I'm
going
to
propose?
I
think
the
most
important
thing
that
we
do
here
that
graham
won't
miss
like
so
regular
meetings
and
things
are
fine,
like
we
have
recordings
demos
and
things
like
that,
and
no
no
great
problem.
It's
probably
the
social
piece,
that's
the
biggest
gap
right,
because
we
don't
record
that.
So
what
do
you
think
us
having
a
delivery,
social
slack
channel?
We
can
take
some
of
this
async
and,
like
kind
of
supplement,
our
conversation.
A
So
it's
not
like
a
total
you're
either
in
it
or
you're,
not
in
it
type
of
view
and
see
how
that
goes,
and
we
can
then
we
can
work
it
out
like.
We
could
also
consider
staggering
this
meeting.
So
that's
like
some
weeks,
it's
in
the
afternoons
like
or
like
early
mornings
for
us
lot
and
then
other
times.
It's
like
more
of
a
time
that
suits
graham-
and
we
just
accept
that
we
won't
have
everyone
on
every
call,
but.
A
Cool
okay,
I'll
put
in
a
slight
channel.
I
know
we
can
chat
to
graham
next
week,
at
least
about
what
he'd
like
to
do
and
like
you
know
how
he
you
know
what,
if
there's
additional
stuff
he'd
like
to
do
beyond
like
coffee,
chats
and
whatever
regular
one-to-ones
with
with
any
of
you
where
he
does
overlap,
but
yeah
I'll
put
together
a
plan
so
that
we
actually
can
kick
things
off
with
him
next
week,
but
yeah
exciting
stuff
awesome.
Is
there
anything
else
anyone
wants
to
bring
up
on
this?
Recording
I've.