►
From YouTube: 2023-02-15 Delivery Group: Ruby 3 Rollout
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
You
know:
oh
yeah
I
wrote
this
down
quite
a
quite
some
time
ago,
actually
earlier
in
the
week
where
we
got
confirmation
that
basically
no
manual
testing
is
required
during
the
rollout
from
the
stage
teams.
B
B
I
guess
like
they
got
their
testing
environments
up
to,
like
the
testing
part
that
they
wanted
and
yeah.
They
don't
need
to
do
that
during
the
rollout.
So
that's
yeah
as
far
as
a
huge
celebration,
because
that's
like
one
less
dri
that
needs
to
be
involved
in
this
process.
B
One
less
point
of
failure.
Well,
that's
a
huge
plus
and
yeah.
According
to
our
sync
last
week
you
know
I
was
able
to
reduce
down
the
whole.
B
What's
it
called
the
rollout
time
and
that
still
needs
to
reflect
the
QA
full
speed
test
which
takes
about
15
minutes,
but
then
that's
still
was
like
like
it
should
be.
It
should
be
plenty
what
we
have
right
now
for
make
times
so
yeah,
just
the
QA
test
to
worry
about
and
no
specific
stage
groups.
A
B
A
B
A
B
So
two
things
right,
so
we
have
basically
like
a
timetable
of
specific
dris
from
teams
that
we
really
need
like
hand
on
Deck
kind
of
thing
so
such
as
you
know,
application
performance,
team,
I,
don't
have
the
story
right
in
front
of
me,
but
I
think
it's
under
the
schedule.
The
final
scheduled
one
yeah,
so
we
have
here.
Let
me
show
my
screen.
B
B
We
need
to
find
people
from
distribution,
but
anyways
there's
this,
but
then,
when
you're,
asking
about
stage
groups
I'm
more
leaning
towards
if
anything
goes
wrong
depending
on
what
the
failure
is
right
and
then,
if
we
and
if
we're
very
early
in
the
rollout
phase,
you
know
I
believe
it's
like
you
know,
application
performance
might
be
able
to
make
that
call
of.
B
Do
we
involve
that
stage
group
or
like
whatever
in
that,
but
I,
don't
think
they'd
be
needed
to
Grant
like
a
pretty
strict,
like
scheduling,
dri
schedule
for
that
matter.
Yeah.
C
A
Okay-
okay,
let's
not
formalize
that
maybe
we
can
I
mean
they're
gonna,
be
aware
when
we
roll
out
right.
Maybe
we
just
send
a
messaging
that,
in
case
of
minor
problems,
when
we
want
to
roll
backman,
we
just
actually
want
to
fix
that
there
should
be
someone
from
a
state
group
that
should
be
at
least
available
to
answer
a
slack
message
or
two
or
website
what
to
do
next
right.
A
C
A
Okay,
perfect:
okay,
do
you
during
your
checking's
journey,
do
you
have
contact
with
the
state
groups
or
is
mainly
Matthias,
that
is
coordinating
that.
A
B
B
A
Perfect,
thank
you.
One
thing
did
you.
There
was
a
comment
from
Igor
vidler
yesterday
and
let
me
let
me
pick
it
up.
B
A
C
A
C
Yeah,
okay.
So
the
next
item
is
the
deployment
schedule.
I
noticed
that
Jenny
put
together
the
Ari
timetable,
which
is
super
useful
I,
just
wanted
to
mention
that
under
the
quality
one,
there
is
a
person
that
was
recently
impacted
with
the
ruralization.
So
we
need
to
check
that
I'm,
not
sure
what
is
the
next
step
here,
I'm,
not
sure
if
we
should
ask
for
BNC
to
help
us
set
someone
available
or
if
we
should
ask
someone
else.
C
I
am
going
to
leave
that
up
to
you
Michaela,
to
help
us
figure
that
out
yes
and
then
for
the
dris
on
the
quality
side,
whether
whoever
is
choose,
we
need
to
make
them
aware
that
they
need
to
execute
the
full
pipeline
from
the
Q
a
on
each.
C
It
is
not
just
like
hey
just
me:
keep
an
eye
on
the
quality
pipelines
is
also
like.
You
need
to
take
action
during
the
deployment
schedule,
so
they
need
to
be
aware
of
that,
and
also
I
noticed
that
their
application
performance
team
is
mostly
based
on
Europe
I
think,
but
we
do
also
need
coverage
from
Amer
and
we
need
to
all
engage
with
them
about
this,
like
what
is
going
to
happen
with
the
hammer
time
zone.
If
there
is
someone
available.
A
A
B
B
Yeah
I
I'll
probably
ask
Matthias
on
both
the
both
about
the
Stage
Group
dri
and
this
oh,
this
one
yeah.
C
A
A
Yeah
perfect,
okay.
C
Okay
and
then
regarding
the
deployment
schedule
itself,
Igor
and
ascarbeck
made
a
comment
on
the
change
request
about
how
well
that
will
be
the
procedure
to
roll
back
days
later.
If
anything
is
fine
like
if
we
found
something
that
went
completely
wrong
and
we
need
to
roll
back
and
yes,
I
I
understand
that
they
have
a
point
so
I
think
a
deployment
is
scheduled.
That
currently
looks
like
well
I,
just
put
it
there,
but
I
can
quickly
summarize
it.
C
We
are
going
to
have
on
the
day
two
days
before
deployments
to
getlove.com
and
then
the
last
execution
of
the
post
deployment
migrations.
Then,
one
day
before
we
are
going
to
stall
half
deployments
to
gitlab
and
communia
and
on
Amer
we
are
going
to
post
them
and
prepare
the
auto
deploy
package.
Then,
on
March
7
we
are
going
to
have
the
Ruby
3
upgrade
the
actual
upgrade
and
then
on.
March
8th,
the
PC
elf
is
going
to
be
lifted
and
deployments
can
continue,
but
I'm
thinking
that
the
PDM
can
still
be
passed.
A
B
Do
we
so,
let's,
let's
wear
the
content,
Pros
right,
obviously
the
pro
being.
We
could
roll
back
from
this,
and
in
that
sense
we
would
probably
want
to
quote
unquote
Let
It
Bake
for
as
long
as
as
long
as
you
know.
We
want
it
to,
but
what's
the
con
of
not
having
the
PDM
go
out.
C
Basically,
we
kind
of
stop
development
velocity,
because
some
developers
rely
on
indexes
being
created.
Foreign
key
is
being
created,
Etc.
B
C
C
A
Not
expecting
you
know,
I'm
not
expecting
a
PDM
to
cause
any
problems.
What
I'm
expecting
is
like
okay,
something
happens
during
the
weekend.
We
actually
run
a
PDM,
so
we
cannot
really
roll
back
to
the
previous
package,
so
I'm
kind
of
more
keen
kind
of
on
the
night
or
on
the
Monday.
C
Okay,
I
guess
it
can
be
also
up
to
the
contents
of
the
PDM.
If
the
PDM
only
contains
index
creation
or
anything
like
that,
I
guess
it
is
okay
ish
to
be
executed
on
the
ninth,
but
it's
it's
hit.
If
it
has
also
background
migrations
and
all
the
data
migrations
that
might
be
risky,
perhaps
it
would
be
better
to
execute
it
on
Monday.
C
Yeah
to
summarize
I
think
this
can
be
like
some
sort
of
decision.
At
the
moment
we
can
analyze
it
on
the
ninth
if
we
should
execute
them
and
just
wait
until
Monday.
B
C
B
C
So
I'm
gonna
set
it
tentatively
to
the
ninth
and
then
yeah
I'm
gonna,
put
that
in
the
plan
awesome.
A
A
C
We
are,
we
are
waiting
for
the
1510
monthly
release
issue
to
be
opened,
so
we
can
actually
put
all
those
steps.
C
Awesome
and
then
well
since
the
day
is
getting
closer
and
closer
I
think
we
are
three
weeks
yeah
sort
of
three
weeks
from
now
I
wonder:
I'm
excited
Jenny
I'm
excited
what
are
the
logistics
for
it
and
when
I
say
Logistics
I
mean,
are
we
going
to
send
an
invite
to
all
the
dris?
Are
we
going
to
have
a
dedicated
Zoom?
Are
we
going
to
have
a
dedicated
slack
Channel
yeah.
B
So
what
I
was
thinking
is
before
we
okay.
Let
me
a
much
better
visually
than
orally
I
guess,
but
let's
just
go
to
actually
no
it'll
be
the
draft
okay.
Let
me
just
refresh
this
once
just
in
case
something's
changed
it's
where
I
logged
in
this
morning,
please:
okay,
okay!
So
we
have
these
pre-changed
steps
on
March
6th,
right,
I'm,
guessing
before
we
start
this
right.
So
pre-pre-change
we
have.
B
We
have
the
slack
Channel
created.
We
invite
everyone.
We
invite
all
the
dris
there,
also
because
we
have
the
March
6
American
dri
on
like
it's
like
a
just
in
case
kind
of
thing.
B
While
you
know
the
packages
are
getting
done,
we
just
do
it,
then,
so
that
that
way
we
don't
have
to
deal
with,
like
kind
of
like
slack
Logistics
Zoom
Logistics
during
March
7th,
when
we're
already
busy
doing
this
right
so
either
the
sixth
either
the
fifth
even
well
like
at
the
slab
Channel
created,
we'll
get
the
zoom
created
like
the
Zoom,
can
just
linger
right.
It
doesn't
need
to
technically
have
someone
in
it
to
be
like
quote-unquote,
alive
right.
A
C
C
B
So
yeah
a
new
channel,
Zoom
link
will
be
pinned
and
then
this
this
change
request
will
be
pinned
as
well.
So
people
cannot
follow
along.
C
A
Yes,
Jenny
for
the
dri
for
distribution.
Do
you
need.
B
A
C
C
B
B
A
A
B
B
I
want
to
I
mean
afterwards,
I
mean
I'm,
hoping
nothing,
nothing
bad
happens.
I
won't
I,
don't
want
to
call
like
a
post-mortem
kind
of
thing,
but
I
do
want
to
talk
about
the
possibilities
of,
maybe
in
the
future
of
doing
this
like
service
to
service
rollout.
Instead
of
this,
like
13
hour
roll
out
all
at
once.
B
A
C
I
think
yeah
I
think
having
a
service
to
service
rollout
goes
in
line
with
the
with
our
self-serve
approach,
which
we
are
actually
enabling
other
teams
to
do
the
rollout
themselves,
instead
of
us
being
the
ones
that
coordinate
everything
so
yeah
before
the
time
goes
goes
out.
I
do
have
another
question:
what
is
the
status
of
the
auto
deploy
package?
I
think
we
have
an
issue
there
onto.
B
Yes,
we
are
okay.
The
contents
of
oh
yeah,
yeah,.
B
Yeah,
so
there
hasn't
been
that
much
activity
on
that
side
since
about
a
week
ago,
two
weeks
ago,
actually
Let
me
show
my
screen
again
yeah
so.
C
A
B
To
test
the
cngs
compatible
with
Ruby,
3
and
yeah,
these
QA
runs
and
then
essentially,
the
merge
requests
in
order
to
merge
them
in.
C
I'm
working
on
that
one
yeah,
it
might
be
a
good
idea
to
also
give
them
a
friendly
thing,
like
hey
yeah,.
B
C
Perhaps
if
they
already
have
the
merch
request
ready
to
assign
them
to
us,
so
we
can
actually
close
this
issue.
B
C
B
Oh
I'm,
trying
to
run
a
QA
pipeline
using
this,
that's
the
one
that
I
was
looking
for.
I,
don't
know
how
he's
trying
to
do
this
should
I
ping
him
on
this
issue
or
on
this
Mr
I.
C
A
C
A
A
Things
are,
we
are
going
pretty
fast,
I'm
gonna,
take
care
of
the
quality
people
and
be
sure
that
your
eyes
are
up
to
speed
of
what
they
need
to
do
for
the
next
for
next
call
and
if
anything
extra
comes
up.
If
you
need
my
help
for
that,
please
ping
me
and
I'm
going
to
take
care
of
it,
but
looks
like
that.
We
have
a
lot
of
things.
We
are
still
some
open
things
to
solve,
but
more
or
less
we
are
there.