►
From YouTube: 2022-01-31 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
Awesome,
hey
everyone
happy
monday,
so
we've
got
a
few
announcements
on
there
for
you
to
read
particularly
make
note
of
one
b
and
one
c
discussion
items:
okay,
okay,
oh
okay,
very
you've
explained
it.
I
was
super
surprised
I
was
like.
I
was
under
the
impression
that
no
one
had
access
to
this
project,
which
is
not
intentional.
It's
just
literally
that
it's
on
my
to-do
list
to
get
this
figured
out
so
that
you
that
you
can
have
access.
A
But,
most
importantly,
so
we
can
have
a
bot
to
have
access
and
then
the
release
tools
can
just
the
like
security
process
can
just
ping
ping
on
that
issue.
So,
okay,
good
to
know,
I
will
continue
with
my
original
plan,
which
is
to
get
a
bot
sorted
out,
but
maybe
myra
actually
I'll
work
with
you
on
doing
this
in
the.
If,
like
the
future,
since
you
already
have
access,
you'll
probably
be
able
to
be
the
best
person
to
help
either
yeah,
I'm.
B
Okay
with
it,
I
think,
in
the
future,
we
can
also
add
the
release
tools,
bot
and
have
a
command
like
in
chat.
Ups
too,
with
the
due
date:
okay,.
A
Yeah,
exactly
okay
cool
all
right,
thanks
so
b,
so
b
is
more
of
a
just
kind
of
showing
some
info
stuff,
so
alessio
is
away
which
gives
us
a
few
gaps.
So
a
few
things
whilst
we'll
have
a
few
extra
bits
and
pieces
to
pick
up,
but
just
as
a
kind
of
a
request
to
please
make
sure
your
epics
are
updated
at
least
once
a
week,
they're
running,
auto
updates
that
pull
the
updates
onto
the
epic
170..
A
So
if
ever
you're
not
sure,
if
like
did
I
do
this
recently,
have
I
forgotten
about
any
epics
or
you
know
if
you
want
to
help
each
other
out,
then
that's
the
place
to
have
a
look
at
and
the
most
important
thing
about
that.
Epic
is
that's
the
kind
of
landing
point
for
people
outside
the
team.
So
if
steve
is
looking
for
updates
on
what
are
we
working
on
or
where
we're
up
to,
that
would
be
the
epic
he
would
land
on
and
that's
where
he's
pulling
from.
A
So
that's
kind
of
a
handy
way
to
just
keep
things,
keep
things
up
to
date
and
when
you're
picking
things
up,
please
assign
them
to
yourselves
when
close
them
when
they're
complete
and
if
you
think
something's
going
on
for
a
super
long
time
just
have
a
think
or
ask
each
other,
maybe
like.
If
there's
a
way
you
can
cut
it.
A
So
it's
a
smaller
scope
and
we
can
close
an
issue
and
come
do
another
one
later
or
you
know,
are
we
trying
to
do
too
much
or
just
generally
check
in
with
each
other
and
see?
If
there
are
ways
we
can
keep
issues
kind
of
moving
along
and
then
on
b,
four
I've
shared
here.
I
have
a
lot
of
my
to-do's
on
this
board.
So
these
are
things
which
are
generally
going
along
that
you
maybe
don't
see
so
much
day-to-day.
A
A
A
Awesome
cool
so
see
ahmad,
ok,.
C
So
this
is
a
quick
discussion
item,
since
g-staging
graph
is
failing
frequently,
while
deploying
deploying
so
like
it's
a
suggestion
that
we
removed
the
auto
lock.
So
basically
we
don't
got
get
logged
and
like
intervene
like
manually,
basically
every
time.
So
what
do
you
think
people.
B
B
B
D
A
E
A
C
Remember,
I
think,
like
there's
a
ticket
to
improve
the
stability
of
yes
engine
ref,
and
that
was
the
issue
she
was
pointing
to.
So
I'm
not
sure.
F
C
Yeah
yeah
I
disabled
actually
like
the
notification
based
on
her
suggestion
to
notify
on
failure,
and
we
manage
that
so
right
now.
I
don't
think
we
will
get
notifications
when
the
pipeline
fails.
A
A
Do
you
know
how
to
remove
that
lock
or.
A
A
Yeah,
do
you
two
mind
just
figuring
that
out
like
it
can
be
just
a
temporary
thing,
but
I
know,
since
there
is
an
issue
to
improve
stability,
it
feels
like
maybe
until
that's
closed.
We
should.
We
should
be
a
bit
more.
A
It
feels
like
we're,
unlocking
this
thing
an
awful
lot
right.
It's
probably
worth
thinking
awesome.
Thank
you
for
bringing
that
up.
So
is
there
any
other
stuff
you
want
to
chat
about
on
that
stuff.