►
From YouTube: 2023-02-22 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).
B
A
C
Morning,
I
would
say
that
we
can
start
so.
This
is
a
22nd
of
February
2023,
APAC,
Amia
delivery
group
weekly.
We
have
some
announcement.
I
think
I
actually
left
the
same
one
that
we
discussed
on
Monday,
so
nothing
new
there,
some
people
taking
some
time
off
friends
and
family
a
birthday
today,
actually
two
birthdays
today
coming
up,
and
we
have
a
discussion
point
from
Amy
that
she's
not
in
the
Hall
but
I
guess
we
can
start
you.
D
E
Awesome
so
I
wanted
to
is
someone
cool
I
wanted
to
just
give
you
all
a
kind
of
an
FYI,
because
I
know
that
some
of
you
may
have
already
seen
inside,
or
you
may
also
see
other
things
it's
like
so
configure
and
release
T
stage
groups
have
been
combined
and
they
are
now
a
new
Team
all
focused
on
kind
of
the
same
sort
of
problem.
There
is
discussions
inside
there
was
an
assumption.
It
sounds
like
it
was
just
the
the
name.
E
Delivery
was
used
as
a
placeholder
and
has
been
kind
of
assumed.
That's
what
the
team's
being
called
so
you'll
see
various
things
through
snapchat
channels
about
oh,
the
new
delivery
team,
or
this
is
being
the
delivery
team.
There
is
an
issue
that
is
in
progress
to
discuss
team
names.
Sam
is
working
with
Victor
to
figure
out
what
is
the
right
name
for
the
product
and
it
would
go
from
there.
E
Simon's
also
I
think
already
aware
of
the
cost
to
us.
If
delivery
goes
to
configure
and
release
like
what
we
would
have
to
do
to
move
off
the
delivery
name
and
the
confusion
that
would
cost
so
he's
figuring
that
out,
there
is
a
comment
in
there
around
orchestration
I'm
more
open
to
that.
Just
because
there's
not
a
heap
of
work
for
us.
E
If
we
end
up
shifting
off
that,
so
I'm
going
to
let
Sam
and
Vic
to
go
figure
out
what
makes
most
sense
from
the
product
I
know
we
can
respond
from
there,
but
just
wanted
to
make.
Let
you
all
know
in
case
you
are
seeing
that
around
in
slack
that
this
is
definitely
not
yet
a
a
final
final
naming.
E
Cool
and.
F
C
C
E
C
Okay,
perfect
another
question
around
that
in
the
case
that
things
got
not
only
on
the
right
direction
and
we
are
kind
of
like
asked
to
be
renamed
I
think
it's
something
that
we
need
to
plan
for,
because
I
guess
we'll
have
a
lot
of
work
to
do
even
to
rename
ourselves
and
I
think
it's
something
that
probably
should
kind
of
like
make
it
visible.
That
is
not
something
just
renaming
a
variable
somewhere
and
it's
going
to
end
up
everywhere.
That's
right!
C
C
E
Hope
that
will
just
become
completely
unnecessary
work.
Judging
from
the
comments
already
and
since
we
already
have
quite
a
lot
of
other
tasks
going
on
I
think
probably
better
that
we
just
armed
Sam
with
the
info,
he
needs
and
let
him
go
go
work
out.
What's
going
to
be
best
yeah.
A
E
That's
it
exactly
it's
all
of
that
stuff.
You
know
like
release
issues,
there's
a
ton
of
little
things
that
rely
on
the
delivery
name
exactly
so
just
let
make
sure
and
I
think
if
Sam
does
agree
to
a
switch
like
this,
then
what
we'll
have
to
do
is
same
as
we've
always
done.
When
we
have
these
kind
of
ad
hoc
projects
come
in
is
we
will
very
visibly
pause
on
okrs
or
something
like
that
to
give
ourselves
like?
Okay,
delivery
group
needs
to
now
spend
x
amount
of
time
doing
this
thing
right
like
it.
E
B
D
B
E
E
E
The
main
thing
is
the
visibility
right,
so
just
how
long
will
the
confusion
go
on
for
if
somebody
says
oh
delivery,
like
you
know,
like
people
have
in
my
and
my
their
mind
already
what
that
means.
So
I
suspect
we
don't
need
to
worry
about
delivery,
orchestration,
maybe
less
so
but
I
say
I'm,
not
actually
super
attached
to
to
that
name.
It's
it's
much
easier
for
us
to
just
re
like
we
could
just
rename
some
labels
like
and
update
the
handbook.
It's
it's
not
going
to
be
the
end
of
the
world.
E
If
we
have
to
move
off
that
one,
but
we
can,
we
can
see
what
that
looks
like.
E
So,
let's
let's
figure
and
then
we
make
follow-up
plans
afterwards,
good.
E
And
then
my
second
one
is
kind
of
also
related
I,
think
which
is
I'm
personally
seeing
increased
numbers
of
kind
of
ad-hoc
requests
coming
my
way,
I
think
that's
expected.
Just
as
teams
are
reorging
they,
you
know,
people
have
got
new
longer,
backlogs
priorities
are
changing,
but
I
suspectra
will
probably
see
the
same
stuff
right.
So
just
as
a
if
you
need
to
push
back
on
stuff,
please
do
it'll,
be
we
continue
with
deployments
and
releases
and
okrs.
E
If
you
have
other
requests,
then
just
consider
how
that
actually
fits
in
with
those
things
right,
not
to
say
you
shouldn't,
do
it
and
actually
something
which
doesn't
happen.
Often
enough
is
not
very
many
people
ever
challenge
the
team
priorities
that
McKelly
and
I
post
on
Mondays.
That
is
absolutely
the
place
where
you
all
should
be
coming
back
to
us
and
saying
hey,
but
you've
asked
me
to
do
this
other
project
or
I'm
involved
in
this
other
thing
that
we
must
do
right.
E
So
please
do
challenge
us
either
on
slack
or
in
your
one-to-ones,
so
that
we
can
make
sure
that
we're
not
trying
to
just
do
everything.
That's
largely
the
thing.
I'd
like
us
to
avoid
is
we
can
never
ever
do
everything.
So,
let's
be
clear
on
like
what
we
actually
choose
to
do,
and
then
we
can
tell
other
people
we're
not
doing
that
thing
and
escalate
up
if
we
need
to.
We
have
a
lot
more
support
now
with
Sam
and
with
Fabian
around
as
well
as,
of
course,
my
own.
E
So
we
we
have
a
lot
more.
We'll
have
a
lot
more
people
to
help
us
actually
prioritize
things
later
if
they
need
to
or
figure
out
alternative
plans
or
basically
help
us
help
us
keep
our
workload
manageable.
C
F
I
have
a
small
question
yeah.
So
when
a
package
starts
getting
deployed
to
production,
a
comment
is
posted
automatically
to
the
monthly
release
issue
should
should
there
be
information
about
the
diff
that
is
being
deployed
in
that
comment,.
D
A
You
mean
to
give
it
a
diff
compared
to
the
last
promotion
right,
not
the
last
package
yeah.
So
if
you
don't
promote
things
in
between
when
you
promote
you
want
to
to
write
there,
this
is
what
is
in
production,
now
I'm
rolling
up
this.
So
that's
the
diff
and
so
you're
skipping
everything
in
between,
because
you
you
care
only
about
okay,
yeah.
E
I
I
mean
I'm
very
much
like
I'm,
not
gonna,
say
we
shouldn't
do
it.
I
would
put
it
definitely
in
the
nice
to
have
category.
So
if
you
want
to
go
for
it,
then
do
it,
but
I
personally
wouldn't
prioritize
it
against
other
things.
Like
you
know,
I
I
wouldn't
say
we
shouldn't
do
this
okr
because
we're
doing
that.
But
if
you
know,
if
you
want
to
go
for
the
change
and
the
kind
of
like
as
a
as
a
side,
change
I
wouldn't
be
against
them.
E
I
think
the
the
main
things
of
what
we
track
right
now
are
the
things
compliance
are
looking
for.
So
I
think
if
there's
some
additional
benefits
to
tracking
it.
Fine,
but
I,
don't
think
it's
not
like
compliance
are
not
asking
for
it.
They
have
the
information
they
need
already.
F
Sounds
good.
The
reason
I
asked
just
for
context
is
because
sometimes
we
have
to
search
for
the
diff
of
like
a
package
that
was
previously
promoted
or,
and
it's
I
think
it's
easier
to
search
on
the
monthly
release
issue
rather
than
going
to
slack,
and
you
know
scrolling
through
messages.
A
Have
something
as
well
that
came
to
my
mind,
reading
a
message
right
now,
so
there
is
this
new
Sentry
instance
right.
So
is
anyone
aware,
if
what's
the
plan
to
Sunset
the
old
one,
because
we
are
sending
information
to
the
old
one
when
we
deploy
something
we
are
creating
releases
and
things
like
that,
so
I'm
wondering
I,
don't
even
remember
how
we
do
this
if
we
have
token
or
something
like
this
and
how
this
will,
if
and
how
we
have
to
change
this,
to
go
to
a
new
instance.
D
My
understanding
is,
they
are
going
to
so
it's
already
up
at
like
newscentury.gitlab.net
or
whatever.
It
is
I
think
eventually,
they're
doing
the
DNS
switch
like
so
they're
literally
century.getlab.net
will
just
suddenly
point
to
the
new
one.
You
would
hope
that
that
meant
they
were
going
to
migrate
all
the
access
tokens
and
stuff.
So
none
of
these
apps
broke.
But
that
is
a
very
good
question.
We
should
figure
out
if
we
do
have
to
do
anything.
A
Yeah,
so
the
old
one
is
the
one
that
we
are
using
is
kind
of
I
mean
I.
Think
you
generate
your
account
using
Google,
something
like
this.
So
you
log
in
with
Google
Apps,
and
you
are
mutant,
green.
A
Yeah
so
strange,
it's
anyway,
it's
a
service
in
that
sense,
but
it's
not
using
OCTA
and
I
think
it's
also
running
a
very
old
version
of
Sentry.
So
my
understanding
was
that
ethiops
took
ownership
of
Sentry
as
a
system
and
they
created
a
new
instance
that
is
running
with
octar,
so
everything
is
centralized
and
they
are
I,
don't
know.
F
Think
we
use
Sentry
in
two
ways:
right,
one
is
to
check
for
issues
in
the
main
rails
repository
and
the
other
is
to
actually
upload
errors
in
release.
Tooling
is
the
Sentry
integration
for
release
tooling
working
because
I've
seen
a
lot
of
Sentry
errors
in
the
last
few?
Actually,
the
last
few
weeks,
I
think.
D
F
A
C
Okay,
any
other
topics
to
discuss.
B
Yeah
I've
added
this
observability
topic
for
the
pipelines
and
like
for
delivery
in
general,
but
I
don't
know
like
when
I
click
on
the
link
in
the
invite
it
says
you
have
no
access
but
I
found
like
the
document.
B
I
found
the
document
Delivery
Systems,
you
can
demo
and
I've
added
there,
but
it
looks
like
it's
I
don't
know.
Do
you
see
my
my
discussion
point
no.
A
D
B
Yeah
now
I
see
that
yes,
okay,
okay,
perfect
so
anyway,
like
let's
maybe
discuss
a
little
bit
of
observability
and
the
ideas
that
we
have
so.
C
Just
don't
want
to
for
the
sake
of
time,
we
only
have
eight
minutes
left
Vladimir.
Oh,
how
long
is
gonna
take,
because
we
also
have
to
go
through
release
management.
Is
it
something
that
we
can
discuss
today
in
the
Living
Single
demo?
You
think.
C
Okay,
perfect:
it's
okay,
no
worries;
okay,
Place
Management
Ruben;
this.
There
are
something
to
go
through
today.
F
I,
don't
think
there's
much
of
an
update
from
Monday
I
will
say,
though.
The
last
few
days
has
seen
a
lot
of
incidents,
but
I
don't
think
there's
anything
to
go
through
unless
someone
has
any
questions.
D
My
only
question
is:
have
you
been
seen
a
lot
in
your
kind
of
because
your
APAC
in
more
Europe?
Do
you
have
you
been
seeing
a
lot
of
incidents
in
your
APAC
Europe
time
zone
and
do
you
think
we've
been
having
a
lot
in
us
as
well,
because
in
APAC
I'm
seeing
a
lot
I'm
just
trying
to
establish
if
it's
kind
of
evenly
distributed
or
what
sometimes
owns
the
same
more
than
others
but
I
know
you've
just
got
anecdotal
evidence.
F
Yeah,
do
you
mean
like
have
any
incidents
started
during
the
emea
time
zone.
C
F
D
D
F
D
E
Make
sure
those
are
all
labeled
up,
because
I
think
when
we
do
get
increasing
bursts
like
this
it
could.
They
could
be
related
to
test
changes,
or
you
know
there
could
be
like
an
underlying
cause.
That's
allowing
things
to
happen
so
I
definitely
want
to
make
sure
we
follow
up
with
other
teams
to
make
sure
we're
not
just
receiving
like
side
effects
of
other
changes.