►
From YouTube: 2021-01-25 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
It
was
like
just
minutes
that
we
saw
each
other
cool,
so
added
a
couple
of
things
on
the
announcements
go
ahead.
If
there's
anything
else,
people
want
to
call
out
on
that
one.
A
Otherwise,
what
I
wanted
to
just
talk
about
a
little
bit
was
the
planning
board,
so
I
spent
a
bit
of
time
this
morning
juggling
some
things
around.
Let
me
just
share
my
screen.
What
I
wanted
to
so
my
kind
of
original
intention
behind
this
board
was
to
be
able
to
like
focus
our
attention
so
that
we
don't
all
have
to
be
trying
to
keep
up
with
absolutely
everything.
B
A
So
what
I'm
hoping
to
do
is
try
and
limit
this
down
a
little
bit
into
the
things
which
we
want
to
discuss
like
this
week
or
in
the
next
week,
or
so
so
either
things
that
we're
blocked
on
or
that
maybe
are
slightly
bigger
discussions.
That
would
be
worth
us
talking
about.
A
A
So
it
still
feels
to
me
that
having
11
proposals
to
kind
of
review
probably
is
still
too
many.
What
I'm
trying
to
do
is
just
simply
remove
the
planning
label,
and
then
we
have
our
kind
of
full
backlog
list
of
things
that
you
know
we
can
pull
in
as
needed,
but
in
terms
of
what
we
want
to
go
through
this
week,
so
scarbeck,
I'm
assuming
it
would
be
useful
for
you
to
actually
get
some
more
thoughts
going
on
that
geo
pipeline
work,
yeah,
cool
and
then
all
the
others
are.
A
We've
got
quite
a
lot
of
security
things
on
here,
so
I
don't
know
maira
whether
you
have
any
opinion
on.
I
call
you
out
just
I
think
you've
raised
most
of
this,
but
are
there
any
like?
Is
there
like
one
or
two
of
these?
That
would
be
most
useful
to
be
discussing
right
now.
C
I
don't
think
so.
I
just
reviewed
all
the
proposals,
proposals
that
are
there
and
yeah.
I
don't
think
we
need
to
discuss
it
right
now,
but
I
think
I
also
think
we
can
just
remove
the
delivery
team
planning
label
if
it
is
not
needed
there.
Okay,.
A
Yeah,
that's
fine,
so
yeah.
If
you
want
to
have
a
review
like
I'd,
say
it's
not
to
like
stop
all
conversation,
but
if
there's
one
like,
maybe
just
one
that
we
want
to
focus
on
for
now,
we
could
do
that.
I've
left
the
deploy
from
master
branch
on
there,
because
I
think
it's
worth
everyone
probably
having
a
read
through
that
again
this
week,
not
to
say
we
have
to
necessarily
answer
the
question
right
now,
but
there
will
be.
A
I
think
there
will
be
a
point
where
rollbacks
probably
become
easier.
If
we
make
a
decision
on
some
of
this
stuff,
that's
just
an
assumption.
So
I've
left
that
one
on
for
now,
like
not
to
say
we
have
to
have
a
final
answer,
but
I
think
it'd
be
worth
just
being
familiar
with
the
points
that
were
raised.
A
C
E
A
Yeah,
I
think
that's
correct
right
from
my
understanding
my
wrath,
I
don't
know
what
we
want
to
do.
It's
just
it's.
We
didn't
prioritize
it
last
week,
yep
yeah,
perfect,
okay,
I'll
just
move
it
into
into
ready
for
now
so
got
that
there's
improvements
to
delivery
release,
dashboard,
which
again,
I
think,
have
a
have
a
read
through
and
see
if
people
have
an
opinion
on
that
skybex
put
together
some
good
kind
of
proposals
on
particularly,
I
think,
current
release
managers.
A
If
you
have
thoughts
on
whether
this
will
help
or
not
for
you
that
useful
and
then
we
have
two
kind
of
new
ones
and
again,
if
we
can
make
a
if
we
can
find
a
small
iteration
that
looks
useful
for
these
for
automate
feature,
flag
approvals
or
addressing
tech
data
in
release
tools,
then
I
think
it'd
be
worth
bringing
them
through.
So
if
people
haven't
looked
at
those
ones
that
would
be,
you
know
useful.
I
do
think
most.
A
The
priorities
are
correct
on
these
labels,
though
geo
might
be
the
only
one
scarbeck
we
might
want
to
raise
up.
Based
on
how
urgent
you
think
this
is
coming
in.
So
also,
please
use
those
labels
to
prioritize
your
time
like
I
do
think.
Most
of
these
are
peoples.
A
So
if
you
need
to
drop
something,
this
would
be
a
good
place,
certainly
fantastic,
and
then
for
everyone
else.
Then
yeah,
if
you
wouldn't
mind
like
find
a
little
bit
of
time
this
week,
to
have
a
read
through
and
let's
see
if
we
can
get
some
of
the
proposals
into
ready
so
that
we
can
start
prioritizing.
A
Excellent
one
thing
I
was
going
to
say
about
the
board
is
so
for
me,
the
intention
I
say
is
to
help
us
focus
on
how
to
spread
our
time
and
attention
energy,
because
in
our
delivery
issues
backlog
we
have
about
300
issues.
So
there's
no
expectation
that
every
week
we
are
making
decisions
and
discussing
those
all
those
issues.
So
this
is
a
intended
to
be
a
bit
of
a
subset
for
those
things.
A
D
Well,
I
can
speak
for
myself,
so
I
think
that
this
is
a
great
habits
to
have,
but
we
are
kind
of
coming
from
a
very
let's
say,
not
so
organized
type
of
workflow.
D
So
I
mean
I
just
struggle
with
now:
I'm
just
I'm
also
doing
release
management,
so
I
also
spend
less
time
than
usual
in
issues
and
things
like
that,
but
I
think
that
it's
just
a
matter
of,
at
least
from
my
days
in
development
sticking
with
the
workflow
and
just
reiterating
the
concept
so
that
it
would
be
natural
for
us
to
just
say
yeah.
If
we
want
to
discuss
something
together,
we
just
need
to
apply
those
labels
because
then
monday
will
be
in
that
list
in
the
board,
and
we
will
talk
about
it.
A
Cool
yeah
that
makes
total
sense
like
what
I
have.
I
definitely
haven't
been
sort
of
tidying
up
and
helping
this
board
out.
I've
been
mostly
focused
on
the
billboard,
which
looks
pretty
healthy
now,
so
that's
great
news,
so
yeah.
I
will
make
sure
we
check
in
on
this
so
for
now
for
this
week
the
request
is
simply
anything.
That's
on
that
proposal
column.
Please
take
a
look
at
and
then
next
month,
next
monday
I'll
do
another
round
of
clean
up,
and
we
can.
We
can
iterate
through
that
stuff.
A
Awesome,
myra
fta.
C
Yep
thanks
so
last
week
was
quite
fun
because
we
had
a
lot
of
incidents
and
I
mean
a
lot
so
the
common
question
in
all
of
those
was
what
is
the
div
that
is
being
deployed
at
the
moment,
and
I
normally
what
I
do
is
to
either
rely
on
the
auto
deploy
status
command,
but
sometimes
it
is
not
super
trustworth
trustful
because
there
might
be
another
package
that
is
being
deployed
at
that
moment.
So
the
leaf
is
not
the
one
that
you
want.
C
So
what
I,
if
that's,
not
if
that
doesn't
work
for
me,
I
normally
try
to
graph
the
sha
from
the
package
that
I
am
investigating
and
find
out
what
was
the
last
package
that
was
deployed
and
then
grasped
the
difference,
but
it
is
just
a
lot
of
trouble
and
you
are
under
pressure
and
because
you
want
to
find
it
out
like
as
quickly
as
possible.
So
I
just
wonder
if
any
of
you
have
a
script
or
a
better
idea
of
how
to
do
this.
D
I'm
doing
exactly
the
same,
so
I
would
just
go
to
the
environments
list
of
the
the
security
project,
because
then
you
are
kind
of
sure
that
everything
is
there.
Also
when
you
are
in
security
mode
and
just
do
and
get
the
diff
between
what's
in
there
and
what
we
are.
It
really
depends.
That's
the
real
problem
right
because
it
depends
if
you
are
in
in
within
a
deployment
deployment
after
a
deployment
if
there
is
a
gap
in
what
it's
in
production
and
what
is
in
in
canary.
D
E
Browser
extension
for
it
I
was
using
the
announcements
channel
if
I
ever
need
to
get
that
information
which
I
don't
like.
I
think
it
sounds
like
the
fact
that
you're
asking
this
question
and
our
team
is
the
closest
to
this
information.
Maybe
we
should
improve
this
a
little
bit.
B
D
Yeah,
I
think
it's
a
good
idea,
jarv
as
well
as
yeah
from-
and
it's
probably
the
right
moment
in
time
where
we
can
actually
get
the
correct
diff,
because
at
that
point
we
either
we
start
or
we
start
early.
We
know,
what's
what
is
running
in
that
environment,
I
wish
we
could.
We
can
check
this
from
the
api
and
we
know
what
we
are
deploying,
so
we
can
build
the
diff
link.
D
I
will
like
I
had.
I
put
a
question
in
after
my
question,
because
this
is
just
one
part
of
the
problem.
Usually
it's
the
biggest
one,
but
there
is
also
omnibus
there
is
also
gita.
There
are
a
lot
of
other
things
that
changes
that
we
don't
have
a
quick,
quick
way
for
showing
this.
So
maybe
this
maybe
could
be
an
extension
to
our
release
management
dashboard.
D
I
don't
know
if
it's
something
easy
to
add
there,
but
kind
of,
because
I
would
like
to
really
have
a
kind
of
a
dashboard
where
I
can
see
this
is
this:
is
the
diff
between
what
we
are
deploying
and
what
is
in
there,
but
also
this.
This
means
that
italy
moves
from
this
version
to
this
other
version
and
being
able
to
see
the
same
diff
for
italy
as
well
as
omnibus
as
well
of
cng,
because
yeah.
B
B
E
A
Possibility
could
someone
open
an
issue
like
it
sounds
like
that
would
be
useful
enough
that
we
should
work
out
a
way
to
do
that
yeah.
I
can
do
that.
Okay,
thanks
it'd,
be
interesting
to
also
see
if
there's
anything
in
the
product
that
we
can
extend
or
yeah
whatever
like
options.
We
have
there
cool
thanks
for
raising
that,
though,.
A
Cool,
so
was
there
anything
else,
and
I
wanted
to
raise
on
the
recording.