►
From YouTube: Weekly Kubernetes 1.18 Release Team Meeting for 20200224
Description
Weekly Kubernetes 1.18 Release Team Meeting for 2/24/2020
A
Hello
everyone
good
morning
evening
and
afternoon,
depending
on
whatever
you
are,
welcome
to
it
yet
another
meaning
for
the
kubernetes
1:18
release.
I
am
my
name,
is
Jorge
I.
Am
the
release
team
lead
for
1:18
and
before
we
get
started,
I
want
to
remind
everyone
that
we
are
now
the
coronaries
community
has
that
code
of
conduct,
which
essentially
boils
down
to
please
be
nice
to
each
other,
no
be
a
jerk,
and
with
that
let's
get
started,
doing
cool
open
source
settings
and
actually
before
we
go
into
enhancements.
A
B
B
So
with
that
in
mind,
the
other
thing
to
really
report
is
that
since
we're
getting
close
to
coach
Frese,
we're
monitoring
things
for
getting
PRS
merged
and
right
now
about
half
of
the
48
things
around
20
have
PRS
that
are
open
still,
which
isn't
really
unusual.
From
last
release.
It
seems
there
was
a
lot
of
stuff
that
happened
in
the
last
two
weeks.
Prs
are
open.
A
lot
of
them
are
in
review.
People
are
working
through
comments.
B
A
good
number
of
them
also
like
pretty
close
to
they're,
just
looking
for
approves
so
we've
gone
through
and
marked
all
of
those
things
as
at
risk
and
the
enhancements
tracking
spreadsheet
I
think
the
next
milestone
is
the
docks
PR
placeholder,
my
deadline,
which
is
it's
28,
I,
think
so
we'll
revisit
the
number
of
issues
that
if
people
haven't
gotten
docks,
placeholders
open,
but
for
now
that's
the
the
status
of
twenty
things.
As
is
this
morning,
we're
still
waiting
PR,
merge.
A
C
C
A
A
Okay:
sweet
with
that.
Thank
you
very
much
for
your
comment,
Stephen
and
Jeremy.
Thank
you
very
much
for
all
the
work
that
you
and
your
team
have
been
doing
and
let's
move
on
to
CI
signal.
I
believe
that
Nikko
mentioned
that
he
wasn't
going
to
be
available
with.
Is
anyone
from
a
cell
signal
here
around
I.
A
Okay,
so
let
me
go
through
the
update,
so
notable
events
led
me
a
little
check
master
blocking,
really
quick.
So
we
have
a
skew
cluster
latest
cube
kernel
stable
one
GCE
that
is
actively
failing
and
you
see
cost
master
default.
That's
flaking,
let's
start
with
cosmos
to
default,
since
someone
is
closer
to
the
what
a
what
is
actually
been
test
on
the
blocking
piece
of
meat
for
kubernetes
kubernetes,
and
it
seems
one
of
the
latest
France
a
fail
to
actually
create
a
cluster
put
other
than
that.
Nothing
in
particular
seems
worrisome.
A
A
skew
cluster
latest
cube.
Coral
talent
has
been
failing
for
a
while
and
I
believe.
I
need
to
actually
check
in
with
say
signal
on
this,
and
let
me
add
a
note
about
down
the
meeting
notes
that
one
is
under
investigation.
Well,
okay,
that
one
is
already
in
the
meeting
notes.
I
think
this
might
be
somewhat
related
to
one
a
infrastructure
change
that
was
made
by
sick
testing
last
week,
I.
C
A
A
D
For
sure
so,
yeah
Steven
touched
on
that
the
change
with
the
workload
identity
affected
a
lot
of
the
jobs,
so
we're
still
kind
of
recovering
from
that,
which
is
why
you'll
see
the
volume
of
failing
right
now
and
why
we're
in
the
red.
Most
of
these
others
are
ones
that
have
been
like
triaged
and
someone
is
working
on,
and
so
there
aren't
any
that
are
of
too
much
concern
but,
for
instance,
like
the
GC
windows
container
d,
one
that
one's
been
on
here
for
quite
a
while,
and
that
is
related
to
a
test.
D
D
Think
we
really
got
anywhere
but
well
I.
Don't
think
that
we
want
to
bring
in
any
new
work-in-progress
ones,
but
since
this
one
is
already
here,
it
is
like,
should
we
actually
remove
it
and
so
I
don't
know?
The
last
follow-up
was
on
January,
21st
and
well
actually
Nikolas
responded
seven
days
ago
and
we
have
gotten
an
update
there.
So
it
may
be
time
to
think
about
moving
this
out
of
the
board
yeah.
D
D
D
A
A
Sweet
I'm,
looking
at
1
ATM
right
now
seems
to
be
the
skewed
cluster,
keep
coral
again,
so
it's
a
probably
related
to
master
Oh
other
than
that
so
I
guess
big
things.
Delta
features
one
way
we
can
investigate
that
one
is
synchronously.
The
other
thing
that
I
wanted
to
mention.
You
mentioned
that
there
was
some
discussion
with
the
windows
contain
a
container
the
issue,
whether
it
should
be
added
to
a
informing
or
not.
It's
been
a
while
since
I.
Actually,
since
I
went
through
the
documentation
for
blocking
test
on
sick
release.
A
A
C
A
A
F
C
C
No
okay,
so
yeah,
so
there's
a
kept
open
for
for
the
HT
triage
workflow,
so
we're
talking
about
adding
some
bits
into
that
to
help
make
it
easier
to
triage
issues
and
PRS
across
kubernetes
kubernetes
to
start.
So,
if
you
have
interest,
please
take
a
look
at
that.
It's
popping
it
in
the
notes.
Right
now.
H
Hello,
everyone,
so
the
docs
update
for
today's
the
current
status
seems
to
be
alerted
l,
so
we
have
a
deadline
in
less
than
three
days,
which
is
on
February
28
dogs,
placeholder
PR
deadline,
so
the
total
enhancements,
as
of
today,
is
49,
so
we
had
50,
but
one
was
removed
out
of
the
milestone
and
needs
dogs
like
we
have
31
and
enhancements
who
confirmed
that
they'll.
They
need
dogs
for
the
new
enhancements
and
placeholder
P
as
in
place
our
16.
So
we
have
Delta
of
15
PS
which
need
to
be
placed
in
place.
H
So
we
have.
We
are
positive
about
this
50
enhancements
as
the
enhancements
owners
are
like
we'll
put
them
like
bye
end
of
today
or
tomorrow,
and
we
have
eight
unknown
enhancements
like
we
reached
out
to
them
twice,
but
we
didn't
receive
any
response
back
so
from
today
we
will
be
reaching
out
to
them
in
person
and
slack
and
if
needed,
we
will
also
reach
out
to
the
respective
six.
So
this
is
the
status
of
dogs.
Today,.
A
I
J
I
Then
the
other
was
a
discussion
on
dumping,
the
Jason
release
notes
into
into
a
TCP
bucket.
We
didn't
want
to
do
further
work
into
that
one,
because
we
were
pending
on
saying
if
we
were
going
to
go
the
the
include
if
we
were
going
to
the
bucket
or
not
I
linked
the
issue
on
the
on
the
agenda
right
now.
So
what's
to
say
about
that
I
think
Stephen
you
were,
you
were
going
to
see
into
that
right.
Yeah.
C
Yeah,
so
the
bucket
should
be
easy
to
do.
I
just
wanted
to
see
some
of
the
stuff
move
a
little
further
along,
but
now
that
implementations
there
I'll
step
back
into
that
issue,
I'm
wondering
is
there:
do
we
think,
there's
a
need
for
an
additional
bot
to
do
some
of
this
stuff
Sasha
like
a
gates,
release,
notes,
pod
or
something
no
I'm,
not
terribly
concerned
about
the
API
call
limit,
but
just
a
little
bit
I.
J
G
One
more
question:
Sasha
and
Stephen:
have
we
thought
again
about
as
we're
getting
close
to
RC?
We
need
to
start
putting
together
the
final
release,
notes,
template
and
markup
file,
and
in
the
past
there
was
a
there
was
a
template
or
in
that
release,
notes
folder
and
now
that
where
we
move
to
the
kind,
that's
all
changed.
So
have
we
looked
at
that
again
or
how
do
we
want
to
attack
it?
G
C
C
G
C
C
G
What
I'll
do
is
I'll
do
a
PR
on
that
issue,
so
that
way,
there's
a
diff
on
the
new
template
versus
the
old
template
and
everyone
can
see
what
the
changes
are.
And
then
you
know
determine
what
we
want
to
add
or
remove
from
there,
so
that
we
have
the
new
template
with
it's
it's
organized
by
kind
instead
of
by
sig,
and
then
we
can
kind
of
organize
perfect.
C
C
Potentially,
the
only
way,
the
only
reason,
I
know
that
is
I-
think
that
once
we
did
manual
changes
to
the
both
the
template
that
we
send
out
in
announcements
as
well
as
the
the
existing
change
logs
it,
it
provides
like
a
double
a
double
header,
so
it's
like
like
changes
and
then
changes
by
kind
and
they're,
both
second
header
indented
or
something
it's
it's
a
formatting
thing.
It's
it's
a
small
thing,
but
it's
a
formatting.
F
H
A
K
All
right,
this
is
Paul
I'm
filling
in
for
Karen
shoe,
who
got
a
unexpected
visit
from
a
plumber
during
our
meeting,
so
I'll
be
reading
off
the
notes,
so
we've
recently
finished
working
with
Jorge
to
reach
out
to
most
SIG's
we're
waiting
on
one
last
one.
So
whoever
you
are
out
there
we'll
be
in
touch
shortly.
A
A
L
Thanks
George,
two
quick
updates
for
me:
I,
have
the
mid,
mid
review
her
mid
release
shadow
survey
ready
to
send
out
so
I'll
send
that
out
today.
So
if
you're,
a
shadow
keep
an
eye
out
for
that,
it
should
take
you
about
two
minutes
to
complete
and
your
completion
would
be
much
obliged.
Thank
you
very
much,
and
the
other
piece
is
I'm
going
to
be
ramping
up.
Pinging
everybody
to
start
thinking
about
secession
for
the
next
release.
I
know
we're
only
halfway
through
this
one,
but
the
more
time
I
give
you
to
think
about
that.
L
A
Thank
you
very
much.
Anyone
has
any
comments.
Questions
okay,
I,
hear
crickets.
So
again,
thank
you!
So
much
and
I
guess
it's
now
my
turn
to
speak
so
big
things
that
I
big
things
that
I
have
to
mention
cold
freeze
is
coming
and
other
than
that
other
that
other
important,
important
deadlines
that
we
have
this
week,
I
believe
is
a.
We
have
to
have
open
placeholders
for
peers
by
February
28th.
On
top
of
those
two
things
again
conference
is
coming,
and
this
week
we
are
going
to
start
with
a
random
meetings.
A
I
get
if
you
notice,
hopefully
everyone
in
this
meeting
and
everyone
that
is
not
in
this
meeting,
but
in
the
release
team
a
place
hold
it's
a
double
check,
with
your
shadows
to
make
sure
that
they
get
bytes.
But
hopefully,
hopefully
you
all
got
in
bytes
and
no
reason
they
meet
it
at
the
meeting,
thanks
for
the
Wednesday
and
Friday,
a
meaning
some
different
from
today
and
the
reason
for
those
timings
is
I
actually
went
off
the
dural
that
I
sent
out
that
they
began.
A
A
please
start
thinking
about
succession
a
pick
at
some
time
because,
sometime
in
the
future,
to
chat
with
your
shadows,
they
think
they
think
about
who's.
Going
to
take
your
Red
Hots
go
egg
who's
going
to
take
your
place
a
four
day
for
kubernetes
119
and
I'm
gonna
make
a
quick
stop
for
anyone
to
make
any
comments.
Questions
suggestions
before
we
move
on
to
scalability
updates.
A
Okay,
sweet
so
time
for
scalability
updates,
and
this
is
from
Matt
who's
chair
with
six
scalability,
and
he
just
reads
that
everything
looks
good
from
the
scalability
side.
We
don't
have
any
regressions
at
the
moment
and
there
are
some
one
of
failures
from
the
master
informing
test
booth.
They
turn
out
to
be
flakes
and
other
than
that
I
haven't
received
any
secret
information
that
anything
that
there's
anything
to
worry
about
at
this
moment
from
any
scalability
related
test.
A
So
hey
enhancements,
get
part
the
facts,
a
issue,
a
pull
request
15:45
in
the
enhancements
repo.
If
you
care
about
enhancements
a
please
double
triple
check
on
this
one,
a
keep
comments,
reviews
the
order.
A
the
second
issue
that
I
want
that
I
want
to
bring
up
is
about
making
the
release
team
more
happy.
It's
about
having
more
synchronous
communication
in
the
release
team.
Again,
one
of
one
of
the
features
that
we
have
is
a
lot
of
people
in
the
release.
A
Team
are
distributed
around
the
world
and
we
want
to
provide
the
opportunity
for
everyone
to
contribute
equally
to
the
release
team
there.
Within
the
past
couple
weeks,
there
have
been
some
proposals
on
how
to
improve
communication
within
the
release
team.
If
you
have
any
more
for
a
any
more
proposals,
please
drop
em
in
there.
A
This
one
like
a
it,
was
kind
of
healing
in
their
way
in
the
release
port,
so
investigate
out
a
automation
to
facilitate
tracking
of
spreadsheets
I,
paying
all
the
leads
for
for
the
way
for
the
relief
of
the
release
team,
but
again
really
hoping
to
a
really
hoping
to
hear
feedback
from
every
way
from
everyone
here.
If
you
think
that
you
will
make
use
of
spreadsheet,
that
looks
anything
like
the
enhancements,
a
spreadsheet,
a
place,
a
drop,
a
comment
in
there.
A
A
mention
mentioned
that
you
needed
mentioned
that
you
would
like
to
test
it
out,
and
hopefully
we
can
get
the
experts
from
enhancements
in
Jeremy,
Bob
and
everyone
that
has
been
around
to
into
one
of
those
enhancement
spreadsheets
to
help
you
out
and
those
were
my
general
announcements.
It
does
anyone
have
any
a
does
a
does.
Anyone
have
any
other
topics
that
you
want
to
discuss,
or
does
anyone
want
to
discuss
any
of
those
issues?
Yeah.
C
Just
to
around
the
sheets,
the
sheets
kind
of
relate
to
the
enhancing
of
the
cap
artifacts,
so
people
who
have
read
the
proposal
are
aware
that
you
know
kind
of
the
main
thing
that
we
want
to
do.
There
is
break
caps
out
from
a
single
flat
file
into
a
directory
structure
right
separate
the
metadata
from
the
top
of
the
the
front
matter
of
the
of
the
markdown
file
into
its
own
file.
So
it
can
be
ingested
in
various
places.
C
If
that
metadata
includes
details
around
what
the
sir,
by
binding
the
by
binding
the
kept
number
to
the
github
issue,
we
then
have
a
kind
of
a
way
to
track.
Okay.
What
issue
is
open
for
the
enhancements
team
right,
but
also
anyone
who
wants
to
view
it
can
view
the
cap
via
convening
Hanson
issue
via
the
kept
metadata
right.
So
eventually
this
will
be
presented
on
a
site
and
then
hopefully
like
this.
We
won't
need
an
enhancement
tracking
sheet
right.
C
The
issue
triage
stuff
to
use
so
getting
I
want
to
make
sure
that,
like
as
we're
moving
through
this,
that
we're
we're
moving
towards
processes
that
are
that
are
proactive
instead
of
reactive.
There
are
some
there's
some
things
that
we
do
on
the
teams
right
now
that
are
kind
of
like
Oh
ping,
a
person
and
week
tool
of
thing
happens
right
as
opposed
to
provide
a
process
upfront
that
allows
the
thing
to
happen
without
having
to
constantly
paying
someone
right.
C
Of
course,
the
human
interactions,
always
it
required,
but
the
more
we
can
get
machines
in
front
of
this
would
be
lovely
right.
This.
This
is
going
to
make
everyone's
life
easier.
So
that's
why
pretty
much
all
of
these
meetings
I
go
like.
Please
go
review
the
caps
I
go.
Look
at
those
caps.
They're
like
they're
gonna,
be
big
for
us
and
later
cycles.
A
A
A
A
minor
documentation
ensure
that
release
team
will
organize
a
retrospective,
a
just
a
small
reminder
in
the
lead
handbook
to
point
out
a
to
tell
delete
and
team
of
how
to
organize
a
participate,
released
retrospective,
nothing
major
just
documentation
and
document
release,
team
mailing
list
membership
criteria,
I
believe
no
word
in
sick
release
that
we
actually
have
a
host
owner
who's,
a
manager
and
who's
a
who
supposed
to
be
a
member
for
the
release
team
membership
for
the
release
team
mailing
list.
So
this
issue
is
an
attempt
to
get
that
a
documented.
A
C
We
released
team
leads
on
the
call
who
can
who
can
agree
that
the
process
is
kind
of
ad
hoc.
Essentially,
we
said
you
know
someone
triggers
out
a
design
for
something
sends
an
email
somewhere
and
then
magically
stuff
eventually
happens.
We
need
to
get
a
timeline
down
for
that
stuff.
So
the
fact
that
you're
starting
right
now
is
super
awesome.
The
thing
that
you
need
to
do
is
ping
me
and
you've
done
that
so
do
we
did
we
hear
back
regarding
the
design?
Are
we
happy
with
that?
I
know
you
wanted
to
do.
C
A
A
Thank
you
so
much
and
sorry
for
breaking
the
format
a
for
this
part
of
the
meeting
yeah,
but
let's
see
next
up
in
basic
animation
to
facilitate
tracking
spreadsheet.
Again
I
just
mentioned
this
one.
Let
me
double
check
the
there
hasn't
been
anything
and
super
important
since
I
just
commented
on
this
a
little
while
ago
and
yeah.
Nothing
so
again
just
mention
this
one.
A
L
M
M
L
M
A
A
A
N
C
A
So
next
one
a
tracking
husband
sleep
across
multiple
releases
and
document
reason
for
inclusion.
Let's
take
a
look
at
these
couple
of
issues:
okay,
so
Jack
enhancements
across
multiple
releases.
I
forgot
about
this
comment.
So
I
guess
this
one
is
still
a
yeah,
nothing
to
worry
about
on
this
one
hey.
Whenever
we
get
through
code
freeze,
the
enhancements
team
is
gonna.
Give
us
some
information
in
document
reason
for,
in
conclusion,
on
police
blocking
jobs.
I
was
spinning,
see
a
signal
on
this
one
and
Daniel
is
a
helping
me
out
with
this
one
good
again.
A
If
anyone
is
interested
helping
on
improvement,
documentation,
a
foreign
team
test
related
a
please
feel
free
on
the
to
add
anything
to
this.
A
to
this
talk
should
we
leave
open
to
the
world
and
I
believe
this
is
Columbia
working
progress
for
a
bit
so
tracking,
okay.
So
those
were
these
two
issues:
kubernetes
charlie
support
cap
117,
retrospective
116
retrospective.
A
C
So
one
of
the
one
of
the
more
interesting
things
that's
being
discussed
is
like
this
definitely
affects
the
release
team.
One
of
the
more
interesting
things
being
discussed
is
of
potentially
changing
our
cadence
to
question
mark
we
don't
know
yet,
but
that
will
that
can
potentially
affect
how
long
people
are
on
the
release
team
for
how
long
a
release
cycle
is.
So,
if
you
have
opinions
on
that,
please
go
to
that
cap
and
and
write
stuff.
A
E
A
E
C
E
A
C
A
Sweet,
so
that's
that
and
sorry,
Bob
and
Taylor,
if
you
are
watching
this
recording
at
some
point,
I
just
really
think
that
this
will
be
a
good
opportunity
to
do
some
more
behind
the
scenes.
Work
that
might
be
super
interesting
1:16.
Let's
see
this
one
is
all
checked
out
and
we
just
need
to
go
through
things
right.
C
Yeah
that
one
actually
is
in
in
all
check
listed,
as
you
said,
I
think
it
may
need
a
few
issues
in
some
places,
and
some
of
those
I
would
say.
Do
the
I'd
say
to
you,
though,
the
117
one
first
and
see
how
it
matches
up
and
if
we've
got
issues
and
a
lot
of
these
things
cleared
up
or
EE
mentioned
that
and
then
close
out.
The
116.
A
A
A
So
that's
that
hoping
to
keep
my
shadows
busy
and
she
released
in
with
handbook-
includes
an
item
for
I-
didn't
release
retrospective
event.
Okay,
so
this
was
the
peer
that
I
just
sent
document
kubernetes
for
listing
a
cocoa
groups.
Membership
criteria
sent
as
well
update,
released
in
handbooks
I
actually
just
went
to
this
one
before
this
meeting,
and
the
only
thing
that
we
have
a
left
open
is
the
wrong
issue
is
an
issue
for
updating
the
docs
handbook
and
I.
A
Think
the
DOX
team
in
slack
okay,
I
got
a
plus-one,
that's
a
good
signal,
so
it's
in
progress,
I
guess
and
the
last
thing
in
progress
update,
released
team
selection,
Docs
and
this
one
I'm
not
really
sure
what
the
original
intent
was.
A
Josh
was
a
had
something
in
mind:
a
I'm
not
sure
what
it
was.
I
can
figure
it
out.
Sorry,
someone
was
constantly
yeah.
C
I
feel
like
we've
done
this,
maybe
maybe
there's
some
stuff
that
we
can
tweak
around
cuz,
I
cuz
I.
Remember!
Writing
up
the
shadow
selection
criteria.
Maybe
there's
stuff
we
can
tweak
around
what
happens
once
the
survey
goes
out
once
it's
like
timeline
to
close
I.
We
haven't
been
consistent
across
cycles
about
exactly
when
we
do
that,
but
I
think
we're
closer
to
about
two
weeks
for
the
survey
being
open
right
and
then
a
week
and
change
to
decide
and
so
on
and
so
forth.
A
A
So
you
want
to
take
it:
yep,
okay,
sweet
I
forget
to
actually
check
who
was
assigned
to
this.
So
all
Jos
gonna
sign
myself.
Oh
my
this
one
cool
okay!
So
that's
that
and
now
to
do.
Try
splitting
release
schedule
ahead
of
release
playbook
I
really.
The
last
thing
we
had
in
here
was
a
quirk
of
Adolfo.
What
we
want
to
work
on
this,
not
jet,
sorry,
I'm,
Joey,
okay,
sweet!
So
this
is
K.
I
A
So
that's
perfect.
Thank
you
very
much
for
the
update
and
a
single
listing
project
again
just
a
reminder.
If
you
have
ideas
about
how
to
make
the
release
team
more
a
time
zone
friendly,
please
drop
em
in
here.
We
have
a
couple
ideas:
I
go
from
a
stitching
together,
a
poem
or
updates
in
video,
having
updates
in
committee
in
issues
in
the
like
a
I
bought
it
for
a
couple,
but
please
feel
free
to
throw
here
and
give
your
feedback
and
I
will
ping
people
on
slack
for
this
one
as
well.
C
But
again,
this
is
I
think
it's
really
important
that,
like,
if
you're
on
the
call,
if
you're
not
on
the
call
you're
listening
to
it
later,
the
the
non-us
people
really
have
to
push
on
this
right.
I
think
it's
gonna
be
most
exciting.
You
know
what
you
need
out
of
this
meeting
better
than
any
of
us
do
alright.
So
if
you
are
non-us
time,
zones
like
we're,
I
mean
there's
a
lot.
There
are
a
lot
of
things
that
we
are
not
considering,
because
it's
easier
for
us
to
attend
these
meetings.
C
A
Absolutely
and
then
we'll
try
to
ping
people
in
Eskimo
slack,
but
that's
kind
of
funny.
The
irony
of
having
us
people
arrive
the
synchronous
communications.
Please
stop
your
feedback
in
there
if
you
can
any,
if
you're
watching
this
meeting
on
some
other
point.
Okay,
so
the
other
couple
issues
I
already
mentioned
this
one:
a
Doc's,
a
handbook
update
and
this
one
we
already
discussed
a
a
released
on
Jason
to
Google
Club
pocket
I
have
jet
to
go
to
go
through
this.
One
in
detail
would
a
released
him
Weiss
seems
to
where.
C
Yeah
I
think
it's
going
if
there
was
not
support
for
essentially
generating
the
the
bits
that
they
need
for
the
release
notes
site
before,
but
that
is
no
longer
true,
so
I
think
the
last
bit
that
we
need
is
really
just
a
bucket
to
dump
the
notes.
So
we
can
why
or
something
up
to
pick
those
up
and
dynamically
update
the
site.
I
think
that
was
the
plan
right,
yeah,
okay,.
E
A
And
that
is
to
do
let's
go
through
backlog,
really
quick,
so
create
shadow
in
retrospective.
A
I
believe
last
comment
was
shadow
survey.
It's
gonna
take
the
role
of
this
one,
and
that
sounds
like
a
good
idea.
But
what
do
we
talk
about
this
issue?
Just
close
it,
or
are
there
any
closing
remarks
or
anything
that
we
want
to
tackle
or
like
it's
just.
L
A
C
L
A
C
C
I
think
nothing
right
now
and
it's
related
to
the
kept
enhancement
stuff
we're
essentially
like
we
need
to
figure
out
if
we
want
to
do
anything,
automation,
II
to
the
exceptions,
IMO
right,
I
I,
don't
think,
there's
a
need
today,
but
as
we
move
towards
talking
about
what
that's
essentially
commit
ticket
looks
like
so
the
idea
being
that
we
maybe
eventually
move
to
something
where
a
cig
instead
of
filing
an
enhancement
issue
or
instead
of
proceeding
to
like
consistently
have
the
back-and-forth
chatter.
On
the
enhancement
issue,
you
would
file
like
a
ticket
right.
C
That
is
your
your
commit
ticket
for
that
release.
Right,
you
say
in
you
say
in
yeah
Mon.
This
is
the
cap
that
it's
connected
to.
We
plan
to
promote
you
beta.
These
are
the
links
to
the
tests
or
whatever
right,
and
that
goes
in
a
proposed
bucket
right
and
then
from
that
proposed
bucket.
Once
enhancements
freeze
hits,
we
hit
a
button
that
runs
a
script
and
the
script
drags
the
things
from
the
proposed
bucket
into
the
accepted
bucket,
and
then
everything
after
that
becomes
an
exception
right
like
we
handle
it
with.
C
We
handle
it
with
tools,
but
the
so
I
mentioned
what
that
the
layout
of
that
could
be
in
in
the
enhance
caps
artifacts
of
PR,
but
that
is
still
early.
That's
still
just
like
ideas
and
heads,
but
we
want
to
focus
on.
We
want
to
focus
on
landing
that
the
first
three
or
four
improvements
that
they
kept
artifacts
before
we
start
moving
into
tying
that
more
deeply
into
the
release
process.
A
A
A
A
Me
yeah
I,
don't
figure
things
out,
so
what
was
the
one
exceptions
create
shadow
template
for
all
handbooks
testing
FRA.
It's
gonna
be
a
fun
one
scalability
test
and
let's
go
after
this
one.
Okay,
so
create
shadowing
template
for
all
handbooks
latest
update.
Let's
have
the
meet
release
Aubrey,
okay,
so
we
are
gonna,
wait
to
see
what
the
survey
brings
us
before.
We
think
about
this
one
again:
testing
for
cold
freeze,
yeah
I,
want
to
come.
Ai
want
to
add
a
couple
of
comments
in
here.
A
C
I
go
for
it,
it's
gonna,
say:
I,
don't
know
we
can
consider
leaving
like
a
CI
signal
journal
or
something
like
because
that's
like
something
that
popped
up
and
we
I
think
we
were
kind
of
caught
unaware
by
it
and
our
were
still
working
on
mitigating
so
yeah.
We
should
we
should.
We
should
track
that.
His
events
I.
A
Was
gonna
ask
you
more
details
about
it
would
way.
That's
also
like
a
rabbit
hole
and
we
can
go
about
it.
Yeah
yeah
yeah.
Let's
pick
it
up
once
like.
After
this,
it's
calibrated
test
for
beta
releases,
a
I
was
actually
double
checking
on
this
one,
and
the
last
thing
that
I
was
double
checking
was
from
what
I've
seen.
Certainly
if,
at
some
point
a
pop
text
listens
to
this
meeting,
I
sincerely
apologize
because
I'm
not
sure
I
can
pronounce
your
name
properly,
but
other
than
that.
A
A
It
has
a
because
a
TCP
account
and
he
just
has
a
bunch
of
projects
they
all
of
those
projects
have
played
different
clusters,
but
I
believe
every
single
project
is
still
cool
alone.
So
we
don't
have
any
CN
CF
infrastructure
a
in
the
indie
sense
to
actually
run
them,
and
this
one
needs
a
little
bit
more
work.
But.
C
E
C
A
And
other
than
that,
so
that
one
way
that
one
we
can
also
pick
a
bigger,
say,
offline
other
than
that
we
have
the
kubernetes
support
window
to
one
year
and
the
same
procedure
for
entering
living
blocks.
So
this
one
was
left
for
the
possible
say
signals
of
project,
and
this
one
is
mine
in
this
one
way
we
can
ping
people
in
select
to
forget
some
way,
some
more
feedback
but
other
than
that
I.