►
From YouTube: 2022-10-04 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
Okay,
so
we're
at
times
so
I'll
kick
things
off.
Welcome
to
3rd
of
October.
We've
got
a
few
announcements
on
the
agenda,
which
I'll,
let
you
all
read.
Most
importantly,
is
family
and
friends
day
it's
on
Friday.
So
if
you
wish
to
take
that,
then
please
go
ahead.
Stick
that
in
Roots,
so
people
know
and
on
the
discussion
item,
so
I
wanted
to
just
share
a
little
bit
around
the
upcoming
performance
reviews
or
Talent
assessments
have
been
called
this
time
round.
A
A
So
the
this
time
sort
of
major
changes
are
the
entire
process
is
going
to
take
place
inside
work
day
and
there's
a
new
additional
optional,
self-assessment
step
has
been
added
in
so
I
definitely
won't
make
to
sort
of
really
emphasize
that
is
optional,
but
at
the
same
time
it
is
intended
to
kind
of
give
you
some
time
to
self-reflect
and
also
to
make
sure
that
McKelly
and
I
are
both
aware
of
kind
of
what
you
would
consider
your
highlights.
A
So
if
you
do
decide
not
to
take
part
which
is
totally
fine,
I
do
recommend
that
you
also
consider
just
putting
a
few
bullet
points
into
your
one-to-one
agenda.
A
A
I
have
just
popped
in
the
timeline
here
from
which
is
from
the
handbook,
so
you
can
see
it
there.
It
may
update.
Probably
the
main
things
to
be
aware
of
here
is
this
very
long
timeline.
A
So,
although
things
are
kicking
off
today,
actually
is
the
first
day
of
the
timeline,
the
actual
sitting
down
and
going
through
reviews
together,
which
will
you'll
be
yourself
and
your
manager
will
actually
happen
most
likely
in
January,
so
that
kicks
off
that's
0.8,
so
that
will
be
somewhere
between
the
19th
of
December
and
the
end
of
January.
Anyone
who
reports
to
me
it's
in
January
right
because
there's
no
way
we're
squeezing
that
in
between
the
19th
and
the
end
of
the
year,
so
just
to
be
aware
of
that
right.
A
So,
though
things
do
kick
off,
there
will
be
some
periods
where
it
will
be
very
quiet,
but
it
is
all
going
on.
I
also
want
to
just
add
in
there
as
well
about
the
fact
that
this
tie
rod
is
being
called
Talent
assessment.
It's
not
an
assessment
of
your
talent
because
we
know
you're
all
super
talented.
A
It's
an
assessment
of
how
things
have
gone
this
year,
how
you
know
what
sort
of
things
you've
managed
to
achieve
and
what
growth
you've
seen
right
and
then
setting
you
up
for
growths
and
goals
and
things
for
next
year.
Right
like
it's,
not
a
judgment
of,
are
you
talented
or
not?
A
Hopefully
it
means
it's
sick
and
we
don't
have
to
fill
in
so
many
spreadsheets
and
docs
and
other
things
which
sort
of
goes
on
around
the
the
you
or
the
previous
processors
so
awesome
and
if
you
do
have
anything,
if
you
think
of
anything
or
it's
anything,
you
want
to
ask
you
don't
want
to
share
on
this
recording
or
in
this
call,
obviously
use
your
one-to-ones
or
give
the
DM
right.
A
So
we
can
clear
those
things
up
cool
so
on
B
I
opened
an
issue
a
couple
of
weeks
ago
around
the
soft
PCL
that
we
have
in
place
on
the
22nd.
A
The
intention
behind
the
PCL
is
to
limit
kind
of
unneeded
changes
around
the
release,
but
at
the
same
time
we
don't
want
to
prevent
ourselves
from
deploying,
because
if
we
do
need
to
get
a
patch
fixed
out,
we
want
to
be
in
a
good
place
to
do
that.
There's
no
confusion
around
what
we
can
in
card
or
what
we
should
or
shouldn't
do
on
the
22nd
so
open
an
issue
to
try
and
clear
that
up
now
a
couple
of
suggestions
have
come
up.
A
Steve's
suggestion
was
simply
like
why
don't
we
just
exclude
deployments
from
soft
pcls
and
Alan
has
got
a
slightly
different
one,
which
is
why
don't
we
reclassify
deployments
as
sort
of
low
severity,
so
they
will
always
be
like
criticality,
three
or
four,
so
they
would
therefore
be
excluded
from
a
soft
PCL.
A
One
of
the
big
changes
I
could
think
of.
If
we
did,
this
was
technically
we'd
still
be
able
to
do
deployments
on
family
and
friends
days
and
over
the
holidays,
which
would
be
bad
if
you
usually
take
those
days
off.
They
just
want
to
add
that
we
would
get
the
control,
but
it
would
be
on
us
to
be
able
to
basically
say
we
choose
not
to
deploy
on
those
days,
which
is
fine.
We
can
certainly
do
that,
but
does
anyone
else
have
any
other
thoughts
or
concerns
like?
Are
there
other
things
I'm?
A
Not
thinking
about
that
would
be
a
risk
if
we
were
to
exclude
deployments
from
basically
from
soft
pcls.
A
Cool
okay,
so
nothing
obvious
what
I'll
do
is
I'll
go
ahead
and
get
an
mrr
created,
which
adds
some
wording
around
something
like
this,
like
we
will
still
have
a
soft
PCL,
because
I
think
one
thing
that
will
be
really
important
is
that
we
don't
run
the
post
deploy
migrations
because
we
will
want
to
roll
back.
If
anything
does
happen,
so
there
will
be
a
slightly
different.
I
will
certainly
still
need
to
be
aware
of
soft
pcls
and
and
manage
those
so
I'll
Stand
Up
on
Mr
and
I'll
drop
it
in
Psych.
A
A
Cool
Reuben
over
to
you.
B
So
I
was
looking
at
products
that
allow
us
to
do
some
kind
of
analysis
on
Pipeline
traces
and
honeycomb
was
one
of
them.
So
I
was
wondering
what
procedure
we
have
to
follow
in
order
to
like
do
a
POC
using
a
free
account
on
honeycomb,
so
their
free
account
gives
you
like
2
million
traces
or
something
which
is
much
more
than
we
need.
B
We
have
like
a
few
hundred
pipelines,
so
it's
more
than
enough
for
us,
but
I
was
wondering
if,
because
it's
deployment
pipeline
traces
do
we
have
to
worry
about
any
compliance
related
stuff,
so
they
are
soc2
compliant,
but
like
does
that
have
to
be
formally
verified
or
something
I
don't
know
so.
I
just
wanted
to
check
if
anyone
else
has
gone
through
this
process.
Before
knows
anything
about
this.
A
No
super
great
question:
I'm
going
to
guess
that
well
in
detail,
Steve
to
review
and
approve
I
guess
couple
of
things
like
I
think
an
issue
like
I
mentioned
like
if
we
get
an
issue
together,
which
basically
explains
what
we
want
to
do.
A
You
know
like
if
there
are
any
costs-
and
you
know
what
compliance
they
have,
then
we
can
figure
out
what
the
process
is.
It
may
be
worth
thinking
about.
If,
if
we
love
I
mean
I
I
know
our
a
trial
is
the
first
thing
but
like
if
we
absolutely
loved
what
we
saw.
What
would
that
look
like
like
what
would
be
the
kind
of
costs
and
and
sort
of
things
that
we'd
need
to
have
in
place
for
that?
A
Or
is
it
just
a
I
guess
a
trial
to
kind
of
see
what
things
could
look
like
versus?
Is
this
a
great
tool
to
try
and
adopt?
So
if
you
could
try
and
get
some
of
those
things
into
the
issue,
then
we
can
ask
Steve
how
to
go
about
like
setting
this
up
like
we've.
Certainly
done
this
a
lot
of
times,
I'm
sure
with
other
tools
in
him.
For
us,
so
we
will
certainly
have
a
way
of
doing
that.
A
A
So
if
you
get
all
that
stuff
in
anyway,
we
can,
we
can
certainly
work
out
what
what
this
looks
like
in
terms
of
like
how
do
we?
How
do
we
go
ahead
and
get
this
done
better.
A
Can
build
this
house?
Oh.
A
A
That's
super
hard
to
measure,
of
course,
and
we
probably
don't
want
to
like
spend
two
years
only
building
this
stuff,
but
just
to
be
aware
that
those
are
the
sort
of
things
that
there
are
documented
to
kind
of
help
us
make
these
decisions.
B
We
did
have
a
chat
with
the
gitlab
observability
group,
so
they
don't
currently
have
any
such
ability
to
analyze
pipeline
traces,
so
we
did
check
with
them.
First,
okay,.
A
A
Yeah
we
can
certainly
get
I
will
be
surprised
if
we
have
trouble
getting
a
trial
approved,
particularly
if
they
already
have
sock
too.
That's
probably
going
to
be
the
big
question,
so
yeah
see
Guyana,
we'll
see
what
we
can
do
about
getting
that
approved.
B
Okay
related
to
that
The
gitlab
Observer
observability
group
told
us
that
they
can
accept
traces
and
give
us
a
view
of
the
traces,
no
analysis
or
anything,
but
just.
C
B
View
could
be
helpful,
so,
let's
see
they'll
provide
us
with
a
URL
and
stuff
and
we
can
start
sending.
B
C
B
So
the
observability
group
is
comprised
almost
entirely
of
a
company
that
they
acquired
called
op
stress,
okay,
yeah,
so
that
product
of
stress
had
logging
tracing
metric
capabilities,
so
that's
being
integrated
into
gitlab.
C
C
Relatively
new
acquisition
of
ours
gotcha
all
right.
Thank
you.
B
B
C
Yeah
I
can
do
that.
Let
me
just
show
my
screen.
C
I
repeated
the
same
mistake
because
last
week
and
do
not
have
everything
open
so
give
me
a
minute.
C
Oh
yeah
cool
so
last
week,
although
I
was
out
on
Friday
for
the
most
part
yeah,
that's
how
the
graph
is
looking
like
from
what
I
remember
I
mean
I
wrote
the
style
this
morning
there
was
this
incident,
so
you
kind
of
see
the
not
promoter
going
up
over
here,
but
I.
Don't
I'm
not
actually
sure
why
this
bump
is
happening.
Oh.
A
I
thought
I
added
an
annotation,
but
I,
don't
know
why
you
can't
see
it.
So
there
was
refreshing
that
one
was
a
oh
there.
C
So
yeah,
that
seems
those
are
the
same
thing
right,
yeah.
So,
okay,
so
that's
that's
the
incident
that
happened
that
blocked
and
then
yeah
another
one
around
this
time,
which
makes
sense
right,
but
then
yeah
other
than
that,
the
rest
of
the
week.
It
seems,
like
you
know,
no
real
blockers
happening
and
we're
able
to
get
it
done,
and
then
yeah
just
got
to
pick
back
pick
it
back
up
this
week
and
then
for
deployment
frequency
yeah.
It
seems
like
last
week,
was
kind
of
back
to
normal.
C
After
what
happened
the
week
before
yeah
I
like
how
there
are
points
there,
but
then
it
just
makes
a
straight
graph,
yeah
kind
of
looks
similar
to
this.
This
kind
of
graph
and
then
lead
time
for
changes.
C
I
think
we're
going
back
to
how
I
kind
of
generally
looks
like
this
week
last
week
was
a
bit
Yeah
abrupt
because.
C
That
too
yeah
we
are
nothing
too
out
of
the
ordinary
from
what
I
can
tell,
and
then
this
is
the
blockers
right,
yeah
yeah!
So
that's
really
peculiar,
because
I
remember
the
week
before
being
very
hectic.
But
that's
not
that
much
different
from
number
of
hours
that
production
deployment
was
booked
for.
A
The
PCL
countries
a
lot
of
that
as
well
though
so
on
on
last
week,
gotcha
so
I
think
overall
last
week
was
probably
less
hectic
like
we
had
five
things
versus
six,
but
one
of
the
five
was
a
PCL,
so
it
probably
contributes
a
little
bit
icic.
C
Yeah
is
pretty
much
it
questions
comments.