►
From YouTube: 20200506 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
All
right,
thank
you,
everybody.
This
is
production,
readiness,
so
project
of
architecture,
meeting
for
May,
6th
2020,
and
we
have
velocity
short
agenda
I.
Think
so
few
things
I
wanted
to
talk
about
did
update
the
template
based
on
basically
I
wrote
last
week
two
weeks
ago,
feedback
and
that's
it
sleazy
consensus
time
out
now.
So,
if
nobody
complains
about
it,
then
we
should
merge
that
tomorrow,
at
noon,
I,
don't
think
we're
gonna
get
any
complaints.
Concern
I
think
was
one
comment
and
I
checked
handled
it.
B
A
A
C
A
C
In
a
in
my
perfect
world,
I
would
have
a
query
that
said
these
are
the
things
that
are
targeted
for
GA
and
119
that
do
not
have
these
things
inside
the
okay
and
I.
Don't
know
how
to
I.
Don't
think,
that's
a
thing
we
can
do
from
github,
but
maybe
it
is,
and
it
made
me
think
about
Tim's
like
I,
can
really
see
like.
Let's
do
this.
A
Yeah,
so
so
we
have
actually
mean
this
is
finally
talked
about
here,
so
totally
separate.
Now
you
know
that
enhancement,
sub
project,
which
was
part
of
big
PM,
is
now
in
cig
architecture.
What
actively
kind
of
started
you
work
on
trying
to
include
this
tooling.
So
definitely
that's
something
we
can
add
the
cap
tooling
and
subsea
either
on
it,
but
basically
we
flip
this
stuff
in
the
metadata
so
that
we
can
do
that.
But
you
want
to.
A
A
A
B
C
A
C
A
That
there
already
that
starts
to
look
at
mine,
but
we
need
to
put
down
all
those
uses.
So
this
would
be
one
use
case,
Olivia's
cases
and
what
we're
trying
to
do
with
the
kept
reading
group.
Let's
try
to
discover
things
that
a
lot.
What
are
the
criteria
and
how
do
you
flag,
those
I,
don't
know
but
like
discoverability
and
the
management
of
these
things.
A
C
C
B
C
B
A
A
That
tracks
all
the
different
caps
that
are
being
potentially
targeted
to
119,
but
most
of
these
won't
get
swept
out
of
here,
but
at
some
point
we
will
have
a
list
of
specific
caps
and
they
should
be
marked.
As
you
know,
nineteen
now
this
doesn't
tell
us
which
ones
meet
here
are
like
this
is,
if
there's
any
list
anywhere
that
can
give
you
an
idea
of
that.
It's
this,
but.
A
So
the
river,
then
he
had
Spence
team
on
the
relief
team.
Basically,
we
divided
up
come
on
this
cycle
team.
Basically,
we
divided
up
he's
and
then
we
iterate
for
you
and
talk
to
the
different
authors
of
each
different
tap
and
try
to
get
whether
they're
planning
on
delivering
something
in
this
coming
or
not,
and
then
make
sure
that,
if
they're
planning
on
delivering
something
in
the
release
that
they've
met
certain
criteria,
you
know
this
is
where
we
would
add
a
PR.
A
Our
needs
to
be
in
this
acceptance
criteria,
and
then
that
would
become
part
of
the
enhancements
release
team
to
go
through
and
people
question
is
when,
when
are
we
gonna
require
that
these
criteria,
in
order
to
moved
implementable,
State,
and
so
it
would
be
included
in
the
release?
Those
need
to
be
done
said
in
the
next
two
weeks
by
by
the
people
and
what
we've
said
I
think
in
1620
is
basically
yeah.
A
C
A
A
Yeah
and
not
even
just
in
the
mouth,
all
the
issues
in
the
enhancements
we
both
that
are
still
open
and
then
we
go
through
and
how
do
people
to
find
out
whether
they
should
be
included,
and
so
it's
a
it's
an
iterative
process
right.
It
takes
time
so
in
actually
looks
like
there
are
about
38
of
them
that
actually
made
it
in.
C
A
A
C
A
Yeah
they
get
the
go,
the
status
goes
from
like
it
can
be
pending
inclusion.
Basically
that
means
we
don't
know
yet
we're
gonna,
look
it
about
the
people
and
either
we
get
no
response
or
we
did
response,
and
they
say
you
know
nothing
in
this
time
can
be
deferred,
which
means
nothing
in
this
release,
but
the
next
release
may
be
well.
It
can
be.
A
Just
contract,
meaning
we
don't
know
when
we're
gonna,
deliver
it
or
it
can
go
to
tract,
which
means
it's
part
of
this
release
pending
and
having
the
milestone
and
and
then
that's
when
we
sort
of
actively
make
sure
people
need
the
code.
Freeze,
make
sure
people
meet
the
docs,
freeze,
etcetera,
etcetera,
so
becomes
our
search
process.
Do.
A
B
C
A
So
what
you'll
see
is
there's
some
scripts
and
things
you'll
see
a
bunch
of
these.
When
occasionally
somebody
will
run
the
script
and
it'll
pull
all
these
things.
That's
the
on-track,
whatever
it'll
just
disappear
off
in
here
any
that
are
green
right
now,
you'll
see
like
okay,
here's
you
know,
support
CRI
computer,
be
on
Windows
trap,
graduating
its
graduating.
The
beta.
C
I'll
work
that
out
separately
you're
on
the
release
team.
C
A
A
Anyway,
so
so
yeah
part
of
the
reason
I'm
I
intentionally
wanted
to
be
in
the
enhancements
team
I
was
in
at
118
in
19.
Well,
was
because
of
a
PR.
Our
stuff
and
I
saw
it
as
being
part
of
flowing
into
this
process
is
just
managing
that
so
I
wanted
to
make
sure
that
no
one
of
the
Samanas
team
is
to
make
sure
that.
A
B
A
A
Why
don't
we
just
in
the
channel?
If
you
decide
you
want
to
review
one
of
these,
just
grab
it
and
let
people
know
in
the
channel,
so
people
don't
do
the
same
one,
but
like
right
now
nobody
has
filled
out
those
things
so
part
of
what
I'm
gonna
have
to
do
as
part
of
this
team
and
other
people
on
this
team
is
we're.
Gonna
start
coming
down.
People
before
enhancements
treats
so
once
the
16
pony
merges
tomorrow,
then
we
can
start
saying:
hey
this
just
merged
it's
a
new
requirement.