►
From YouTube: 2021-10-25 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
Welcome
back
hello,
welcome
hello
there.
I
think
this
may
be
all
of
us,
I'm
not
sure
if
reuben
is
joining
us
today.
Possibly
it's
not,
and
everyone
else
is
out
so
we're
pretty
light,
but
ahmed
has
joined
us
so
yeah,
it's
also
slightly
higher
numbers.
So
thank
you
awesome.
A
So
I'm
gonna
do
a
slightly
different
format
today,
since
we
don't
actually
have
any
release
managers
in
this
meeting
just
on
the
so
I
should
say
this
is
our
weekly
delivery
meeting.
Is
this
recorded
and
we'll
put
this
public
I'll
make
a
section
towards
the
end
where
we
have
we'll
stop
the
recording
and
do
a
bit
of
a
chat?
So
if
there's
anything,
anyone
wants
to
share
outside
the
recording,
save
that
for
towards
the
end
of
the
meeting
on
the
recorded
section.
A
So
just
a
heads
up
really
that
lots
of
people
have
time
out
today
and
then
through
this
week
and
next
week,
so
I
don't
think
there's
any
great
problem
with
that,
we'll
just
adjust
like
our
capacity
and
things,
but
if
you're
particularly
waiting
on
any
specific
people.
Please
factor
these
dates
in
around
your
your
requests.
A
I'll
move
the
backboard
request
discussion
item
into
an
issue.
I
think
so
a
kind
of
brief
summary
of
that.
If
we've
been
asked
to
do
a
couple
of
back
ports
to
go
back
to
1312.,
we
we
may
we
may
need
to
do
this,
but
we'll
certainly
the
main
thing
I
wanted
to
kind
of
remind
everyone
is
just
to
make
sure
all
these
requests
go
through
the
process
and
people
are
filling
out.
The
the
full
docs
reuben
is
with
us,
hey
ruben.
A
Is
he
here?
No
he's
not
he's
just
writing
on,
because
I
was
like.
Oh
he's
writing
on
the
agenda.
I
thought
I
have
my
tiling.
So
if
you,
when
you
are
release
managers
like,
I
just
want
to
make
a
reminder
that,
like
please
challenge
people
on
these
things
make
sure
everyone's
following
the
process
correctly.
It's
totally
fine
to
say
no
delay
patch
releases
to
a
better
time
or
just
escalate
them
up
to
me.
A
A
It
was
decided
at
the
time
that
no,
we
didn't
need
to
be
supporting
more
versions,
so
I'm
going
to
bring
that
back
up
again
in
this
request
and
we'll
see
how
that
goes,
but
just
as
a
kind
of
heads
up
like
we
don't
have
to
support
every
single
request,
and
that's
why
I
put
in
the
issue
it's
like.
If
we
do
need
to
patch
back
quite
a
few
versions
now,
is
there
anything
that
we
should
now
be
prioritizing?
A
So
if
anyone
has
the
ideas
now,
otherwise
I
will
run
that
past.
One
that
I
know
robert
opened
is.
We
could
automate
the
patch
blog
post,
mr
generation,
so
probably
not
the
whole
blog
post,
but
we
could
do
the
prep,
which
at
least
takes
away
some
manual
stats.
B
Yeah,
but
even
that
one
I
mean
the
so
the
the
real
manual
and
stuff
where
we
lose
say
more
time
is
actually
the
blog
post
right,
because
we
have
to
kind
of
rearrange
the
formatting
make
sure
that
things
make
sense
and
things
like
that,
but
still
it's
just
one
single
post.
So
exactly
so,
even
if
you're,
just
back
porting
10
versions,
it
usually
is
it's
the
same
bug
that
just
got
backported
10
times,
because
it's
very
important
or
whatever
right,
so
it
would
still
be
the
same
blog
post.
B
I
think
the
real
problem
with
supporting
more
versions
is
the
likelihood
that
things
goes
wrong.
B
So
the
real
problem
here
is
that
the
reason
why
we
stick
to
three
is
that
our
code
changed
so
fast
that
three
months
later
is
likely
that
the
thing
cannot
be
cleanly
picked
into
the
stable
branch
and
even
and
so
up
until
this.
No
that's
not
the
point.
So
during
a
security
release,
this
process
is
handled
by
the
developer
themself
because
they
have
to
prepare
three
backboards
themselves.
B
When
we
do
the
regular
patch
releases,
they
don't,
they
just
add
a
label
to
their
merge
requests.
Speaking
to
whatever,
and
if
we
ever
decide
to
run
that
patch
release,
our
tooling
is
backporting
everything,
so
we
just
share
a
peek
everything
that
has
the
label
and
if
he
cleanly
applies,
we
move
on.
If
not,
we
just
leave
a
message.
That's
the
point,
that's
where
the
problem
is
right,
because
there's
no
check
ahead
of
time
if
that
thing
is
compatible
or
not
with
the
disabled
branch.
A
What
we
mean,
what
we
can
certainly
do
for
this
one
is
request:
developer
support
right,
so
this
is
all
going
to
be
around
italy
change
completely
fine
with
us
requesting
that
someone
from
italy
pairs
with
us,
possibly
prepare
you
know
for
a
week
and
then,
if
we
have
any
problems,
picking
they
can
be
the
ones
to
debug.
For
example,
yeah.
B
To
specifically
to
this
one:
yes,
that's
that's,
okay!
This
is
just
the
first
point
of
failure
of
this
process
right
because,
okay,
it
may
fail.
You
usually
fail
if
it's,
if
you're
back
porting
to
all
the
releases
and
when
it
basically
we
decide
to
run
the
patch
release
and
then,
if
it
fails,
we
are
basically
running
against
time
right
because
we
didn't
know
ahead
of
time,
and
we
rely
on
someone
else
to
fix
that
after
that
point.
The
other
point
that
usually
fail
is
qa
or
tests
in
general,
because
some
of
them
are
just
flaky.
B
A
Challenge
we've
had
a
lot
of
flaky
tests,
so
lots
of
things
have
been
quarantined
recently,
so
yeah
that
for
sure
those
two
things
are
going
to
be
real
painful.
So
it's
not
going
to
be
a
normal
thing.
We
need
to
make
sure
that
this
is
very
much
if
we
go
ahead,
I'm
happy
to
push
back,
but
if
we
do
go
ahead,
it'll
be
truly
exceptional.
B
A
And
if
I
say
if,
if
it
becomes
not
the
exception,
if
this
becomes
the
norm,
then
we
can
look
forward
to
adding
some
more
people
to
our
team
and
automating
patch
releases
right,
which
is
the
other
way
awesome.
7B
reminder
if
you
haven't
done
so
already.
Please
could
you
contribute
to
the
q4
okr
discussion?
I
am
I've
got
a
due
date
of
today.
I'm
happy
to
extend
it
for
a
day
or
two,
but
I'd
really
like
to
know
kind
of
the
it
doesn't
have
to
be
exact.
A
One
note
on
q4
is
it's
a
shorter
quarter,
obviously,
because
the
holidays
more
people
will
be
off
so
let's
not
be
too
ambitious
and
and
that's
some
kind
of
good
okrs,
but
like
also
it's
been
a
big
year.
So,
let's,
let's
not
like,
I
think
it
was.
I
think
it
was
scarbeck
proposed
h.a
proxy.
Let's
not
attempt
to
hear
proxy
again
was
like
this
is
gonna
be
way
too
hard.
A
So
we
can
do
stuff
to
set
up
for
q1,
but
please
take
a
look
through
q4
and
see
what
you
think
awesome.
Is
there
anything
else
anyone
wants
to
mention
on
the
recording.