►
From YouTube: 2020-08-31 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
C
Indeed,
just
to
reiterate,
while
I
was
or
while
jarv
was
on
vacation,
I
found
it
a
little
troublesome
because
it
was
a
little
difficult
to
get
things
pushed
through.
C
D
Yeah
different
results
pretty.
I
guess
it
was
pretty
painful
when
there's
only
one
of
us
here.
C
D
E
Yeah,
but
if
we
had
the
other
teammates
as
approver
just
in
case
one
of
the
two
is
not
here,
but
then
we
had
no
idea
how
to
review
or
understand
what
we
are
changing.
You
can
just
self-approve.
D
Yeah
yeah,
I
think
that's
that's
reasonable,
and
I
put
a
note
there
that
we
discussed
this.
While
you
were
out
scarback
and
thought
that
maybe
we
could
create
an
issue
template
that
has
a
checklist
of
things
that
people
should
do
to
become
a
maintainer.
B
C
F
D
Yeah,
so
I
was
thinking
whether
we
should
switch
to
the
new
priority
labels.
I
saw
that
all
the
existing
party
labels
were
switched
over
any
opinions
on
that.
F
E
E
B
B
D
C
Why
don't
we
create
an
issue
and
address
it?
Async.
B
My
next
issue
was,
I
was
wondering
if
there
were
any
issues
with
the
security
branch
only
being
on
auto
deploy
while
I
was
away
or
if
we
can
just
proceed
to
make
that
the
default
and
remove
the
feature
flag.
E
E
E
So
what
happened
was
that
the
new
auto
deploy
branch
was
created
after
the
the
fix
getting
merged,
so
the
peak
failed,
but
I
I'm
not
sure
if
this
is
how
it
works,
but
I
think
we
are
using
something
like
a
merge
train
to
to
bring
changes
in.
So
it
was
was
not
clear
at
that
point
in
time.
If
that
fix
was
in
or
not.
E
E
A
Yeah,
I
think
it
was
kind
of
confusing
because
now
create
we
create
auto,
deploy
branches
every
six
hours.
So
we
tried
to
pick
a
security,
a
fix,
but
it
wasn't
possible
and
then
the
fix
was
already
included
in
the
new
one.
So
we
really
didn't
have
to
do
anything
else
other
than
just
push
the
new
auto
deploy
branch.
A
C
C
We
were
waiting
on
the
new,
auto
deploy
branch
to
be
created
and
there
were
plenty
of
green
build
jobs
worth
to
choose
from,
but
it
picked
a
really
really
old
one.
So
I
ended
up
having
to
cherry
pick
the
revert
into
the
newer,
auto
deploy
branch
to
continue
forward
with
what
I
was
working
on
at
the
time.
I
don't
know
what
led
to
that
occurring,
but
I
don't
also
don't
know
if
that's
related
to
this
particular
feature
set
or
if
it's
a
new
issue
that
we
need
to
look
into
or
not.
Okay,.
B
A
Yeah,
I
pointed
an
issue
that
talks
a
bit
about
what
scarvet
experimented.
Somehow
some
of
the
branches
were
created,
identical
and
we
were
not
sure
about
it,
and
I
also
pointed
out
another
small
issue
we
had
when
we
created
this
stable
branch
for
the
major
release,
cool.