►
From YouTube: 2021-07-05 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
Awesome
welcome
back
henry
cool,
so
mttp
is
looking
really
good
like
when
you
show
it
monthly,
it's
very
effective
by
the
first
week
you
have
so
last
week
we
had
a
really
good
week.
So,
unfortunately,
today
we
are
blowing
mttp
out
the
water
no
deployments
so
far
today,
but
we'll
see
where
it
settles.
We
have
just
16
hours
of
deployment
blockers,
though
last
week,
which,
although
that's
a
lot,
is
not
as
bad
as
some
of
our
recent
weeks.
A
So
yeah
it's
certainly
interesting.
There
were
definitely
some
interesting
things
which
I
noticed,
which
I
didn't
get
a
chance
to
dig
into,
which
I
think
will
come
out
as
we
start
building
out
more
of
deployment,
slo
so
canary
had
a
couple
of
times
last
week
where
it
took
an
incredibly
long
time
to
get
through
its
deployment
early
in
the
day,
which
is
quite
unusual,
but
no
obvious
errors.
A
The
pipeline's
passed
in
the
end,
so
I
think,
we'll
start
to
see
some
quite
interesting
patterns
once
we
we
have
things
a
bit
more
broken
down.
A
Cool
and
then
I've
just
shared
in
here
in
the
announcements
it
says,
read
only
not
read
only
please
make
yourself
aware
of
this
safe
framework,
so
I
think
generally
people
are
saying
that
from
the
training,
training's
really
good
and
it
shows
you
stuff,
but
ultimately
we're
gonna
we'll
get
to
a
stage
where
we
do
need
to
keep
checking
about
sensitive
information.
A
So
please
know
where
to
find
that
for
those
times
and
then
the
thing
I'd
like
to
discuss
with
you
all
is
q3,
so
q3
is
rapidly
approaching
starts
in
august,
goes
through
to
october
and
I'll
open
up
an
issue.
So
we
can
have
an
async
discussion
on
this
as
well,
but
I
was
kind
of
wondering
to
get
your
sort
of
early
thoughts,
I'm
thinking
based
on
the
last
few
quarters
we've
had.
A
We
seem
to
have
a
lot
of
things
in
progress,
and
it
doesn't
always
make
sense
that
it
almost
never
makes
sense
for
us
to
fully
stop
what
we're
working
on
right
now
and
completely
pivot
into
something
new
and
sort
of
set
these
up.
So
I
was
going
to
have
my
sort
of
initial
proposal,
as
we
have
one
okr,
which
would
be
around
kubernetes
to
continue
there.
What
exactly
we
put
in
that
we
can
discuss
that.
A
You
know
maybe
something
around
hardening
the
cluster
or
picking
up
whatever
comes
next
or
whatever
that
looks
like
and
then
for
all
the
other
stuff.
I
think
we
kind
of
have
these
things
grouped
up.
We
have
we'll
almost
certainly
have
some
kind
of
follow-ups
to
deployment
slo,
maybe
the
next
iterations
of
that
we
definitely
have
some
follow-ups
to
rollbacks.
A
We
have
some
coordinate
deployment
pipeline
work
that
we'd
like
to
keep
going
on,
and
then
I
think,
there's
also
kind
of
always
the
little
things
that
we
don't
really
group
under
any
of
these
things
so
much
which
are
like
general
improvements
to
pipelines.
So
I
know
we
have
several
issues
which
are
just
open
which,
if
we
just
reordered
jobs,
a
bit,
things
would
go
faster
and
I
think
all
of
those
things
track
against
mttp.
A
So
just
in
the
interest
of
not
trying
to
bring
in
too
much
additional
work
but
to
wrap
up
things,
we
already
have
in
progress.
What
do
people
think
to
us
just
having
a
kubernetes,
okr
and
then
everything
else?
We
will
prioritize
against
mttp
and
basically
pull
in
work
that
we
think
makes
the
most
sense
based
on
how
mttp
is
getting
on
each
like
week
or
few.
B
Weeks,
yeah,
I
think,
from
my
perspective,
there's
enough
of
things
to
do
for
communities
to
choose
from.
I
think
we
should
just
focus
this
on
on
certain
aspects,
maybe
because,
as
we
can
just
end
up
in
fixing
and
tuning
anything
and
everything
there,
I
mean
there
are
possible
things
like
looking
to
cost
savings
and
and
performance
optimizations
when
needed.
B
Maybe
that
would
be
one
topic
and
the
other
one
would
be
looking
into
how
to
make
it
easy
and
safe
to
operate
changes
in
kubernetes
right,
because
this
is
the
other
thing
I
think
it
will
just
be
be
more
working
on
like
if
he's
done
with
most
of
the
migrations,
I
think
most
of
the
communities
work
will
shift
over
to
doing
something
with
that
like
playing
changes
and
configuration
smaller
changes
and
and
how
we
at
certain
services,
maybe
and
things
like
that,
and
also
including
other
people
and
two
using
kubernetes,
so
our
tooling
chain
and
our
way
to
work
with
that,
should
be
as
easy
as
possible
to
include
other
people
to
be
able
to
do
changes
in
a
safe
way.
B
I
think
there
were
a
lot
of
ideas
from
dream.
Already
instructions,
so
these
two
topics
like
tuning,
optimizing,
cost
savings
and
the
other
topic
operation
of
communities,
I
think,
are
things
which
are
coming
to
my
mind
for
this.
C
I
have
a
question
amy,
so
I
I
like
the
the
the
approach
you
are
giving
to
this.
But
how
will
this?
How
will
this
reflect
with
the
straight
the
strategy
that
we
have
on
our
team
page
in
the
end
book,
because
we
have
goals
for
the
end
of
q2,
which
are
obviously
not
going
to
be
met
and
then
there's
other
goals
by
yeah
for
the
rest
of
the
year?
So.
A
Yeah,
that's
a
really
great
point,
so
let
me
quick,
I
don't
think
we're
too
far
off.
C
And
then
we
have
another
two
extra
for
q4,
which
is
I'm
just
going
to
continue.
Reading
sir
for
everyone's
second
q4
is
defined.
Planet
executed
on
migration
of
stateful
services
to
kubernetes
platform,
and
there
is
the
dog
footing
effort.
I
think
yeah
convert
at
least
four
release
workloads
to
github
fishers.
A
Yeah,
that's
a
good
point,
so
I
think
the
only
one.
That's
probably
a
maybe
a
question
mark
on
timing.
I
guess
is
around
the
rollbacks.
A
C
Stage
well,
predictable
and
reliable.
I
mean
I
don't
think
we
are
really
that
far
off.
Is
that
there's
nothing
written
down
about
automated
or
things
like
that,
so
we
already
have
this
in
place.
So
if
we
tweak
the
wording-
and
we
just
polish
a
bit
and
we
get
more
training
and
things
like
that-
I
think
this
could
be
done
and
kind
of
the
same.
I
mean
slo.
C
The
quarter
is
not
yet
concluded
fine,
but
it
really
depends
on
what
doesn't
mean
to
define
right
so
just
say:
well,
we
define
then
we're
still
working
on
it
or
if
it
is
look,
this
is
a
complete
dashboard,
showing
you
everything
from
event
x
to
event
z.
So
that's
another
story
right,
so
it
really
depends
on
the
level
of
accomplishment
and
those
things.
A
Yeah
definitely
so
I
think
in
terms
of
deployment
slo,
I
think
that
one
is
defined.
A
I
I
would
consider
that
what
we
have
in
the
strategy
is
when
we
meet
the
the
things
outlined
in
that
in
our
okay,
our
q2
okr.
A
So
we
may
not
achieve
them
all
this
quarter
we
might,
but
we
might
not-
and
I
think
we
should
finish
the
work
like
regardless,
if
it's
in
q2
or
q3
to
make
sure
we
we
do
have
this,
because
I
think
this
is
the
kind
of
minimum
of
defining
what
an
s
deployment
slo
is
and
making
it
visible
and
sharing
it
with
other
people
in
terms
of
how
in-depth
the
dashboards
are.
I
do
think
there
are
future
iterations
that
we
can
build
it
out
and
put
in
kind
of
there's
lots
of
extra
stuff.
A
We
know
we
want
which
I'm
really
not
expecting
in
iteration,
one
like
we
should
just
get
the
overall
number
and
graph
visible
so
that
other
people
can
follow.
A
I
think
probably
the
yeah.
We
need
to
make
a
plan
for
rollbacks,
because
there's
definitely
some
training
that
we
need
to
do
myron,
and
I
are
hoping
to
do
a
rollback
this
week.
We
just
need
to
organize
it
and
then
hopefully
not
be
doing
lots
of
patches
and
security
releases,
and
things
like
that
so
fingers
crossed
we
will
get
one,
and
then
that
fits
in
with
our
kind
of
original
plan
of
every
set
of
release
managers
will
do
a
production
roll
back.
A
So
we
know
that's
working
and
we'll
do
a
staging
robot
before
we
attempt
to
do
it
on
production.
Just
so
we
know
everything's
working
and
make
sure
we
know
the
process,
so
this
month
at
least
we'll
get
those
but
yeah.
We
should
work
out
what
we,
what
the
gap
is
between
that
and
what
we
have
written
in
our
strategy,
which
is
intentionally
kind
of
openly
worded
and
work
out.
What
that
looks
like
and
then
we
can
fit
that
together.
A
And
also,
I
suppose,
the
other
thing
is
it's
not
to
say:
if
something
isn't
an
okr,
it's
not
to
say
we
shouldn't
do
it,
so
we
could
absolutely
spend
a
decent
amount
of
our
quarter
working
on
rollbacks.
If
we
think
that's
the
most
valuable
thing,
it's
really
just
about
a.
How
much
do
we
want
to
kind
of
create
the
visibility
and
like
be
reporting
to
other
people
and
then
using
it
to
prioritize
our
own
things
as
well.
A
Yeah
it's
great
questions
and
I
think
the
only
reason
I'm
thinking
that
we
don't
necessarily
want
to
go
into
q3,
saying
that
that
rollback
strategy
line
is
the
okr
is
just
simply
because
I
do
think
there's
probably
benefit
of
us
actually
wrapping
up
things
like
coordinate
deployment,
pipelines
and
deployment
slo
as
well,
and
how
we
prioritize
those
against
each
other.
If
one's
an
okr
and
the
other
two
aren't
it's
a
little
bit
more.
A
Difficult
cool:
well,
thank
you
for
the
questions
and
comments.
I
will
open
up
an
issue
so
that
we
can
start
gathering
ideas
here
and
everyone
else
can
have
input
as
well,
but
one
of
the
big
things
we'll
try
and
do
across
the
whole
department
is
just
limit
the
number
of
okrs
a
little
bit
as
well.
The
last
couple
of
quarters
we've
had
a
lot
of
okrs
and
it's
it's
not
really
helping
us.
A
Awesome
is
there
anything
else
that
anyone
would
like
to.