►
From YouTube: 2020-10-26 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
It
gets
better
yeah,
so
the
eu
has
voted
that
spring
next
year
is
the
last
one
which
makes
sense
well.
That
means
in
the
uk
we'll
see
because
obviously
brexit
we'll
make
our
own
decisions
so
yeah.
It
gets
more
complicated.
A
Whatever
it
was
in
the
1970s
we'll
have
that
one,
that's
basically
our
default
here
awesome
so
so
find
the
agenda.
A
Cool
so
main
things
starting
off
so
scale
back
out
this
week,
alessio's
off
sick
today,
hopefully
hopefully
he'll
be
back
with
us
soon.
Euric
is
out
friday
and
marion
you're
off
so
out
for
some
days
as
well
from
wednesday's
your
first
day
out
awesome.
So
first
the
second
item
I've
got.
The
announcement
was
just
to
re-share
the
vpn
message
that
was
in
slack
last
week
with
the
handbook
stuff.
So
it
might
be
useful
for
people
to
know
about
that
stuff,
particularly
the
endpoint
management.
A
Things
start
coming
in,
like
they
that's
rolling
out
slowly
via
email.
As
far
as
I
understand
so,
if
you
get
the
email
that
says
install
it,
then
please
follow
the
instructions
awesome
so
on
to
discussion
points.
So
what's
the
plan
for
our
security
release.
C
I
think
we
should
start
it.
It
doesn't
look
like
there's
anything
critical
outstanding
for
patch,
but
yeah.
I
think
it
makes
sense
to
start
what
do
you
think
robert.
C
A
Okay,
cool,
so
we're
gonna
do
some
like
start
the
merge
window
like
latest
day
and
then
release
whatever.
A
A
This
will
also
be
the
final
piece
of
around
the
api
release.
Changes
as
well
like
this
is
the
final
type
of
release
that
we
haven't
yet
been
through.
So
also
just
be
aware
of
that
awesome
so
on
to
the
next
point,
so
q4
okrs,
so
I
am
in
the
middle
of
making
some
edits,
but
I
wanted
to
give
you
some
more
context
on
this
stuff,
so,
thanks
to
everyone,
who's
input
so
far,
myra.
A
Hopefully
the
issue
is
in
a
state,
that's
reasonably
okay
to
catch
up
on,
and
if
there's
things
that
you
feel
you
know
you
would
have
contributed
if
you'd
have
been
around
last
few
weeks.
Just
shout
right.
These
are
not
set
in
stone.
We
can
edit
these
for
the
next
few
weeks,
so
feel
free
to
to
throw
in
your
ideas
as
well
and
what
I've
started
doing
is
we
have
our
discussion
issue
where
we've
been
contributing.
A
What
I've
tried
to
do
is
wrap
those
ideas
up
into
what
will
become
our
kind
of
official
three
okr
issues,
they're
all
still
in
draft
mode,
but
at
least
it
gives
us
a
place
where
we
can
start
expanding
out
on
the
individual
topics.
So
we'll
have
three
okrs
for
delivery.
Next
quarter,
one
is
going
to
be
around
continuing
with
the
kubernetes
migration
so
reasonably
straightforward.
A
What
we
need
to
just
I
need
to
add
a
bit
of
an
update.
Just
explaining
around
like
the
web
stuff
will
be
a
stretch
goal.
We
know
that
because
the
pages
work
that's
still
going
on
and
the
other
bit
which
I've
left
as
a
kind
of
question
mark
is
around
where
exactly
we'll
finish
on
q3
and
where
we'll
start
in
q4.
So
we
have
both
the
get
ssh
and
the
get
https
stuff
reasonably
near
the
end.
A
Hopefully
maybe
we'll
get
one
of
those
done
and
whatever's
left
over
will
roll
into
q4.
So
it's
a
few
tweaks
coming
that
way,
but
I
don't
think
there's
any
sort
of
radical
changes
on
that
one
unless
she
does
a
great
job.
C
C
Done
and
you
know
next
is
the
get
ssh
stuff.
So
so
that's
good.
A
Awesome
and
I
had
a
dave's
going
to
work
on
unblocking
us
on
that
one
as
well,
so
we
should
have
an
update,
hopefully
on
that
one
soon
about
where
the
extra
work
will
come
in
so
awesome,
that's
really
great
stuff,
then
the
second
okr,
which
again
is
reasonably
straightforward,
I
think,
is
around
the
moving
our
changelog
stuff
into
something
that
sits
inside
gitlab.
So
under
the
banner
of
dog
fooding
we'll
build
the
thing
that
will
dog
food
so
that
we
kind
of
get
best
of
both
worlds.
A
So
this
kind
of,
I
suppose
from
our
side.
What
we
need
to
do
is
work
out
what
we,
what
we
need,
make
it
generic
enough
so
that
it
can
go
inside
the
product
and
then
we
can
test
it
out
iron
out
any
of
the
edge
cases
and
then
hopefully
roll
it
out
to
everything.
So
this
one
hopefully
has
a
reasonably
straightforward
scope.
There
was
already
quite
a
lot
of
work
done
on
this
about
seven
months
ago,
within
the
releases
team,
so
there's
already
actually
an
approach.
A
Whole
epic
and
issues
have
already
been
specced
out,
so
that'll
be
a
good
starting
point
for
us
to
actually
review
those
and
see
would
if
we
did,
that,
would
that
meet
our
requirements
or
not,
and
if
not
fine,
we'll
make
something
generic,
but
it
certainly
had
some
interesting
ideas
using
labels
on
mrs
as
a
kind
of
jumping
off
point
into
how
do
you
bring
things
into
the
changelog?
A
So
I
think
it'll
be
interesting
to
think
about
with
our
requirements
and
then
the
third
one
is
the
one
which
I
am
still
doing
about
loaded
editing
on.
So
what
I'm
trying
to
do
for
this
one
is
write
up,
something
that
is
going
to
be
around
coordinating:
multi
pipelines.
It
builds
or
we've
got
four
epics
around
kind
of
the
complexity
of
running
pipelines
and
we've
got
various
things.
There.
We've
got
things
about
like
the
order
in
which
the
pipelines
run.
We've
got
so
like
initiating
with
the
tagging
of
omnibus.
A
We've
got
things
in
there
about
the
fact
that
we
have
lots
of
satellite
projects
which
at
the
moment,
are
kind
of
quite
tied
in.
We
don't
have
a
way
of
having
those
isolated
and
also
the
fact
that
release
toys
and
deploy
are
like
really
sort
of
interlinked
with
each
other.
So
we
kind
of
have
this
one
thing
that
tries
to
do
all
the
kind
of
preparing
and
building
and
deploying,
and
then,
alongside
that,
we
also
have
at
the
moment
we
don't
have
a
great
ability
to
test
releases.
A
So
there
is
a
proposal
up
there
around
shadow
releases
and
that
starbuck's
also
got
a
sort
of
similar
issue
around
one
of
the
pieces.
I
can't
remember
it
was
a
slightly
smaller
but
similar
vein
around
a
check
mode.
So
what
we're
trying
to
do
is
bring
in
some
of
that
as
well
and
actually
to
take
the
first
cut
at
moving
things
into
release
tools
so
that
we
trigger
from
there,
but
also
separating
out
the
preparation
and
building
from
actual
deployments.
A
So
I
make
another
edit
on
that
today,
but
again
completely
draft.
So
I
wanted
to
give
a
bit
of
context
around
what
I've
tried
to
do,
which
is
take.
These
four
big
epics,
which
are
very
each
of
them,
are
very,
I
suppose,
quite
broad
in
their
own
right,
but
quite
deep,
try
and
combine
them
and
give
us
a
sort
of
thinner,
horizontal
slice
that
might
fit
still
fit
within
a
quarter.
A
So
definitely
expecting
there'll,
be
lots
of
detail.
We
have
to
work
out.
There'll,
certainly
be
some
things
that
I've
got
wrong,
so
please
do
step
in
and
point
those
out
and
suggest
better
ways
of
wording
things,
but
I'm
trying
to
make
it
generic
enough.
Not
you
know
high
level
enough
that
it
fits
for
an
okr
issue
that
we
can
then
dive
into
like
specifics
of
implementation
details,
we
can
do
that
somewhere
within
the
team.
A
Awesome
so
feel
free
to
like
comment
on
those
issues,
as
I
say,
the
individual
okay,
our
issues
plus
our
discussion.
One
anywhere's
fine
share
your
thoughts
or
in
slack
as
well,
we'll
bring
all
these
together
in
the
next
day
or
two
to
get
the
kind
of
official
okrs
and
then
over
the
next
couple
of
weeks,
we'll
start
really
sort
of
working
out
like
what
are
the
first
steps.
What
do
those
issues
look
like
and
how
do
we
take
that
forwards?.
A
Awesome
and
then
the
other
thing
I
was
going
to
mention
around
okrs
was
on
q3
okrs.
So
we
are,
we
are
sitting
well
currently,
our
kubernetes
one
is
at
50.
We
could
just
recalculate
that
now
with
jeff's
announcement.
So
that's
super
awesome
and
then
our
manual
deployment
steps
one
we
have
the
bit.
We
will
definitely
not
get
to
is
halting
deployments
and
that's
totally
fine.
A
A
Cool,
so
I've
got
a
little
bit
of
work,
which
I
promised
celestia
I'd
get
to
today,
which
is
about
putting
something
up
so
that
we
can.
We
agree
that
this
is
a
development
tool,
so
finding
a
way
to
actually
pass
sentry
ownership
back
into
development,
and
we
can
move
on
focusing
on
using
using
our
metrics
that
we
have
in
place.
So
it's
a
little
bit
of
tidy
up
to
do
there
and
we
have
one
final
task,
which
I
hope
we
can
hit.
A
This
quarter
find
it
which
ties
in
with
this.
It
is.
A
And
there
is
just
one
final
piece
that
goes
with
the
notifying
release
managers.
So
now
we
check
as
we
go
through
a
deployment.
There
are
checks
as
we
go
through
about
how
the
fleet
health
is
there's
just
one
final
piece,
which
is
around
notifying
release
managers
if
things
become
unhealthy,
reusing
the
canary
bake
time
setup.
So
if
somebody
would
like
to
pick
that
up
myra,
I'm
not
sure
how
quickly
it'll
take
you
to
sort
of
catch
up
but
like
if
in
the
next
day
or
two
you're
looking
for
a
task.
A
This
would
be
a
great
one
to
grab,
because
this
will
give
us
a
nice
sort
of
shouldn't
be
a
huge
thing,
but
it
will
nicely
wrap
up
that
little
piece
in
notifying
release
managers.
A
Call
is
there
anything
else,
people
wanted
to
ask
or
say
about
ok,
arts.
C
Yeah
just
wondering
what
is
the
latest
on
performance
reviews?
Is
there
anything
that's
going
to
happen
before
the
end
of
this
year
or
is
it
going
to
be
beginning
of
next
year?
Are
we
still
doing
360?
Are
we
just
doing
performance
reviews
with
our
with
you?
I
guess
our
manager.
A
D
Are
no
right
legs
at
the
moment,
mostly
because
there
is
a
lot
of
things
happening
right
now,
so
I
can
share
a
couple
of
very
confusing
things
just
to
make
you
confused
so
number
one
is
as
a
company.
We
have
a
completely
new
process,
so
it
is
not
a
360
review.
It's
a
performance
review.
It's
an
iteration
on
the
nine
box
performance
reviews.
D
D
However,
because
this
came
in
so
late,
when
I
say
so
late
I
mean
it
is
still
being
developed.
Engineering
is
opting
out
of
the
whole
process,
so
we
are
going
to
do
something
in
between
the
nine
box
and
the
old
compa
groups.
There
is
a
template
in
there.
D
I
can
find
that
merge
request
at
least
I'll
try
to
find
and
share
it
here,
but
to
make
things
even
more
confusing
infrastructure,
on
the
other
hand,
is
going
to
most
likely
follow
the
company
level
approach,
mostly
because
we
are
so
small
that
we
want
to
probably
provide
feedback
with
an
exception
that
we
will
not
follow
the
whole
process,
but
we'll
take
parts
of
engineering
process
as
well,
just
because
people
ops
is
not
fully
ready
with
the
tools,
so
we'll
probably
take
templates
from
engineering
but
follow
the
general
process
as
they
laid
it
out.
C
D
C
A
Things
will
happen
this
year.
As
far
as
I
understand
it,
there
is
a
there
is
no
c
360.
I
don't
believe
I
didn't
see
anything.
That
said
there
would
be,
but
there
is
a
personal
review
and
there
is
like
a
manager
aspect
which
is
kicking
off
in
the
next
few
weeks,
so
the
personal
bit
is
in
early
december.
I
think.
D
No,
it's
it's
it's
starting
now,
in
november,
like
mid
to
late
november
throughout
december,
so
I
was.
I
was
trying
to
be
also
a
bit
funny,
which
is
not
really
helpful,
mostly
because
it
is
confusing,
and
I
wanted
to
like
frame
it
as
it
is
right
like
it
is
still
being
worked
out
as
we
go
along
so
the
only
last
week.
This
merge
request
came
in
from
eric
to
set
the
direction
on
on
info.
Sorry
on
the
whole
engineering
department,
but
the
general
idea.
D
It
is
more
going
to
resemble
the
compa
groups
thing
that
we
did
last
year
in
the
fact
that
you're
going
to
be
discussing
things
with
your
manager
and
the
templates
are
going
to
be
different
and
the
expectations
are
going
to
be
a
tiny
bit
different.
But
it's
going
to
resemble
quite
a
lot.
Compa
group
review,
rather
than
360
performance,
sorry
360
review
that
we
had
at
the
beginning
of
the
year.
If
you
remember
the
peer
review.
C
Yeah,
I
just
remember-
and
we
also
had
like
a
lot
of
feedback
on
that.
I
was
curious
if
any
of
that
feedback
was
taken
and
they
intend
to
improve
it,
but
it
sounds
like
the
improvement
is,
maybe
we're
just
not
gonna.
Do
it
pretty
much
okay
and
this
performance
review?
Does
it
tie
into
raises
or
salary
adjustments
at
all,
or
is
it
completely.
D
Does
it
it
completely
ties
into
the
raises,
so
there
is
no
more
how
what
was
the?
What
was
that
called
like
the
end
of
the
year
increase.
D
D
Thing
like
the
cost
of
living
that
one,
so
we
are
no
longer
doing
that
we
are
doing
increases
based
on
performance,
so.
C
D
Review
that
is
going
to
be
happening
now
is
the
one
that
is
going
to
be
affecting
compensation
in
starting
from
february.
Did
you
know
how?
How
did
I
want
to
put
it
not
with
the
start
date
of
february,
but
your
compensation
from
february
1st
will
be
adjusted
based
on
the
outcome
of
this
performance
review,
okay,
cool,
so
I
shared
the
merge
request.
D
You
can
see
the
diff
there
on
what
is
actually
happening
differently
in
engineering,
and
you
have
all
the
links
for
how
people
group
is
looking
into
into
things,
and
we
are
going
through
training
sessions
right
now
with
people
group
to
help
us
with
clearing
things
up.
I'm
sorry.
D
D
A
Yeah
awesome
and
so
yeah
you've
all
got
like
objectives
in
your
one-to-one
docs.
So
now
would
be
a
great
time
to
start
thinking
having
a
think
about
those,
and
you
know
think
about
how
much
progress
you've
made
against
them,
but
also
where
do
we
go
next,
like
what's
the
other
stuff
that
you'd
like
to
be
thinking
about?
Because
this
all
ties
into
kind
of
the
next
round
of
those
things
as
well.
A
Awesome
thanks
for
bringing
that
up
job,
that's
yeah
I'll!
Keep
you
updated
on
changes
of
that
one
as
we
keep
going
because,
like
it,
it
will
be
there'll,
be
more
information
coming
in
the
next
days
and
weeks
for
sure
awesome
is
there
anything
else?
Is
there
anything
else
anyone
wants
to
bring
up.