►
From YouTube: 2021-01-04 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
Cool
okay:
let's
get
started,
hey
everyone,
so
I'm
not
gonna,
go
through
the
announcements,
so
much
just
pretty
much
stuff
to
read.
There's
quite
a
lot
been
shared
over
the
last
week
or
so,
but
a
few
things
to
read.
Thank
you,
robert!
I'm,
completely
useless
without
slack,
so
yeah
enjoy
lots
of
slack
links.
If
there's
anything
that
well
with
the
engagement
survey,
stuff
there'll
be
more
stuff
coming
out
over
the
next
few
weeks.
A
So
that's
the
full
engineering
department
view
there
will
be
an
infrastructure
review
and
we'll
also
chat
about
it
at
a
delivery
team
level
as
well.
So
that
will
come
in
the
next
few
weeks
and
then
marin's
been
busy.
Writing
us
some
things
so
have
a
read
through
those.
If
there's
anything
missing,
please
add
it
in
if
you've
got
any
more
links
and
things
then
do
that
as
well
cool.
So
we
enter
the
last
month
of
this
quarter.
So
that
means
we
get
to
start
thinking
about
okrs
for
this
week.
A
The
main
request
is,
if
you
haven't
already,
please
put
some
thoughts
down
in
the
retro
issue
so
that
we
can
improve
on
the
process
for
the
next
round
of
things.
A
I
think
it
will
be
a
little
bit
different
anyway,
just
because
we're
not
completely
changing
direction,
so
the
last
quarter
was
kind
of
like
several
fresh
okrs
to
start
from,
but
still
it's
really
good
to
just
have
a
think
about
what
worked
and
what
didn't
work
so
that
we
can
improve
on
that
stuff
and
roughly
what
I'm
thinking
kind
of
the
process
will
look
like
is
is
out
for
most
of
this
week,
so
we
won't
make
any
actual
decisions
until
he's
back
and
had
time
to
contribute
as
well.
A
There's
also
some
stuff
going
on
about
strategy.
So
there's
a
little
bit
in
there
already,
which
I've
linked
there'll
be
some
more
stuff
coming
into
the
handbook
as
well.
But
we
want
to
make
sure
our
team
is
fully
aligned
to
like
the
department
strategy
and
then
up
through
the
company,
so
that
will
be
the
kind
of
extra
piece
that
we'll
have
to
think
about
as
well
alongside
okl's.
A
But
for
now
I
think
just
have
a
think
about
things
like
as
much
as
possible.
It's
helpful
not
to
have
to
start
from
zero.
So
if
you
have
ideas
you
wanna
put
together,
then
we
can
then
sort
of
work
out
how
they
fit
together
from
next
week
and
the
week
after
any
questions
on
okrs.
A
Cool,
so
one
thing
I
wanted
to
think
about
as
we
go
into
this
new
year,
is
this
meeting
so
I
was
wondering
this
can
also
be
async
if
that's
easier,
but
I'm
curious
to
hear
people's
thoughts
on
like
what
do
you
want
to
get
from
this
meeting,
and
how
can
we
make
sure
that
happens.
A
Yeah,
okay,
I'll
open
up
a
thing,
so
we
can
actually
think
about
that
so
like,
for
example,
from
my
side,
one
of
the
things
which
I
think
I've
mentioned
to
all
of
you
separately,
but
is
around
as
we
go
through
this
year.
A
The
sort
of
threads
of
our
work
start
to
come
together
a
lot
more
as
we
progress
further
into
the
kubernetes
migration,
it
will
be
the
sort
of
integral
for
all
of
our
deployment
work,
so
it'll
be
much
more
key
that
we
kind
of
have
a
good
understanding
of
what
each
other
are
working
on,
and
we,
you
know,
work
together
on
sort
of
fewer
goals
with
more
of
us
working
on
those
things.
A
So
I'd
like
this
meeting
to
be
able
to
actually
help
us,
like
you
know,
do
that
and
coordinate
and
kind
of
practice
working
out
like.
What's
the
smallest
situation,
we
can
get
to
and
like
how
do
we
collaborate
on
those
small
iterations
and
things
like
that?
But
you
know
obviously
keen
that
this
meeting
also
serves
purposes
that
you
all
have
as
well,
so
I'll
open
up
an
issue.
So
we
can
talk
about
that
stuff,
but
do
have
a
think
about
like
that.
A
Like
it's
everything's
up
for
grabs
like
this
meeting
could
be
a
different
cadence.
It
could
be
a
different
length.
It
could
be
a
different
format,
so
yeah,
let's,
let's
see
what
we
can
make
it
really.
B
A
Yeah
absolutely-
and
that's
really,
I
think,
where
the
question
of
like
what
do
we
want
this
meeting
to
cover,
but
yeah
absolutely
like.
If
we've
got
10
things
we'd
like
to
cover,
we
should
schedule
it
so
that
we
have
time
for
10
things
so
yeah
great
point
cool,
so
jeff.
If
to
you.
B
Sure
I
just
wanted
to
socialize
the
fact
that
we're
gonna
be
pausing
deployments
previously
was
planned
for
next
week,
though
we
did
the
helm3
upgrade
in
staging
for
live
home
files
today
and
it
went
smoothly.
I
think
we
could
probably
start
prod,
but
I
don't
want
to
start
to
like
any
auto
deploy
interruptions
until
the
security
release
is
complete.
So
can
anyone
answer
this
question
it's
like:
when
do
we
think
the
security
release
will
be
done.
C
So
it
should
be
done
this
thursday
and
well.
I
think
this
can
be
done
after.
B
Yeah,
that
sounds
good.
So
so
maybe
tentatively
we
could
say
like
we
try
to
do
staging
on
friday
and
I'm
actually
even
thinking
about
doing
production
on
sunday
or
something
and
just
shifting
my
schedule
a
bit
so
that
we
don't
pause
deployments
on
monday,
but
we'll
see
how
that
goes.
How.
B
I
think
it's
going
to
be
no
more,
in
fact
it
may
be
less,
but
I
think
it's
going
to
be
no
more
than
two
hours,
maybe
even
only
one
hour.
The
gitlab
release
is
actually
much
simpler
than
the
helm
files
release,
which
is
what
we
did
today
and
that
took
about
four
hours.
But
I
think,
like
the
staging
I
mean
staging
end
prod
for
for
git
lab
is
gonna,
be
much
faster.
C
I
mean
if
that
is
the
case.
I
think
it
can
be
done
before
thursday
if
it
is
only
two
hours.
I
don't
have
a
problem
by
doing
it
yeah.
What
are
you
thinking.
B
So
I'm
trying
to
manage
risk
here.
The
problem
is,
is
that
if
something
goes
wrong,
we
kind
of
have
to
fix
it
before
we
can
do
a
deploy.
There's
no
easy
rollback.
B
Once
the
wheels
are
set
in
motion
for
the
upgrade,
because
helm
keeps
state
and
there's
like
a
migrate,
you
have
to
migrate
the
state
from
the
helm,
2
side
to
the
home
3
side,
and
then
you
can't
deploy
on
helm
2
until
you
completely
move
over
so
to
manage
risk,
and
given
that,
like
it,
isn't
super
urgent
like
there's,
no
nothing.
This
is
blocking
right
now,
so
I
would
say,
like
might
as
well
wait.
B
A
So
how
about
on
friday,
then
we
put
out
a
deployment
like
morning
deployment
and
then
we
can
pause,
because
actually
we
have
quite
a
big
gap
between
our
first
and
second
deployments
of
the
day
and
if
the
second
one
was
delayed,
then
you
know
we've.
It's
still
quite
like
reason.
It's
still
in
your
morning,
right
right
like
so,
I
think
we've
got
quite
a
long
window
in
the
middle
okay.
We
could
use.
A
And
on
the
sunday,
like
completely
fine
again
for
us
to
do
that
on
monday,
and
just
you
know,
delay
the
second
deployment
of
the
day
like
the
afternoon
one
if
it's
safer,
to
do
this
on
on
a
monday,
when
we
have
everybody
around.
B
Yeah
yeah,
I
think
what
we'll
do
is:
let's,
let's
make
the
call
after
we
do
staging
on
friday.
If
we
do
it
because
we'll
know
like
okay,
maybe
it
only
took
20
minutes
and
you
know
then
won't
be
any
problem,
but
yeah
yeah.
Well,
I
guess
we'll
see
we'll
see
how
it
goes.
C
Yep
thanks
so
gitlab,
shell
already
changed
their
the
fall
branch
to
from
masters
to
the
main,
and
they
are
handling
two
branches
at
the
same
time,
so
I
think
manually,
a
maintainer
when
someone
pushes
to
main
the
maintainer
also
pushes
to
master,
and
I
just
want
to
know
since
we
don't
really
handle
patches
nor
security
releases
for
gitlab
shell.
C
D
So
I
think
he's
from
the
top
of
my
head.
I'd
have
to
look.
It
is
completely
detached.
As
in
when
we
package,
omnibus
and
helm,
we
do
read
the
gitlab
shell
version
file
from
the
gitlab
repository.
D
But
as
far
as
I
know,
we
don't
have
any
code
that
actually
updates
that
I
think
that's
a
manual
process
even
and
I
think
part
of
it
because
gitlab
shell
releases,
like
you
know,
once
a
decade
or
so,
but
I'm
not
sure
if
there's
any
sort
of
hidden
code
in
release
tools
where
we
do
something
with
gitlab
shell
and
we
expect
the
master
branch
to
exist.
B
I
don't
think
so
either
and
I
don't
think
omnibus
has
any
special
logic.
I
mean
they're,
just
basically
looking
for
a
ref
for
the
shell
version
in
the
gitlab
rails,
codebase.
C
So
if
they
were
to
delete
the
master
branch
today,
we
wouldn't
need
to
do
anything
else
from
our
side
in
the
release
tools.
C
Okay
well,
either
way,
I'm
going
to
open.
B
D
I
did
a
quick
check,
at
least
for
helm.
We
read
everything
from
the
eu
repository.
I
think
omnibus
is
the
same.
So
I
think
removing
master
should
be
fine
for
release
tools,
but.
A
Could
we
get
them
to
so
they're
pushing
to
both
main
and
master
right
now?
Could
we
get
them
to
just
push
one
thing
to
main
and
do
the
test
and
check
we
pick
it
up.
A
Nice
cool
so
yeah,
so
that
I
wanted
to
sort
of
make
sure
everyone
was
aware
of
kind
of
some
things
going
on
so
obviously
help
three
upgrade
is
going
on
and
renaming
master
is
also
going
on
on
that
one.
We
are
pushing
on
as
much
as
we
can
to
do
the
deployment
tooling
changes
so
that
we
don't
need
to
worry
about
what
things
are
called.
So
if
you
can
help
on
any
of
that
work,
either
picking
up
the
issues
that
myra's
got
or
reviewing
or
things
like
that,
then
please
do
help.
C
And
nope,
so
we
have
some
issues
that
I
am
linked:
the
epic
in
some
moments,
but
basically
we
just
need
to
rename
or
to
remove
the
hard
coded
master
reference
from
our
tooling
and
to
use
now
the
project
default
branch.
And
after
that
we
should
do
a
test
to
ensure
that
our
patches,
our
security
releases
and
monthly
releases
and
deployments,
are
still
working
like
some
sort
of
dry
run
and
that's
it
but
yeah.
Just
let
me
let
me
link
the
epic.
A
Cool
and
robert,
do
you
want
to
mention
coordinated
pipeline.
E
Yeah,
just
picking
up
that
work
again,
the
next
part
is
waiting
for
the
omnibus
tag
to
be
available
from
what
I
remember,
I
was
just
fighting
with
ci
yeah,
well
configuration
so
I'll
pick
that
back
up.
A
Cool
and
to
go
back
is
anything
on
the
dr
side
that
we
need
to
work
out
this
week.
D
A
Cool
okay,
even
on
like
the
planning
side,
it's
really
if
anyone
need
any
help
or
not
just
to
actually
scrub
it.
Does
anyone
need
any
help
on
finding
solutions
to
problems
that
will
be
coming
up
in
the
next
week
or
two.
A
Cool
okay,
great,
okay,
cool!
So
are
there
any
other
discussion
points.