►
From YouTube: 2022-08-22 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).
B
A
Happy
22nd
of
august
we've
got
a
few
out
of
office
announcements
up
in
the
in
the
top,
so
great
news
there
enjoy
hope
you
all
enjoy
family
and
friends,
which
is
next
29th
next
monday
29th,
if
you
haven't
already,
if
you
plan
to
take
it
off-
and
you
haven't
already
got
that
into
routes-
please
do
pop
it
in
there,
so
we
we
can
see
who's
available
and
who
is
not
if,
for
whatever
reason
the
20
nights
doesn't
work
for,
you
feel
free
to
select
another
day
as
an
alternative,
family
and
friends
cool,
so
discussion
items.
A
So
I
just
wanted
to
drop
in
it's
just
a
little
bit
less
of
a
discussion
unless
people
want
to
discuss,
in
which
case
please
go
for
it,
but
I
did
just
want
to
drop
in
a
little
mention
that,
thanks
for
all
the
comments
on
the
team,
split
and
kind
of
domain
discussion
that
we
started
off
last
week,
it's
something
which
we'll
definitely
be
continuing
to
refine
and
scope
and
sort
of
we'll
have
some
updates
that
we
can
post
on
there
to
try
and
improve
clarity
and
kind
of
set
things
up.
A
So,
even
though
not
everything
has
been
addressed,
or
most
of
it
hasn't
been
addressed,
yet
we
have,
we
have
heard
you,
so
please
continue
if
you've
got
any
other
questions
or
suggestions,
or
things
like
that,
so
you
know
like
please
just
keep
dropping
them
on
there,
we'll
be
we'll
be
updating
on
the
issue.
As
we
can
cool
myra.
You
have
point
b.
C
Yes,
thank
you,
so
I
wanted
to
bring
to
your
attention
the
issue
that
we
had,
I
believe,
last
thursday.
C
So
summarize,
merchant
quest
was
merged
and
this
merch
request
was
updating
a
front-end
library
which
caused
for
our
deployments
to
increase
around
30
minutes,
because
compilation
times
were,
for
some
reason,
also
increased
now
to
deal
with
it.
Grains,
prepare
a
merch
request
to
update
the
waiting
time
in
the
release
tools,
and
this
was
necessary
because
otherwise
our
checks
were
failing,
because
we
automatically
expect
only
30
minutes
of
release
times
now
as
an
upcoming
release
manager.
C
I
am
kind
of
anxious
about
this
because
I
don't
really
want
to
add
another
30
minutes
to
our
deployment
pipeline,
so
I
am
inclined
to
revert,
but
I
also
wanted
to
bring
this
to
your
attention,
because
we
don't
really
have
a
streamlined
process
on
how
to
deal
with
this.
For
example,
if
a
merch
request
is
added
later
and
that's
10
minutes
to
our
release
pipelines,
are
we
okay
with
it?
C
Are
we
not
okay
with
it
or
if
another
merge
request,
adds
20
minutes
to
our
deployment
pipelines
and
we
are
just
going
to
say
no
or
how?
Where
is?
I
guess,
I'm
not
clear:
where
is
the
line
if
there
is
a
line
or
if
we
should
automatically
reject
every
increase
to
our
deployment
pipelines
or
if
there
is
a
better
way
to
deal
with
this?
A
Super
question:
I
I
don't
think,
there's
a
black
and
white
answer.
I
don't
think
we
can
automate
this
to
say,
auto
reject
or
we
just
accept
like.
I
don't
think
either
of
those
will
work
well,
but
I
do
suggest
that
we
start
a
discussion
on
this,
so
I
I
suspect,
I
think,
quite
often
when
these
sorts
of
changes
get
merged,
people
don't
know
the
impact,
so
our
job
is
primarily
to
help
them
see
the
impact
to
explain
you
know
what
is
the
cost
of
this
like?
What
are
we
seeing?
A
This
is
where
things
like
deployment
slo
become
our
sort
of
important
metrics
right
where
we
can
show.
This
is
the
impact,
and
this
is
this
is
this-
is
the
cost
of
basically
this
change
and
then
I
think
it
is
a
bit
of
a
discussion
around
the
value
that
comes
from
the
change
versus
the
cost
that
we're
now
seeing
from
this
change.
A
So
on
this
issue,
specifically,
so
is
the
issue
that
you
linked
here.
Is
this
the
one
with
everything
on
it
so,
like
I
see
graham,
is
assigned,
but
is
this
is
graham
dealing
with
this
or
do
graeme
just
extends
the
tools.
C
I
think
great
graham's
it
himself
because
this
was
blocking
the
auto
deploy
pipeline,
so
we
needed
to
fix
it,
and
then
he
created
the
merch
quest
to
extend
the
weight
in
time,
but
I'm
not
sure
if
he's
actually
working
with
the
outdoors
to
get
clarifications
on
things.
He.
The
author
mentioned
that
he
is
working
on
how
to
improve
the
timings,
but
there
is
not
an
expected
timeline
or
unexpected
outcome
out
of
it.
A
Okay,
do
you
want
to
maybe
give
catch
up
with
graham
and
find
out
like
between
the
two
of
you
like
what
what
other
pieces,
but
I
would
suggest
we
get
this
written
up
in
a
way
where
we
kind
of
summarize
what
you
just
said:
myra,
where
it's
this
change
has
gone
in
here
is
the
cost
we're
seeing
on
every
pipeline
and
from
there
we
lead
a
discussion
with
front
end
on
other
alternatives.
Do
they
have
other
ways
to
get
their
change
through,
which
won't
inc
lead
to
this
increase.
A
Because
I
think
scanning
on
this
issue
is
the
stuff
in
the
in
the
description
is
great,
where
graham's
got
all
the
timings,
but
I
think
when
I
read
the
comments,
it's
not,
I
don't
think
I
can
easily
see
the
the
well.
Maybe
it
hasn't
happened
already,
but
I
think
we
should
go
to
to
somebody
in.
A
In
front
end,
so
I'm
just
trying
to
scan
this.
Okay,
so
maybe
dennis
is
the
person,
but
I
would
say,
let's
ask
them
on
like.
Is
this
the
only
option
we
have
right
like
because
this
is
quite
a
big
cost
for
every
pipeline
to
to
take
so
much
longer,
and
I
think
it's
certainly
worth
considering
like
what
is
the
change
they've
made
and
is
this
the
only
option
and
we
can
then
escalate
to
other
people
if
needed,.
D
I
think
reading
is
common,
that
it
was
kind
of
yeah.
We
are
upgrading.
This
is
a
third
party
library,
so
we
are
upgrading
it.
We
are
not
even
at
the
end
of
this
upgrade
process,
so
it's
gonna
change
as
well
in
the
future,
and
we
have
some
way
to
deal
with
this.
That's
the
reason
why
he
said
I'm
trying
to
figure
out
if.
D
I
was
probably
we
can
also
there's.
No,
there
are
no
clear
lines
here.
I
totally
agree
with
you
amy.
I
was
also
trying
to
figure
out
where
this
is
a
delivery
problem
and
where
this
is
distribution
problem,
because
we
are
just
affected
by
this
affected
by
this,
but
actually
it's
it's
distribution
pipeline.
D
C
E
A
Cool
thanks
for
bringing
that
one
up,
and
I
think
kind
of
just
to
sort
of
summarize
on
on
this,
what
you
say
myra
like
we.
We
certainly
have
some
of
these
things
that
will
sort
of
just
come
in
and
are,
unfortunately,
we
have
to
just
accept,
but
also
not
everything,
because
I
think
quite
often
what
we,
what
we
find
is
just
people
don't
realize
so,
actually,
quite
often,
if
we
can
just
help
people
understand
the
impact
of
this
change,
they
themselves
understand
the
kind
of
significance.
A
Cool
so
moving,
then
to
section
three
release:
managers.
E
I'm
not
saying
like
I
can
tell
you.
E
Okay,
so
I've
not
marked
today's
problem,
but
we
had
a
qa
failure
in
staining
canary,
I
think
about
two
and
a
half
hours,
so
not
much
otherwise.
Last
week
was
good.
I
don't
remember
what
happened
here.
E
18Th,
oh,
this
was
no
problems
with
auto
deployment,
but
just
a
lot
of
other
problems
which
meant
that
we
missed
promoting
a
few
packages.
E
A
For
sort
of
future
reference
on
those
ones
like
do
always
feel
free.
If
you
become
overloaded
by
something
more
critical
to
to
mention
like
hey,
I
have
no
capacity
to
handle
auto
deploys
because
yeah,
it's
fine
to
prioritize
that,
but
it
also
could
be.
Someone
else
has
capacity
to
take
over
promotion
of
things.
E
Yeah
yeah,
though
sometimes
it's
also
affected
by
what's
happening.
E
This
I've
still
not
understood
what
happens
over
here,
because
usually
mondays
tend
to
have
a
high
lead
time,
but
some
weeks
it
just
it
doesn't.
B
B
So
this
was
easy
to
diagnose,
because
when
you
hop
onto
the
node,
you
saw
that
it
didn't
have
any
memory
left
and
the
cpu
was
just
kind
of
chugging
away,
trying
to
figure
out
what
to
do
with
itself.
So,
since
qa
was
kind
of
in
a
failed
state,
I
went
ahead
and
bumped
the
instance.
I
just
doubled
the
amount
of
ram
required
on
that
instance,
which
may
be
too
much.
I
did
not
evaluate
the
instance
aside
from
the
fact
that
qa
was
passing
and
working
that's
effectively
that
effectively
took
care
of
the
immediate
issue.
B
I
left
this
issue
open
such
that
we
could
probably
redo
qa
just
to
make
sure
that
we're
not
over
provision
on
ram,
because
at
this
moment
in
time,
we've
effectively
doubled
the
cost
of
this
instance,
and
this
node
is
only
required
like
once
a
month.
So
it's
like
really
really
costly.
As
far
as
how
much
we're
paying
for
this
tiny
little
thing
that
really
doesn't
do
much.
B
That
might
be
something
that
we
need
to
address,
or
we
could
just
leave
it,
and
you
know,
just
you
know,
tell
someone
to
whatever
the
bill.
Whatever.
D
I
think
I
don't
remember-
maybe
it
was
with
amy
had
to
remember.
We
had
a
conversation
about
something
like
this
in
the
past.
We
were
thinking
about
so
long
story
short,
so
we
use
release
instance
just
for
the
target
release
we
were
thinking
about.
How
can
we
extend
backwards
or
in
general
thinking
about
backwards
and
running
qa
on
and
every
release
right
and
then
we
thought
about,
and
then
we
need
an
environment
for
each
one
of
this
to
run
keyway
and
things
like
this
and
will
be
costly.
D
E
Is
this
aligning
john
with
the
point
three
of
your
comment
on
the.
B
Issue
yeah,
so
I
left
the
issue
open,
not
with
new
acceptance
criteria,
just
more
like
a
status
update
of
hey.
This
has
been
bumped
at
this
moment
in
time,
consider
reevaluation
and
then
maybe
consider
opening
an
issue
to
address
exactly
what
alessio
stated.
B
I
think
it's
a
fantastic
idea,
but
it's
going
to
take
a
lot
of
effort.
That's
certainly
going
to
be
an
epics
worth.
Project
it'll,
probably
be
more
important
if
we
start
extending
our
back
port
policy
anyways.
That
way,
we
have
appropriate
test
mechanisms
for
those
instances,
because
currently
we
don't
have
anything
at
all
as
it
stands.
B
So
I
just
wanted
to
raise
this
his
attention.
Last
week
I
added
this
to
the
agenda
prior
to
actually
bumping
the
instance,
so
this
is
more
of
a
notification
at
this
moment
in
time.