►
From YouTube: 2023-02-21 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).
B
Yeah
our
Ruby
three
rollout
today
is
February
21st,
so
we
decided
to
do
this
Ruby
three
rollout
meeting
every
week,
since
the
rollout
is
coming
out
pretty
soon
so
yeah
I
just
wanted
to
touch
on
the
overall
epic
have
a
bunch
of
things
wrapped
up.
So
first
one
is
the
change
request.
It
is
currently
out
of
the
draft
phase.
B
B
I
want
to
ask
now
I
think
I,
don't
know
what
to
do
for
those
steps
to
verify
the
change
part.
I
think
this
is
just
the
generic
one
when
it
was
created
a
year
ago,
but
we
can
discuss
it
further
on
this
issue.
I
believe
my
main.
C
B
Today
is
for
us
to
determine
the
technician
and
the
reviewer
like.
Would
the
technician
be
our
like.
A
B
Cool
and
the
change,
reviewer
I'm,
not
sure
I'm,
not
sure
who
this
should
be
or
someone
from
our
team
or
application
performance
or.
C
B
Okay,
right
and
okay
I'll
do
the
labels
after
this
call,
but
so.
A
For
the
reviewer
we
need
someone
that
is
actually
reviewing
that
the
plan
is
technically
sound
and
since
this
is
impacting
like
multiple
people
will
need,
I
would
say.
I
would
begin
to
have
this
reviewed
by
the
Rivera
series
and
someone
from
I
don't
know.
Matthias
Kepler
as
well
or
whatever
is
at
your
iPhone
is
a
little
bit
on
their
side
and.
B
A
Manage
area
will
have
only
to
give
the
approval,
or
that
is
approving
this
change
request
more
than
reviewing
it,
but
we
will
manage
it.
We
review
when
he
thinks
that
all
the
things
are
like
in
line
and
we
have
like
all
the
fields
needed.
We
have
a
proper
plan
for
rollout
program
for
our
back
that
we
have
in
the
right
metrics
listed
on
the
change
request,
so
there's
gonna
be
like
I
I'm.
A
Quite
sure
that,
in
this
change
request
like
this
there's
gonna
be
a
lot
of
back
and
forth
any
issues
and
comments.
So
what
I'm
asking
you?
If
let's
get
this
to
the
the
most
ready
data
we
can
get
this
week
going,
we
can
start
to
bring
people
around
and
to
have
a
full
review
of
that
with
everybody.
Yeah.
A
A
I
think
the
downtown
components
it's
if
you
are
going
to
be
down
for
a
certain
period
of
time
because
of
the
change
I,
don't
know
as
an
example.
Let's
say
we
need
to
do
one
update
on
our
critical
part
about
infrastructure
that
we
cannot
do
like
an
upgrade
or
like
switching
traffic
or
anything
like
that.
We
need
to
go
really
offline,
so
I
mean
like
a
moment
where
you
say
Okay.
A
git
Club
is
not
going
to
be
available
for
from
this
time
to
this
time
for
maintenance.
B
B
So
this
is
mostly
to
keep
track
of
being
able
to
test.
If
the
auto
deploy
package
can
roll
with
Ruby
three
now
we've
had
a
bunch
of
back
and
forth,
with
Balu
from
distribution
and
I.
Believe
that's
in
this
thread,
I
linked
it
in
the
dock,
but
so
there
is
a
bunch
of
issues
that
Mrs
mentioned
from
Balu.
B
In
this
thread
there
hasn't
been
any
updates
since,
like
two
weeks
ago,
so
I
have
pinged
him
again
today
and
yeah
I
would
I
would
like
to
kind
of
have
an
expectation
of
when
we'd
be
expecting
some
of
these
steps.
So
he
said
you
know
we're
gonna
switch.
The
French
builds,
probably
testing
involved
here,
open
the
Mrs
double
switch
Auto
deploy,
builds
to
Ruby
three
and
on
Anonymous
and
CNG,
and
this
is
the
one
that
we're
essentially
waiting
for
on
the
day
searching
all
build,
including
public
release.
B
C
Three
things
from
distribution:
first,
that
they
confirmed
that
CNG
is
going
to
be
compatible
with
Ruby
tree.
Yes,
that
they
execute
the
Q
a
on
both
packages,
Omnibus
and
CNG,
and
the
merge
request
to
update.
A
A
That
because
I
think,
as
this
I
think
somebody
said
that
is
on
video
right,
yeah,
so
I'm
gonna
ping
Vijay
on
that,
because
we
need
attention
to
that
part.
Yes
and
we
see
where
we
get.
Let's
fix,
maybe
the
the
XC
criteria
for
delivery.
So
we
know
that
we
need
to
Market.
A
B
B
Yeah
and
on
top
of
that
I'm
gonna
move
on
to
the
DIY
timetable.
If
you
could
ask
DJ
for
the
distribution
team's
availability,
I
have
ping
them
I,
don't
believe
they
have
seen
it
yet
or
something.
So
if
you
can
just
confirm
that,
for
us,
that'll
be
great.
A
B
The
conversation
and
other
than
that
Quality
team,
they
have
gotten
back
to
me
saying
that
there
is
this
pipeline
triage,
dri
schedule.
B
C
B
They're
going
to,
they
said
they're
going
to
be
editing
the
timetable
as
appropriate,
so
I'm
just
going
to
keep
an
eye
on
that
throughout
this
week,
but
I
think
that's
covered.
B
C
B
C
Could
you
also
make
sure
that
they
know
the
responsibilities
as
a
quality
on
call?
In
this
case,
there
are
two
scenarios
that
they
need
to
check
the
pipelines
are
in
and
they
also
need
to
trigger
the
Q,
a
suite
that
has
been
discussed.
Yes,
so
they
are
aware
of
the
expectations
of
that
day.
Yeah.
B
A
B
As
I
update
the
timetable
and
then
other
than
that,
one
more
concern
is
that
application.
Dri
team
does
not
seem
to
have
any
coverage
in
the
American
time
zone.
B
C
Yeah
I
think
we
can
pull
the
pressure
back
on
them
because
we
need
to
have
someone
to
help
us
enamor
most
likely
because
Cannery
and
production
are
going
to
be
executed
into
the
during
the
American
time.
So
we
need
someone
to
tell
us
hey.
This
is
okay,
we
can.
We
can
continue
to
production
and
then
production.
We
need
to
confirmation.
So
perhaps
they
can
train
someone
from
another
team
to
be
available
or.
A
I
need
to
take
care
of
this
I'm
gonna
I'm
gonna
follow
up
with
them.
Okay,.
B
Awesome
that
sounds
good
all
right,
oh
yeah,
one
last
thing:
we
have
another
issue
on
Logistics,
just
an
issue
to
keep
track
of.
B
You
know,
updating
the
release,
issue,
I,
think
it
comes
out
tomorrow
and
then
Ruby,
three
rollout
stock
Channel,
creating
those
like
Zoom
rooms,
those
the
logistics
just
so
that
we
don't
forget
but
yeah.
If
you
can
think
of
any
other
considerations
or
exit
criterias,
that
we
should
be
keeping
track
of.
Let
me
know.
A
Is
mandatory
and
I
think
the
most
important
thing
for
me
right
now?
If
you
start
to
have
that
change
request
the
best
days,
we
can
get
it
yeah,
so
we
can
just
send
it
around
multiple
people
for
review
and
have
like
even
multiple
approval.
Yeah,
that's
right!
Yeah
he's
not
I,
don't
want
to
be
the
only
one
saying
yes,
I
want
to
able
to
some
other
liability.
Saying
yes,
I
want
to
have
Marty
to
say
yes
as
well.
I
just
want
to
be
sure
that
we
have
multiple
eyes,
because
this
is
a
big
change.
Yeah.
B
A
It
is
tomorrow,
so.
A
Yeah,
let's
do
something:
let's,
let's
put
it
right
now,
in
the
best
ship
we
can
I'm
gonna.
Give
it
a
look
tomorrow
morning
at
this
point,
for
me
yeah
as
a
my
is
priority
in
the
morning,
so
I
can.
If
I
have
any
comments
we
can
address
them
when
we
think
that
for
me-
and
you
is
in
a
good
shape
that
we
can
start
to
Ping,
we
can
start
to
Ping
people.
Let's.
A
No
so
on
my
on
my
to-do
list
distribution,
the
arrival
ability
for
that
just
between
DJ
replacing
value
at
least
having
someone
to
swiping
for
for
Value,
since
it's
not
available
right
now,
and
they
allows
me
to
the
comment:
I
want
to
double
check
with
QA
to
be
sure
that
that
list
is
the
latest
and
greatest,
and
so
we
can
actually
at
this
point,
make
sure
that
people,
the
right
people
know
what
they
have
to
do
because
right
now
you
know
I,
don't
know
until
last
week
when
we
spoke,
we
entered
this
schedule
really
well
defined.
A
So
we
didn't
know
what
to
train
for
that
and
then
I'm
going
to
find
application
performance
there
I
do
in
American
time
zone
or
someone
that
can
cover
for
them
during
the
American
time
zone
or
loud
Android
in
the
production,
CR
anything
else
a
desired
priority.
You
might
need
from
me
Johnny.
C
No
I,
don't
think
so,
I
think
yes,
the
most
important
things
will
be
to
have
the
change
request
as
ready
as
possible
and
to
also
have
the
Aris
defined.
And
yes,
one
thing
that
I
will
suggest
is
that,
once
we
have
all
the
dris
to
send
the
invitation
for
that
date
for
the
zoom
calendar
or
whatever,
and
to
let
them
know
about
all
the
logistics
that
they
should
be
able
to
join
the
channel,
etc,
etc.
Perfect.