►
From YouTube: 20221102 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
So
maybe
people
are
busy
with
that,
but
so
we'll
try
and
make
it
quick
I
see
we
have
a
couple
new
folks,
ashwaria
I,
believe
we
met
in
cubecon
in
Detroit.
A
B
A
Awesome
welcome
and
deepanshu
is
that
how
I
say
it.
C
A
Okay,
so
the
way
things
work
here
with
production
are
uses,
it
tends
to
be
pretty
quiet
except
for
the
month
or
so
before,
code
freeze,
that's
when
we
have
a
lot
of
reviews
to
do,
but
today
I
did
want
to
take
some
time
and
do
a
little
retrospective
on
on
the
last
review
last
period,
Let
me
show
the.
A
A
Sometimes
I
used
to
when
Zoom
share.
Sometimes
it
shares
the
tab,
okay,
cool.
So
from
my
point
of
view,
things
went
pretty
well
I'll
just
put
myself
in
there.
A
D
I
thought
that
the
the
new
project
board
was
the
single
best
Improvement
we've
had
in
the
last
three
releases.
That
was
really
big.
D
I
thought
that
it
was
not
ideal
that
we
were
able
to
manipulate
that
project
board
to
like
remove
entire
columns.
Remember
voytech
had
an
incident
I
had
one
incident
that
wasn't
awesome.
Yeah
I
thought
that
the
help
that
I
got
from
the
Shadows
was
actually
quite
good.
D
You
know
they
were
able
to
go
through.
Take
first
passes.
The
results
were
good
I,
don't
know
how
they
felt
about
the
the
process
that
we
tried,
so
I'm
interested
the
only
one
I
think
who
was
there
with
me
was
Han,
but
but
whether
the
the
here's,
your
training
watch
us
through
this
once
now,
could
you
please
practice
on
these
two
PRS
and
we'll
go
over
it,
whether
that
approach
was
good
or
not,
or
whether
you
could
do
something
better?
Is
feedback?
I
would
like
to
hear
here.
A
Yeah
so
so
I'll,
let
Hans
speak
in
a
second,
but
but
Han
and
Joe
Betts
and
I
had
lunch
the
last
day
of
qcon
and
Joe
mentioned,
and
you
since
he's
not
here.
He
mentioned
that
you
know
he'd
like
to
do
it
reverse
Shadow
next
time,
so
like
let
the
sh
let
the
Shadows
just
do
their
thing
and
then
we
we,
which
is
kind
of
sort
of
what
we
did
but
I,
didn't
feel
like
the
volume
was
enough
for
the
number
of
Shadows
we
had
I.
A
Think
I,
guess
is
what
I
would
say.
The
Shadows
help
was
valuable
as
well,
but
but
I
felt
like
we
have
a
lot.
We
have
a
lot
of
channels
and
Men.
Each
chat
only
got
to
do
a
little
bit.
There's
no
reason
why
Shadows
shouldn't
multiple
Shadows
shouldn't
be
able
to
do
the
same.
A
The
same
PR,
maybe
the
same
cap,
foreign.
C
Well,
you
know:
I
I
had
like
I
think
we
were
assigned
like
a
decent
percentage
of
I.
Think
I
was
ascended
like
a
percentage
of
David's
caps
and
they
were
yeah
I
mean
it
was
like
10
or
12,
or
something
I
thought
it
was
a
decent
number
to
start
off
with,
but
yeah
I
think
Weaver
shadowing
should
be
helpful,
I
I
liked
what
we
did.
I,
don't
see.
C
A
It
was
helpful,
I
would
like
feedback
on
whether
it
was
useful
to
you
and
and
whether
you
saw
something
David
did
that.
Maybe
I
should
do
next
time.
C
No,
there
were
a
similar
I.
Think,
okay,
I
think
the
speed
like
I
think
we
went
through
more
caps
with
David,
but
I
went
to
more
of
David
sessions,
so
that
could
be
it
too.
Okay,.
A
All
right
so
then,
just
for
the
new
folks
here
essentially
give
a
very
high
level
overview
right.
We,
as
caps,
are
proposed
for
the
release.
A
They
are
there's
a
handful
of
questions
on
the
cap
that
are
around
production
readiness,
and
there
are
a
few
of
us
that
can
approve
the
answers
to
those
and
what
that
means
is
we
review
their
answers.
We
make
sure
that
their
plans
and
their
designs
are
in
line
with
what
we
would
expect
to
make
the
features
supportable
and
and
safe,
and
because
there
are
something
on
the
order
of
80
caps
per
cycle,
and
there
are
only
a
few
of
us
that
approve
them.
A
It
can
get
a
little
bit
hectic
those
couple
of
weeks
so
we're
trying
to
bring
more
folks
onto
the
team
which
is
likely
why
you're
here,
and
so
we
did
a
shadowing
process
last
time
where
David
and
I
so
we
had
one.
We
have
one
other
man
active,
approver
voice
check,
but
he
was
out
I
think
he's
out
all
the
way
through
the
end
of
this
year,
and
so
he
was
out
for
the
last
cycle.
A
So,
although
he
did
a
bunch
of
stuff,
even
though
he
wasn't
technically
working
but
anyway,
so
David
and
I
held
these
sessions
where
folks
came
and
we
just
went
through,
and
this
is
how
we
do
the
review.
This
is
the
kind
of
thing
we
think
about
as
we
read
these
questions
and
these
answers
and
then
what
we're
talking
about
doing
next
time
is
reverse
shadowing,
where
the
the
shadow
would
lead
the
review
and
go
through
and
say:
okay,
here's
what
I
think
about
this!
A
Here's,
what
I
think
about
this
and
then
I,
guess,
David
or
I,
would
give
feedback
on
that
is
that
that
match
with
what
you're
thinking
of
as
reverse
shadowing
on
and
then
yeah
Jeremy?
We
are
just
doing
a
retrospective
and
I
would
love
to
hear
from
you
on
how
you
thought
the
shadowing
process
worked
for
you
as
a
shadow
and
then,
if
you
went
to
both
mine
and
David's
shadowing
sessions,
whether
there's
things
each
of
us
could
learn
from
the
other
in
that
process.
E
Cool,
hey,
I
only
went
to
yours,
I
think
it
was
really
useful
to
be
able
to
sit
through
a
couple
with
you
and
okay,
just
kind
of
see
what
you
were
looking
at
I
think
towards
the
end.
I
reviewed
a
couple
of
myself
and
left
comments
and
you
agreed
a
couple
of
them
and
disagreed
with
a
couple
of
them
right.
E
I,
think
part
of
it
is
doing
it
a
few
more
times
and
having
just
like
the
the
iTune
to
that
so
I
plan
on
asking
a
shadow
again
and
I
think
doing
reverse
shadowing
would
be
cool
just
to
force
me
to
do
a
few
more
right.
Then
I
did
this
time.
Okay,.
A
All
right
sounds
good,
any
other
retrospective
comments
from
folks.
D
Yeah
I
have
one
one
thing:
I
noticed
going
through
this
time
was
I
thought
I
had
many
more
caps
staying
in
the
same
maturity
level
where
they
were
staying
in
Alpha
staying
in
beta
and
I
was
wondering
if
the
release
team
tracked
that
anywhere,
whether
we
should
track
that
somewhere,
not
specifically
for
project
Readiness
or
production
Readiness.
But
it's.
A
E
E
So
there
were
cases
like
that
in
the
past,
I,
don't
know
how
that's
been
reflected
in
the
new
tracking
GitHub
project
board.
I
can
take
a
look
at
that
and
see.
If
that's
a
thing
we
can
identify
better,
would
you
prefer
to
not
have
reviews
for
those
or.
E
D
E
Think
it's
always
been
that
way
to
a
point,
mostly
for
things
that
are
making
significant
changes
within
a
stage
because
things
don't
typically
go
back
like
they
won't
go
from
beta
Alpha
they'll,
just
like
here's,
a
new
version
of
the
beta
here's,
a
new
version
of
the
beta
okay.
D
A
That's
fine,
so
so
one
thing
I
do
wonder
about
along
those
lines,
and
this
is
maybe
the
right
group
but
Jeremy,
you
might
have
some
insight.
So
we
have
a
very,
very
I
I
keep
harping
on
this
because
nothing
seems
to
be
happening.
We
have
a
very,
very,
very
tiny
group
of
people
that
can
approve
apis,
David,
I,
believe
you're,
one
of
them
it's
Clayton
and
you
and
Tim
and
Jordan.
So
it's
all
three
googlers
and
you.
D
Those
to
other
people
so
oops,
you
don't
have
to
look
it
up,
live
I'll.
Look
it
up
later
and
someone
will
replay
this.
A
D
A
Sorry
I
think
it's
Maybe.
A
D
A
It
is
all
good
verse
yeah
that
you
should,
you
should
go.
You
should
do
whatever
you
need
to
do.
Mr
Eads,
because
I
I,
that's
not
healthy,
I
mean
I'm
from
Google.
It's
great
for
me.
Right
I,
don't
think
it's
healthy
for
us
as
a
community,
so
yeah,
okay,
I've
been
telling
people
wrong.
I've
been
saying
it's
three
googlers
and
you
I
I
didn't
think
Daniel
was
in
there
for
some
reason,
but
he
is
okay,
so
so
I
kind
of
Wonder.
The
reason
I
brought
that
up
is
I.
A
Wonder
if
you
know
that's
a
that's
a
narrow
number
of
people
to
do
an
important
blocking
task
and,
and
those
tend
to
become
design
reviews,
not
just
API
reviews,
often
too
so
I
wonder
if
there's
just
not
enough
bandwidth
on
those
that
small
number
of
people
for
that
moment
where
people
to
get
changes
through.
So
it's
something
I
think
we
probably
we
should.
Maybe
somebody
to
release
team
can
investigate
a
little
bit
or
at
least.
E
Having
done
tracking
of
enhancements
for
a
few
releases,
that
does
become
a
bottleneck
towards
the
end,
and
there
are
things
that
will
not
make
code
freeze
or
not
make
wherever
they
need
to
get
to
because
they're
waiting
for
API
reviews.
And
they
just
wait
too
long
to
ask
for
them
and
like
the.
A
A
To
let
you
know
like
like
Tim
is
working
on
trying
to
help
bring
more
people.
You
know,
but
but
right
now
it's
an
internal
thing
and
he
hopes
to
bring
it
to
the
community
if
it
works
well,
but
like
we
really
should
do.
I'm
hoping
somebody
from
red,
hat
or
VMware
I
mean
VMware.
I
know
things
are
we
don't
know
where
things
are
going,
but
you
know
from
other
places,
could
could
try
to
I
mean
it
takes
it's
going
to
take
a
year
right,
at
least
so
yeah
anyway.