►
From YouTube: 2023-07-26 Delivery team weekly APAC/EMEA
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
B
C
Okay,
welcome
everyone.
This
is
our
26th
of
July,
it's
APAC
email,
delivery,
weekly
get
the
right
name,
and
it
also
is
our
oh.
No,
it's
not
I
played
that
back.
I
was
going
to
say
final
final
delivery,
weekly
of
the
quarter,
but
actually
no
Mondays
is
officially
the
final
one.
So
I'll
take
that
back,
so
I
just
dropped
in
a
quick
announcement.
We
have
a
infra
and
quality
group
conversation
tomorrow.
So
at
the
very
least,
please
read
through
the
sides,
see
what
people
have
been
up
to.
C
If
you
want
to
drop
a
question
in
the
agenda,
that
would
be
very
welcome
if
you
want
to
come
along
to
the
call
and
also
take
part
in
the
discussion.
That
would
be
even
better,
but
please
do
check
out
the
the
slides
at
least
and
two.
This
may
be
a
big
peen
I
think,
since
we
just
added
this
on
Monday,
but
is
there
anything
that
should
be
in
the
change
lock
since
Monday.
A
I
think
there
might
be
some
things
related
to
the
security
release.
I'll
make
a
list.
C
B
C
A
Yeah,
that's
what
I
think
more
like
an
FIA,
but
also
there
are
some
things
like
like
the
fact
that
if
any
job
fails
in
the
first
steps,
you
can
just
ignore
it.
You
know
check
it
manually
and
and
it's
not
like
a
regular
pipeline
where
something
fails
you
know
the
entire
pipeline
is
stuck
until
you
fix
that
failure.
So
maybe
that
can
be
mentioned
in
in
the
docs
and
then
we
can
just
link
to
it
from
the
change
log
yeah.
C
Yeah
that
sounds
good,
yeah
and
I'm.
Hoping
Steve
will
take
a
look
at
this
because,
ideally
you
shouldn't
have
anything
you
should
need
to
ignore.
The
idea
is
that
the
pipeline
results
are
giving
you
the
correct
information.
So
there's
there's
some
improvement
from
our
slide
on
the
the
fact
you
have
a
failure
that
you
can
just
ignore,
so
we
should
change
that.
A
C
C
It's
pretty
fast.
The
final
steps
is
going
to
be
in
testing
next
week,
so
that
also,
hopefully,
is
another
like
big
win.
So.
A
C
Awesome,
great
and
I've
got
a
discussion
item.
It
may
just
be
a
bit
of
a
quicker
one
since
there's
only
a
few
of
us
here,
but
I
was
wondering,
since
we
are
now
approaching
the
end
of
the
quarter
and
we're
sort
of
looking
at
what
to
do
for
Q3
I
was
curious
about
people's
thoughts
on
like.
Is
there
anything
you
would
like
to
see
improved
or
changed
for
cross-team
sharing,
so
I'm
wondering
like
we
have
Team
priorities,
get
posted
in
slack
each
Monday.
C
We
have
epic
statuses
through
the
week
There's
a
grand
review
on
Friday
and
also
they're,
like
ad
hoc
messages.
Curious
to
hear
on
people
sort
of
say
are
those
useful
like?
Are
they
enough?
Is
there
other
stuff,
not
necessarily
like
other
Solutions,
but
like?
Are
there
other
pieces
of
information
you
would
like
to
be
receiving
on
a
more
regular
basis.
A
The
Epic
statuses-
sorry,
not
epic
Services.
The
the
weekly
priority
list
is
useful.
The
Grand
Review
is
also
useful,
so
yeah,
it's
been
useful
for
me.
D
B
So
I'm
finding
the
the
ground
review
for
very
useful
for
the
platform
level
when
you
want
to
see
what
is
happening
on
a
high
level
on
everything
else,
I
find
it
less
useful
for
cross
delivery
information
because
it's
kind
of
a
hit
and
miss
because
not
every
time
the
host
goes
into
the
details
of
what
is
happening,
and
this
is
okay
at
that
level,
because
they're
giving
an
overview
of
everything,
but
for
a
thing,
people
that
works
more
closely
related
to
each
other.
B
C
Do
those
things
connect
up
enough
like
I'm
wondering
like
right,
because
Grand
reviews
are
slightly
different,
look
compared
to
team
priorities
like
would
it
would
it
be
helpful
if
we
actually
tried
to
kind
of
almost
including
the
10
priorities
like
the
here
is
the
ideal
delivery,
Grand
Review
info,
plus
the
10
priorities.
C
Just
I
think
a
bit
more
of
a
what
we
have
done
is
probably
what
I'm
thinking
is
different,
so
like
I
think
Grand
Review
is
kind
of
like
here
is
the
Epic
status,
which
says
like
here's
what's
been
achieved,
and
and
why
and
here's
what
we're
planning
to
do
next
and
why
and
I
think
team
priorities.
I
think
can
sometimes
be
a
little
bit
more
focused
on
this
upcoming
week.
We
want
to
work
on
this
particular
task.
D
So
simply
a
link
to
the
status
of
the
epics
at
building,
Grand,
Review
or
more
of
an
explanation.
Yeah.
C
Like
a
sentence
or
two
on,
like
you
know,
say,
for
example
like
say,
for
example,
security
releases
right
like
we
have,
the
first
steps
are
pretty
much
complete
and
being
used,
and
we
we
maybe
have
a
bit
of
improvement
to
do,
but
we're
actively
working
on
the
final
steps
ready
for
the
next
security
release,
which
is
like
the
Epic
status
and
then
and
this
week
we
want
to
get
through.
You
know
this
these
particular
three
jobs
and
get
those
ready
for
security.
Don't
release.
B
It
seems
to
I
mean
I
think
it
could
be
useful,
but
it
seems
like
we're
spending
more
time
on
rewarding
the
same
information
that
we
already
have
to
put
in
in
the
epics.
So
I
don't
know
if
just
direct
link
to
the
on
progress
table
on
release
velocity
that
can
be
posted
when
we
do
the
priorities.
B
About
what
we
have
done,
what
we
have
achieved
last
week
link
right.
C
D
I
think
the
part
I
agree
on
the
other
side.
Sometimes
these
status
updates
on
the
epics
are
to
the
technology
or
something-
and
maybe
you
have
some
people
in
the
team
that
will
buy
okay.
D
What
is
this
about,
and
you
know
so
yeah
so
I
agree
that
we
can
reward
on
the
other
end,
some
I
can
I
could
feel
that
someone
might
might
lose
some
context
on
that,
but
so
I
don't
have
a
solution.
Just
like
wanted
to
raise
this
up.
Yeah.
B
D
D
Another
thing
I
wanted
to
ask:
we
want
to
have
a
end
of
the
quarter.
Joint
orchestration
system
kind
of
demo.
B
D
Three
demos,
something
like
that,
so
everyone
is
a
bit
more
up
to
speed
or
what
is
going
on
in
both
teams.
C
Yeah,
like
we
should
be
able
to
do
that,
I'm
orchestration
may
be
maybe
more
equipped
to
do
this
async,
but
don't
let
that
stop
us,
like
we'll,
have
a
think
about
this.
Guy
picky
Alessia,
you've
already
recorded
your
super
fast
CI,
stuff,
I,
I,
you're
you're
off
from
Monday.
Is
that
right,
yeah,
yeah,
so
I
was
thinking.
We
could
do
this
on
Monday,
but
alessia's
already
recorded
a
good
recording
of
of
the
kind
of
in
the
most
interesting
thing.
I
think
that's
coming
on.
C
D
Can
push
it
to
a
week
after
we
don't
have
to
do
it
on
Monday,
if
it's
easier
for
everybody,
you
know
it's,
it
was
it's
also
something
that
if
we
don't
want
to
start
to
apply
this
quarter,
we
can
already
apply,
for
the
next
quarter
is
something
that
I
wanted
to
know.
If
you
were
up
with
the
idea
about
having
kind
of
okay,
this
is
the
end
of.
C
D
We
can
pre-record,
it
I
think
it's
gonna.
It's
gonna
be
more
difficult
to
kind
of
ask
questions
when
something
is
pre-recorded.
D
B
So
what
we
worked
on
this
quarter
as
orchestration
is
really
hard
to
demo,
because
it
has,
inter
it
interacts
with
live
systems
and
change
status
of
branches,
and
that's
why
we
have
the
recordings,
because
of
just
an
example,
so
I
did
recording.
That
Amy
was
mentioned
in
my
GDK
to
show
the
thing
to
to
the
team,
and
then
we
were
testing
this
when
it
was
merged.
We
were
testing
this
live,
but
in
order
to
test
it
live,
we
had
to
have
upsec
online,
a
lot
of
people.
B
So
when
yesterday
was
the
demo
time
was
just
going
through
the
screenshot
and
the
pages
of
the
things
that
happened
when
I
was
testing
it
right.
So
and
basically
that's
the
same
thing
that
Myra
did
yesterday
in
order
to
show
a
demo.
She
basically
changed
out
of
the
code
in
order
to
not
interact
with
this
this
and
that
which
kind
of
gave
us
an
idea
of
the
structure
and
everything.
But
maybe
if
we
want
to
see
how
it
works,
it's
easier
to
record
the
final
step
of
of
the
upcoming
security
release.
D
B
D
C
Okay,
let's
talk
about,
let's
like
let's
make
a
plan
for
how
we
can
do
that
logistically,
but
yeah
I
think
we
should
I
think
it
would
be
great
to
do
a
kind
of
a
wrap
up
of
what
we
did
to
each
call
in
the
quarter
and
also
to
share
a
bit
about
what
we're
planning
for
next
quarter,
appoint
people
in
the
kind
of
right
direction
so
that
yeah
we
share
some
context
so
yeah,
let's,
let's
catch
them
on
me-
can
I
get
get
a
plan
for
Monday.
D
C
D
D
D
Yeah
I
only
have
Reuben
on
Monday
you're.
D
A
B
No,
but
this
I
think
this
is
you're
right
so
because
it's
a
packager,
the
same
is
for
CNG,
but
the
thing
when
what
this
is
doing.
B
So,
basically,
if
you
go
to
the
link,
when
you
say
the
components
under
managed,
versioning
in
the
docs
say
that
gitlab
Omnibus,
gitly
pages
and
CNG
are
considered
managed
versioning,
because
we
generate
tag
and
and
branches.
So
that's
the
managed
versioning,
it's
managed
versioning
when
we
tag
and
generate
branches.
B
The
version
file
is
just
a
mechanism
for
propagating
versions
between
the
packages
and
the
application,
but
the
what
we
meant
here
is
that
if
we
generate
if
there
are,
if
there
are
projects
where
we
generate
stable
branches
and
tags
as
part
of
the
release
process,
there's
this.
This
is
what
we
are
talking
here.
B
C
B
C
A
No
I
mean
it
does
clarify
that
we
don't
have
to
change
anything
for
Neighbors,
no.
B
It's
just
if
Pages
or
or
gisely
have
security
issues,
then.