►
From YouTube: 2021-04-12 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
B
A
We'll
let
you
know
it's
like
you
know:
if
your
internet
gets
a
bit
unstable,
we
know
it's.
Not
it's
not
fully
working
right.
I'm
expecting
good
things
from
these
vaccines
awesome
so
dropped
in
mttp.
I
see
we're
still
having
some
incidents
and
things
going
on
last
week,
but
it
is
looking
super
healthy,
so
great
work,
yurik
and
robert
and
maria
for
helping
out
as
well
so
on
the
announcements.
A
So
we
we
should
do
say
sync
so
that
everyone
can
get
involved.
But
if
you
haven't
already,
please
have
some
spend
some
time
looking
through
the
q2
proposal,
thanks
to
everyone,
who's
left
comments
on
already
there
are,
it's
definitely
open
for
discussion.
I
think
probably
the
big
thing
is.
Is
it's
still
too
much
right?
That
was
probably
the
thing
I
was
thinking
of
last
week.
Is
we
still
have
a
lot
of
other
things
so
have
a
think
about.
Is
there
a
way
we
can
make
it
smaller?
Should
we
make
it
smaller?
A
Should
we
drop
stuff
to
make
you
two
a
little
bit
less
stressful,
but
our
goal
is
to
be
good
to
have
a
sort
of
good
idea
of
what
we
want
to
do
by
the
end
of
this
week,
and
then
we
can
spend
the
next
couple
of
weeks
last
two
weeks
of
the
quarter,
just
getting
those
things
written
up
and
kicked
off
cool
and
then
myra
out
thursday,
very
nice
cool.
So
I
was
discussion
point
sent
so
on
wednesday.
We
have
an
ama.
A
Just
like
I'm
wondering
whether
something
like
we
could
put
out
like
super
lightweights,
we're
all
quite
busy
but
like
just
in
the
kind
of
announcement
of
it's
an
ama,
whether
we
encourage
teams
who
you
know
have
things
coming
in
14.0
breaking
changes
if
they
want
to
come
and
discuss
with
us
how
we
can
make
that,
like
as
little
pain
as
possible,
then
yeah.
That
could
be
a
good
one.
C
Do
do
we
know
if
there
is
an
issue
collecting
all
the
breaking
changes
already
there
is.
C
A
Yeah,
exactly
cool
okay,
I'll
drop
that
in
in
the
slack
channel
as
well.
So
we
can
take
that
async.
So
I
know
we're
missing
a
couple
of
people
today
so
and
then
yeah.
So
maybe
I
thought
unless
you
have
following
on
from
your
slack
comment.
A
Actually,
if
we
do
want
to
try
and
do
this
this
week,
good
to
work
out
what
our
plan
is
for
this
production
rollback
this
week
feels
like
a
good
week,
because
next
week
we'll
be
into
release
prep
well
into
release
prep,
so
that
feels
a
bit
risky,
so
goals,
we're
aiming
for
a
dry
run,
rollback
right.
C
C
So
I
mean
it
really
depends
if
if
we
manage
to
get
the
security
fix
out
and
then
we
also
have
maybe
the
next
production
deployment,
because
I
don't
want
to
mess
with
security
release
with
just
us
trying
to
do
rollbacks
or
things
like
that,
even
if
we
are
not
doing
a
roadblock.
D
D
I
think
they
were
in
a
similar
state
on
friday
and
there
were
some
stuff
just
added
last
minute,
related
to
all
everything,
either
way,
there's
a
couple
merch
requests
that
are
tied
into
each
other
still
on
the
review,
so
I
would
suspect,
probably
we
won't
start
the
security
release
until
the
u.s
time,
depending
a
bit
on
the
review
cycle,
but
probably
tomorrow,
even
let's
say
that
we
can
start
doing
that
eu
time
tomorrow.
D
That
means
probably
around
the
rollback
time
it
already
is
on
production.
You
know
assuming
fingers
crossed
assuming
everything
works.
I
think.
For
the
most
part,
the
rollback
meeting
should
be
fine,
but
I
I'll
let
you
know
like
let's
say
three
hours
before
the
meeting,
something
like
that.
C
So
please
consider
that
yarick
that
we
in
order
for
tests
this
the
way
we
would
like
to
run
it
in
when
we
run
a
real
one,
is
that
we
want
to
cancel
post-deployment
migration
prior
to
running
this.
So
this
means
that
we
should
have
the
security
release
deployed
and
then
another
deployment
in
the
in
the
same
day
that
we
can
cancel
post-deployment
migration
ahead
of
time.
D
A
We
also
don't
have
to
rush
this
bit
right,
so
the
other
thing
is
the
change
request.
We
have
a
little
bit
of
work
to
do
there
still,
I
think,
and
we'll
need
to
find
a
reviewer,
because
java
is
out,
so
we
might
be
a
little
bit
tight
for
tomorrow
anyway,
but
it's
just
like:
let's
go
ahead
and
get
prepared
and
then
maybe
we
don't
do
the
rollback
in
a
demo
meeting,
but
we
can
just
say
like
it's
a
good
time.
We've
got
everything
approved.
A
We
have
a
couple
of
people
are
free
for
two
hours.
You
know
like
it
doesn't
actually
have
to
be
all
of
us
as
long
as
a
few
people
can
watch
it
and
we
can
record
it.
E
Cool
so
let's
have
a
question:
the
rollback
do
we
need
to
cancel
the
post-deployment
job,
even
though
we
are
doing
a
dry
run.
C
A
A
Euric,
do
you
want
to
tell
us
when,
like
be
the
person
that
basically
says,
like
security
release
done
this
there's
another
deployment?
That's
happened
with
safe
to
go,
and
then
we
can
work
out
like
what
we
do
with
the
cr.
Getting
that
ready
and
approved,
and
then
we'll
actually
have
the
step
of
like
okay,
we're
entering
into
our
rollback
kind
of
test,
and
we
can
actually
stop
the
post-deployment
migration
and
planner
times
kind
of
three
pieces.
I
think.
D
Yes,
I
I
will
let,
unless
you
know
tomorrow,
this
is
probably
gonna
be
also.
The
first
employee
usually
done
is
like
one
two
o'clock
give
or
take
so
around
that
time
we
would
know
more.
D
A
C
Yeah,
basically,
that
one
was
designed
around
the
old
idea
of
just
doing
everything
without
cancelling
so
just
deploying
something,
and
so
we
need
to
modify
it
a
bit
to
what
we
will
test
in
dry
run
as
well
as
I
think
we
need
to
provide
some
links
or
information
where
all
the
tests,
so
what
we
tested
so
far,
which
is
basically
the
rollback
scenario.
C
Discussion
issue,
which
is
all
the
discussion,
there's
a
kind
of
outline
at
the
top
now,
and
maybe
just
we
can
create
a
nice
table
which
is
maybe
easier
to
to
get
destruct
information
from.
A
Okay,
that
makes
sense,
are
you
gonna
have
time
to
see
the
table.
A
So
if
you
do
the
table
myra,
do
you
think
you'll
have
any
time
today?
I
know
it's
very
security
release
dependent,
but
if
you
did,
we
could
take
some
slack.
I
guess,
but
I'm
kind
of
thinking
like
if
you
had
time
today.
Maybe
you
could
make
a
first
pass
on
the
cr
and
get
that
ready
and
then
tomorrow
alessia-
and
I
could
do
some
work
in
the
morning-
to
get
the
table
added
in
finish
off
any
bits
you
didn't
get
to.
A
We
could
try
and
get
that
approved
before
you
start
tomorrow
and
then
in
the
afternoon
we
can
maybe
try
and
set
this
up.
A
Yes,
of
course,
does
that
make
sense
I'll
summarize
in
slack
there's
a
few
pieces,
but
I'm
thinking
there's
like
maybe
three
or
four
bits
we
can
keep
moving.
All
of
this
is
security
release
dependent,
of
course,
like.
We
should
prioritize
that,
above
everything,
so
cool
fantastic.
I'll
summarize,
thank
you,
cool,
okay,
I'm
going
to
stop
the
recording,
so
we
can
move
on
to
the
next
topics.