►
From YouTube: 2023-02-07 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
Okay,
awesome
so
I
guess
we
can
jump
in
into
the
notes
that
Jenny
left
the
first
one
is
about.
There
is
some
confirmation
on
some
manual
testing
needed
to
do
it
in
the
rollout
so
far
it
appears
that
there
is
only
one
group,
the
import
group
that
needs
to
do
some
manual
testing
regarding
Matrix
reporting
in
Canary
and
probably
also
in
production,
so
yeah
so
far
it
is
only
one
group,
so
that's
I
guess
it
is
good
news.
A
The
manual
testing
seems
to
be
to
a
minimum
and
I
think
Roger,
which
is
the
product
Managers
from
the
application
performance
at
Matthias,
which
is
the
main
dri
I
think
they
mentioned
that
we
should
go
forward
with
the
merge
of
the
PCL
yeah
because
of
this
jnx
has
has
finished
the
deployment
steps
so
yeah.
That
issue
is
closed
and
the
next
step
is
to
proceed
to
document
those
steps
into
the
change
requests.
So
yeah
awesome.
B
A
Yeah
I
think
she
is
coordinating
already
with
the
release
managers
for
1510
to
double
check
their
availabilities
and
the
duration
of
the
rollout
is
to
be
estimated
around
18
hours
so
far,
starting
early
in
emea,
at
the
beginning
of
the
of
the
day,
at
9,
UTC
and.
B
A
Early
in
Apache
at
around
12
40,
UTC,
yeah
and
she's
asking
if
we
can
have
the
PCL
Go
24
hours
from
nine
to
nine
I,
think
that
is
the
standard
right.
I
think
the
PCL
is
usually
starts
at
the
9
A.M
UTC
and
finishes
9
A.M
delay
later.
A
Yeah,
that
is
my
understanding
as
well.
Would.
A
I
was
checking
that,
where
is
it
yeah?
So
I'm
gonna
share
my
screen,
so
we
can
see
the
same
yes.
A
So
this
is
the
production
change,
lock
page
on
the
gitlab
handbook
report
and
well.
It
says
right
here
that
the
following
dates
are
currently
scheduled
pcl's
time
for
the
dates
begin
at
9,
00
am
UTC
on
the
on
that
day.
That
is
a
schedule
and
end
the
next
day
at
9,
00
am
UTC,
so
I
don't
think
we
need
to
modify
anything
on
the
merch
request,
which
is
this
one
I
think
if
we
add
like
this
is
the
day.
A
It
is
hard
that
should
account
for
9am
you'd,
say
OTC
on
March
7,
and
it
is
going
to
finish
on
9
A.M
UTC
on
March,
8th,
perfect.
A
Awesome
cool,
so,
regarding
that
merch
request,
we
have
all
the
approvals
we
have
Alan,
Marin
and
Steve.
So
I
will
proceed
to
merge.
It
and
I
am
going
to
prepare
the
announcements.
A
I
wrote
a
small
blurp
I,
don't
know
what
you
think
of
it.
Just
basically
saying
that
production
heart
production
change
log
has
been
set
for
that
day.
No
production
changes
are
going
to
be
allowed
from
this
period
and
well
I
am
going
to
share
it
on
what's
happening
with
love
with
love
and
then
using
startups
notify.
So
it
is
on
backhand
development
and
probably
be
in
all
of
those
and
other
people
building
engineering
week
review
perfect,
oh
yeah,
okay
and
then
I
guess
the
main
item
or
the
yeah.
B
A
B
B
B
A
Okay
cool,
so
do
you
have
any
questions
about
the
amount
or
the
PCL?
No
okay,
okay.
So
moving
on
to
point
number,
three
Jenny
mentions
that
we
have
been
solidifying
the
schedule
for
the
rollout,
like
the
broad
schedule,
not
only
the
PCL.
A
Yes,
so
with
the
assumption
that
the
PCL
is
happening
on
March
7,
we
have
been
discussing
executing
the
PDM
before
on
March
3rd
and
then
passing
out
the
deploys
at
the
beginning
of
our
time
zone
and
prepare
for
the
package
on
Monday
March
6th
yeah,
which
makes
sense
because
we
only
want
to
use
the
time
of
the
PCL
to
do
the
deployment.
We
don't
want
to
use
the
time
on
the
PCL
to
prepare
the
package,
which
is
around
one
hour,
so
yeah
I
think
we
can
do
that
on
the
day
before
yeah.
B
A
Awesome
so
one
thing
that
also
is
on
this
issue
about
defining
the
schedule
for
the
Ruby
tree
is
that
we
need
a
release.
Manager,
availability,
which
is
they
are
going
to
be
the
release
managers
for
1510,
yes,
15
10,
yes,
I,
guess
15
10,
and
it
might
be
also
a
good
idea
to
notify
the
people
that
are
going
to
be
on
call,
for
example,
the
SRE
on
call
or
the
quality
on
call.
A
We
are
going
to
need
them
to
be
like
available,
and
probably
we
are
going
to
also
need,
perhaps
people
from
distribution
in
case
something
goes
wrong
with
the
auto
deploy
package
which
I
hope
it
doesn't.
Yes,
they
will
need
to
be
aware
that
this
change
is
coming,
and
probably
we
will
have
some
volunteers.
A
Okay,
regarding
this
change,
now
I'm,
not
I,
discussed
this
with
Jenny
a
little
bit
but
I'm
not
sure.
How
do
you
imagine
the
day
of
the
rollout?
A
What
I
am
imagining
so
far
is
to
have
a
dedicated
slack
channel
for
this
rollout
without,
like
any
incident
like
with
us,
dedicated,
Zoom,
URL,
and
then
people
join
in
throughout
the
day.
Yes,.
B
A
B
Okay,
perfect,
so
this
one
one
question
about
this:
when
do
we
plan
to
do
executed,
release
before
this.
A
A
So
then,
the
fourth
point
is
that,
from
conversations
with
distribution
with
Baloo
on
the
issue
about
defining
the
content
of
the
auto
deploy
package,
it
seems
that
their
theme
has
been
created,
Mrs
to
switch
the
branch
bills
to
Ruby
3
on
CNG
and
Optimus
and
testing
the
package.
Accordingly,
they
are
also
going
to
create
they
have
to
deploy
branches
changes
to
switch
to
Ruby
tree
so
yeah.
This
issue
about
the
finding
the
auto
deploy
content
package
is
basically
on
them.
B
A
Yep
and
then
just
one
small
concern
that
I
brought
up
is
that
on
my
live
release
manager
shift,
we
had
problems
tagging
a
package
only
with
CNG
changes
for
some
reason
we
were
not
able
to
do
it,
so
we
needed
to
to
create
a
new
auto
deploy
branch
which
is
not
what
we
want
here.
I
just
want
to
make
sure
that
when
we
create
the
auto
deploy
package
that
is
only
going
to
contain
Omnibus
and
CNG
changes,
we
are
able
to
do
so.
B
B
B
Thank
you
for
doing
that
anything
else.
B
A
Will
be
this
one
with
pris
and
yeah
I
do
a
documents,
the
change
requests.
A
B
Okay,
perfect
I'm,
going
to
so
I
was
looking
now
at
the
schedule
of
the
next
meetings
of
this
one.
So
we
have
one
in
two
weeks.
Do
you
think
he's
a
too
far
do
we
want
to
have
it
next
week
or
I?
Think
it's
good
enough
for
now,
because
in
two
weeks
is
the
21st,
it's
okay,
the
one
after
will
be
the
seven,
but
the
parent
participated
one
of
the
seventh
to
the
week
before,
just
to
be
sure
that
we
have
everything
in
place.
A
Yeah,
that
is
a
good
point.
Well,
we
could
have
weekly
meetings
just
to
make
sure
that,
since
we
are
getting
closer,
we
can
switch
the
pace
to
be
a
weekly
one,
and
if
we
don't
have
anything,
we
can
just
cancel.
B
B
B
Okay,
perfect,
then,
thank
you
very
much
for
this.
If
it
is
anything
just
please
slack
me
and
try
to
jump
in
on
it
immediately.