►
From YouTube: 20200408 SIG Arch Prod Readiness
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
A
A
A
A
A
A
A
B
So
related
to
that
Pierre,
our
survey
that
we
sent
out,
we
did
go
ahead
and
merge
that
require
a
transition
from
beta
and
I,
am
now
working
on
some
cogeneration
and
verify
scripts
to
try
to
enforce
it.
Inside
of
our
code
during
when
PRS
are
open,
we'll
run
it
as
part
of
the
verify
jobs
and,
hopefully
add
sufficient
data
to
actually
enforce
it
inside
our
arrest
handler.
B
A
A
C
B
B
No,
no,
no
trips,
the
internet.
None
of
that
it
lets
us
do
things
like
you
know,
codify
the
transitions
that
Jordan
had
us
go
through
when
he
was
deprecating
and
removing
beta
api's.
Where
you
have
the
announced,
you're
deprecated
you're
gonna
get
a
warning
later
on.
I'm
gonna,
stop
serving
you
by
default.
You
can
turn
me
back
on,
but
by
default
is
no
longer
going
to
be
served
and
then
finally,
like
no,
you
just
can't
serve
this.
That's.
A
And
so
the
other
excuse
me,
I,
didn't
finish
going
through
this
list
and
figuring
out
I
wanted
to
go
back
through
the
document
we
had
a
few
in
the
beginning.
We
started
this
process.
We
had
a
number
of
efforts,
so
we
had
a
post-mortem
effort,
their
effectiveness
measures,
effort
and
then
we
had
the
field
research
to
the
field
research.
We
did
the
survey,
but
I
think
we
also
had
a
component
of
that.
A
That
was
going
to
be
more
of
a
interview
and
and
Valerie's
here,
I
see
so
I
believe
she's,
one
of
the
ones
who
signed
up
for
that,
or
at
least
so
we
did
collect
as
part
of
the
survey
a
bunch
of
people
who
said
they
were
interested
in
more
so
I.
Think
probably
what
we
would
want
to
do
is
kind
of
figure
out
what
we
want
to
learn
from
those
interviews
before
we
go
and
talk
to
people
and
so
Valerie.
D
A
Interested
okay,
so
I
guess
then
our
next
steps
on
that
are
to
probably
define
what
we
really
want
to
learn
from
in
it
and
make
sure
that
we're
not
wasting
people's
time.
I.
Think
that
there's
a
number
of
things
that
we
didn't
ask
well
in
the
survey
that
we
could
learn
through
these
interviews
like
when
you
had
to
roll
back.
A
A
B
B
Well,
we
need
to
figure
out
which
over
beta
api's
are
actually
being
treated
as
GA
and
end
up
in
the
situation,
where
beta
becomes
obvious
that
it's
beta
and
the
ones
they
need
to
get
promoted,
go
to
GA,
and
so
that
was
a
clear
outcome.
I'd
like
to
have
similar.
If
it
looks
like
this,
we
do
this
action.
If
it
looks
like
that,
we
do
that
action
right.
B
Well,
I'll
say
we
never
did
it
I
in
some
ways,
I
think
the
survey
results
are
better.
They
don't
have
as
many
specifics,
but
they
give
sort
of
the
situation
in
broader
strokes,
as
perceived
by
people
who
are
not
just
like
have
a
bajillion
clusters
right,
as
we
noted
in
the
survey
results.
Basically,
once
you
get
past
a
certain
threshold
and
terms
of
managed
nodes,
a
number
of
clusters
you've
seen
all
the
problems.