►
From YouTube: k8s 1.16 - Week 9 - Release Team Meeting 20190826
Description
Release details: http://bit.ly/k8s116
A
Hello
and
welcome
to
week,
9
of
the
1/16
burned
down.
We
are
in
week
two
of
burn
down
today
is
August
26,
2019
lovely
to
see
everybody's
faces,
welcome,
release
team
a
little
low,
in
fact,
I'm,
not
sure
if
everybody's
forecasting
out,
but
we
are
about
four
mondays
away
from
the
release
so
not
too
much
time
left.
The
16th
of
September
is
the
slated
release
date,
so
that
should
motivate
everybody
and
encourage
everybody,
and
also
just
a
little
bit
of
wool.
That's
coming
really
quickly.
A
A
B
Let's
go
pretty
quickly
so
right
now
we
have
had
two
that
dropped
off
from
last
week,
so
we
were
at
39
I
believe
now
we're
at
37,
so
ingress
networking
that
was
gonna
be
graduating.
A
beta
has
been
removed
as
sidecar
containers
that's
been
deferred
as
well.
Both
of
these
just
said
they
weren't
gonna
get
their
PRS
in
on
time.
Today,
I'm
gonna
be
rolling
through
all
of
the
issues
that
are
being
tracked
start
pinging.
B
Those
issue
owners,
even
some
here
on
the
call
so
they're
gonna
get
your
own
little
email
notifications
coming
in
just
to
make
sure
that
all
the
kkp
ours
are
being
tracked,
and
so
by
the
time
Thursday
comes
around
we'll
be
able
to
have
a
pretty
good
estimation
exactly
what
did
or
did
not
make
it
in
by
Friday
morning.
Stuff
that
didn't
get
merged
by
Friday
morning
will
have
to
go
through
the
typical
exception
process
to
be
added
back
in
to
be
tracked,
for
this
particular
release.
C
So,
first
off
happy
Monday
everyone
in
the
world
of
CI
signals.
So
just
in
just
a
start
off
we
are
working
on
sending
out
the
report.
You'll
be
out
some
day.
It
will
be
out
sometime
today,
but
some
lot
of
some
notable
events
or
for
this
past
week.
So
I.
There
are
a
lot
of
this
a
after
a
lot
of
discussion.
C
Blocking
jobs
also
make
sure
that
we
really
that
they've
released
blocking
dashboards
properly
reflect
the
features
that
people
are
interested
during
a
three
degree
in
a
given
police.
So
that
was
discussed
a
little
bit
last
week,
but
we're
just
gonna
work
on
we're
going
to
continue
the
work
this
week
on
drafting
some
type
of
policy
to
make
whole
area
of
work
run
a
little
bit
smoother
between
they
released
him
in
India,
one
in
six
now
on
Twitch
elope
dates
so
must
of
walking.
C
There's
there
currently
is
one
a
one
job
failing
I
think
it's
it's
a
a
kind
based
joy,
it's
a
kind
based
job
and
there
are
multiple,
a
networking
jobs
failing
I.
All
of
them
are
dependent
on
on
the
stability
of
to
a
on
the
stability
and
end
usage
of
two
whole
stack,
so
all
of
them
use
like
they
ought
to
be
ipv6
a
IPA
ipv6.
There
is
a
fixed,
that's
great,
that
a
the
husband
has
been
proposed,
and
it's
currently
on
the
review
out
of
the
a
other
than
that
a
last
Friday.
C
There
was
a
new
piece
of
meat
job
that
actually
it
actually
test
for
a
for
it
actually
test
ipv6.
So
so
that's
it!
So
that's
also
here,
that's
also
a
new
thing.
It's
really
that
one
has
been
a
little
bit
flaky.
Oh
I
see
I,
see
multiplayer
I,
see
multiple
peers
are
constantly
constantly
failing
on
the
new
kind,
ipv6
presubmit,
but
hopefully
with
this.
Hopefully,
with
this
fixed,
that's
gonna,
it
is
going
to
be
resolved
other
than
that
a
flakes,
a
master
blocking
and
master
informing
in
no
persistent
failures.
At
this
point,
nothing,
nothing.
C
It
doesn't
look
like.
We
shouldn't
be
worrying
about
too
much
and
master
informing.
The
only
existing
failures
right
now
are
related
to
the
dam
and
rpma
in
RPN
jobs
and
the
last
update
from
that
was
from
James
and
they
are
actually
refactoring
some
of
the
some
of
the
scripts
to
a
turret.
There
were
factories
away
some
of
the
docker
scripts
and
they
were
failing
because
they
were
designed
to
be
wrong
locally,
so
they
so
they
tried
to
create
an
interactive
session
inside
of
a
container.
C
Obviously,
obviously
there
might
be
some
troubles
with
that
running
these
jobs
on
CI,
so
that's
getting
fixed
now,
a
1/16
blocking
1/16,
116,
informing
and
also
not
a
no
failures.
No
failures
at
this
moment
flakes
a
it
doesn't
look
like
any.
It
doesn't
look
like
there's
anything
that
we
should
worry
about.
They're,
either
a
release
miscellaneous
a
same
story,
no
persist
a
no
persistent
failures,
so
other
than
the
kind
I
will
be
a
six
failure.
C
Are
there's
enough
information
to
to
be
confident
to
a
certain
degree,
that
is,
it
is
actually
the
job
that
is
broken,
so
they
so
they
can
ipv6
job
a
job
sitting
in
the
master
in
the
master
dashboards
for
test
grid
and
what
they
were
also
added
for
115,
114
and
113.
All
of
them
they
were
already
running
under
a
the
world
with
is
running
in
a
seat
in
the
cig
testing.
That's
great,
that's
great
cool,
so
before
I
think
I
think
this
test
were
added
last
week.
It's
all
before
last
week
a
whole.
C
A
Just
a
couple
thanks,
George
for
the
update,
so
it
looks
like
there
is
considerable
movement
on
that
ipv6.
Getting
it
fixed.
Is
that
correct?
Yes,
okay,
so
there's
no
need
to
to
that'll
run
its
course,
albeit
DS.
Have
you
expressed
I
haven't
looked
at
that
ticket
I
could
pull
it
up
and
have
you
expressed?
You
know
the
fact
that
it's
sitting
in
master
blocking
and
that
we're
all
fretting
about
it.
Yeah.
C
The
other
day,
there's
been
a
there's,
been
a
lot
of
conversation
with
that
and,
as
I
mentioned,
and
the
people
working
on
it,
they
also
added
a
presubmit
job.
So
in
the
future
a
hopefully
that's
going,
it's
going
to
be
a
of
a
lot
of
help
to
prevent
a
these
type
of
failures
from
this
type,
this
type
of
failures
from
occurring
in
their
release
blocking
jobs.
It
just
make
it
easier
for
us
to
catch
any
issue
that
comes
oh.
A
Okay,
thank
you
and
in
the
master,
informing
those
two
failing
jobs
that
they
they've,
been
failing
throughout
the
whole
relationship
and
Stevens.
Are
there
that
this
still
the
two
that
Stephens
working
on
yes,
okay,
I'd
like
to
get
them
cleaned
out
by
all
pings
Steven
and
then
finally,
did
you
I
know
Josh
had
asked
last
week
in
one?
Sixteen
informing
did
you
ever
get
to
the
bottom.
I
know
there
was
a
quick
update
on
why
those
three
additional
I
think
three
or
four
additional
kind
checks
were
missing
kind,
jobs
from
1/16,
informing
yeah.
C
I
have
a
say
so:
I
guess
I
have
a
part.
I
have
a
partial
answer.
It's
kinda
hard
baby
care,
it's
kinda
hard
to
actually
get
I
should
give
you
a
story
because
I
think
one
of
the
issues
is
is
just
they
I
think
there
is
a
knowledge
gap
between
what
we
expect
to
have
in
the
in
the
release
test,
great
dashboards
and
the
winner
in
the
way,
the
people
a
the
way
that
people
usually
usually
work.
So
for
a
so,
for
example,
they
came
they
kind
of
serrano.
C
A
no
information
within
no
additional
information
whatsoever
was
added
in
order
for
the
jobs
to
be
coupled
with
the
with
the
tools
that
actually
create,
with
the
tools
actually
create
the
way
the
116
in
116
dashboards.
So
so
one
of
the
tools
he
lives
on
the
on
the
testing,
the
testing
infra
repo,
it's
called
config
for
her
ay
ay
ay.
C
The
way
the
way.
The
way
it
looks
and
from
the
couple
conversations
that
I
have
with
people
that
work
working
on
those
jobs
is
a
I'm.
Just
coupling
the
actual
brow
gel
configuration
with
config
Forker
was
not
an
a
a
is
that
it's
not
actually
a
requirement.
So
people
is
so.
It
seems
that
people
don't
it
seems
up.
C
It
seems
that
people
don't
do
it,
and
then
you
know
once
we
actually
create
a
new
branch
and
then
you
add
the
new,
the
new
job
say
the
new
jobs
are
configure
and
they
just
use
whatever
a
whatever
existing
jobs
actually
are
couple
with
a
with
a
conflict
worker
would
again
we
don't
actually
audit
which,
which
jobs
a
witch
doctor.
Those
are
so
it's
okay.
So,
for
example,
in
order
to
actually
add
any
new
jobs,
they
work
in
a
status
quo.
Right
now
is
that
people
have
to
explicitly
go.
C
Okay,
create
a
new
job
configuration
added
to
a
added
to
the
a,
for
example,
added
to
the
one
he
added
to
the
115,
a
dashboard,
so
they
so
they
don't
run
a
they,
don't
actually
use
config
for
cur
and
then
somewhat
and
then
some
other
jobs
a
a
from
a
from
ages
ago.
They
they
actually
they
way
they
were.
A
Okay,
understood
is
so
I
guess.
My
next
question
is:
is
there
is
there
a
canonical
set
of
you
know,
release
informing
jobs
that
should
be
there
for
now,
if
I
take
a
look
at
what
the
past
was,
as
at
least
as
a
guide,
115
114
113
all
have
those
jobs
and
116
does
not
I
understand
that
you
know
it's
it's
at
the
people's
discretion
to
put
things
in
the
right
place,
so
they
appear,
but
should
we
try
and
I'm
just
worried
about
a
lack
of
coverage
there.
F
A
Me
that
they,
because,
if
it's
not
in
what,
if
it's
not
in
116
informing
once
once
code
Thor
and
we're
completely
off
master,
you
know
I
just
want
to
make
sure
that
there
is
a
appropriate
set
of
tests
for
that
release.
At
the
moment,
it's
not
so
obvious,
because
master
and
116
are
pretty
much
fast
forwarded
to
head
every
week,
so
yeah
I'm
just
wondering.
Should
we
try
and
match
them?
Should
we
get
take
the
take
the
effort
to
try
and
match
them,
or
this.
E
C
That,
yes,
okay,
so
a
couple
things
onto
that.
So
so
the
canonical
set
up
jobs
it
tough,
Jade
I,
should
run
on
any
release
it
that's
definitely
what's
what's
in,
must
a
must
must
be
informing
and
it
must
be
informing
in
this
case,
master
a
must
have
mastering
forming.
So
there's
a
lot
of
one
thing:
the
discrepancy
between
the
one
Fateh,
for
example,
the
discrepancy
between
115
and
116,
is
last
week.
C
So
the
quick
fix
is
a
to
create
to
create
more
the
same
set
of
kinder
kinder
jobs
for
1:16,
and
we
will
be-
and
in
that
was
a
that
was
part
of
the
plan
for
this
week
for
say
a
signal
that
way
we
were
gonna,
get
in
contact
with
toaster
by
cycle
to
a
torch
and
to
actually
get
that
done
so,
hopefully
they'll
be
at
they
ate.
All
the
previous
releases
will
have
the
same
set
of
master
a
of
informing
jobs
by
the
end
of
this
week.
A
A
That
it's
I
appreciate
that
it's
a
stopgap
measure
because
you
don't
have
policies,
so
things
can
inherently
come
out
of
sync
I.
Guess
the
the
timely
issue
that
we
have
now
is
the
later
we
add
them.
If
they
are
broken,
then
we
got
to
go
back
and
actually
figure
out
how
to
fix
them.
So
any
the
sooner
we
get
them
later
and
we're
focused
on
1/16
specifically
and
once
you
know,
master
diverges
from
the
release.
I'm
very
concerned
about
making
sure
that
1/16
is
adequately
tested.
Given
past
testing.
A
So
you
know
I,
don't
know
if
that's
going
to
happen
in
116,
but
there's
something
that's
going
to
be
a
problem
and
it's
flaky
its
flaky
on
150
14
to
115
the
upgrade
the
upgrade
job
so
just
to
make
sure
that
you
don't
rail
yourself
into
having
a
heap
of
work
in
the
last
couple
of
weeks,
any
more
than
you
already
will
have
I
think
getting
them
up.
There
would
be
a
good
idea.
A
Excellent
okay,
so
assuming
1/16
gets,
gets
fixed.
Sorry
1,
the
CI
signal
for
the
jobs
I
should
say
for
ipv6
get
fixed.
We
should
be
green,
that's
the
only
thing
preventing
green
at
this
point
and
that
was
a
light
binding
Edition
last
week.
So
that's
additional
jobs.
We'd
never
had,
but
you
know
we
have
IP
6
coming
v6
coming
in,
so
we
need
them.
Ok,
cool
bug,
triage
with
Josiah.
G
Hello,
just
out
here
for
bug
triage,
so
I'll
open
with
the
number
of
open
issues
and
PRS
that
we
have
remaining.
So
we
have
66
open,
non
tester,
flake
issues
destined
for
116
and
that's
down
from
4
open
that
we
had
last
meeting
so
for
open
PRS.
We
have
47
that's
down
by
5
and
for
open
all
open
issues,
including
tests
and
flake
issues.
We
have
79
and
that's
down
by
5,
so
1
more
than
the
non
tester
flake
issues
down
by
one
more
so
where
we
are
at
we've
started
pinging
all
of
the
issues.
G
Previously
we
were
pinging
issues
that
had
been
inactive
since
July,
primarily
and
now
we
are
pinging
all
issues
and
we
may
go
back
and
take
a
second
pass
through
already
pinged
issues
for
those
that
we
have
not
gotten
a
response
for
yet
as
soon
as
we
have
finished,
pinging
everything,
since
the
upcoming
milestone,
is
this
Thursday
end
of
day
Pacific
time
for
code?
Freeze,
so
I
might
add
as
well.
If
any
other
teams
need
help
with
bug,
triage
feel
free
to
contact
us
we're
here
to
assist
with
that.
Thanks.
G
G
D
D
G
G
H
So
there's
a
quick
update,
it
is
getting
better
we're
getting
more
and
more
responses,
but
regarding
issues
it
is
not
that
would
turn
around
these.
We
have
a
what
it
is
about,
I
think
40%.
It
was
last
meeting
that
we
had
no
responses
on.
It
is
not
that
good,
but
we
are
going
to
try
to
improve
that
or
if
it
is
still
that's,
not
active,
we
need
to
see.
Probably.
How
are
we
going
to
echo
those
this
ways?
Do
we
want
just
move
them
to
another
milestone
and
we
boot
them
from
I
stores?
I
Hello
everyone:
this
is,
we
need
from
Doc's
team
as
working
as
a
header,
so
this
week
we
are
running
in
green.
So
last
week
we
are
done
with
all
the
docs.
Be
a
placeholder
peers
are
in
place,
and
a
September
3rd
is
is
that
you
for
docs
PR
ready
for
review,
so
we
are
working
on
it
other
than
that.
We
are
going
good
with
this
and
we
had
an
amazing
session
from
Trillian
much
conflict
resolution,
possibly
shadows.
And
yes,
we
are
doing
good.
C
A
H
Probably,
in
a
sense
there,
let's
say
I'm
still,
not
sure
exactly,
but
I
would
just
like
to
have
more
responses
on
the
issues.
So
this
is
something
I'm
looking
at
mercy
mo
kio
fee.
If
you
say
yes,
this
is
a
number
and
we
are
going
to
fix
most
of
them.
But
at
this
point
we
are
not
clean,
clear.
What's
going
to
end
up.
H
A
Is
it
of
what
percentage
are
you
gonna
feel
comfortable
that
you've
taken
the
adequate
steps
to
get
things
reasonably
resolved
in
1/16
before
the
release
goes
out?
The
challenge
I'm,
having
is
there's
no
historical
data
that
I
can
pull
that
really
easily
because
we've
never
tracked.
You
you've
bubbled
up
numbers
week
over
week
and
and
percentage
difference
or
number
difference
in
previous
releases.
A
We've
just
linked
to
the
dashboard
and
they've
all
been
pulled
at
different
points,
I
mean
probably
we
could
go
back
and
dive
in
there,
but
I'm
just
wondering
you
know
well
this
release
how
we
tracking
is
there
more
bugs
open
at
this
point
or
less.
You
know
what
I
mean,
so
it
would
be
interesting
as
you're
formulating
anything
to
automate.
A
But
for
me
as
a
release,
lead
and
you're
telling
me
it's
red,
I
didn't
really
need
to
know
how
to
get
you
green,
and
at
the
moment
the
only
thing
is
more
muscle
and
more
awareness
to
get
people
to
close
things
is
how
we
get
green.
So
I,
don't
know
if
Josh,
Shaw
or
Steven
have
anything.
To
add
I
mean
is
this?
Is
this
a
normal
pattern
for
us
to
be
in
right
now,
Josh?
Are
you
concerned?
I
would
just
ask
Josh
for
as.
E
Emeritus
I
was
gonna,
say
it's
normal,
but
that
doesn't
mean
that
it's
not
a
cause
for
concern,
because
it's
also
normal
for
us
to
have
outstanding
critical
issues
for
days
before
prospective
release
and
and
and
well
that
is
something
we've
done
multiple
times
that
doesn't
necessarily
make
it
a
good
thing,
so
the
I
mean
particularly
because
so
far
we
haven't
had
any
project
affecting
unexpected
developments,
this
release
cycle.
That
would
be
great
if
we
could
push
on.
E
Actually,
fulfilling
some
of
our
targets-
and
things
of
you
know
saying
hey
this,
you
know
this
should
be
green
all
the
time
these
should
be
getting
quote
three
days.
If
they're
marked
critical
urgent,
you
know
it's
pushing
for
for
cyclical
improvement,
rather
than
just
what
we've
done
before.
Okay.
A
E
That's
what
priority
critical
urgent
is
supposed
to
be
for
that
and
having
it
in
the
milestone
right.
Give
those
to
give
there's
two
things,
then
that
saying
that
this
is
release
blocking
and
and
prowl
already
bugs
people
I
mean
mind
you
through
their
github
notices.
So
I,
don't
you
know
necessarily
it
varies
how
much
P
books
you
see
this,
but
prowl
already
bugs
people.
If
something
is
more
critical,
urgent,
like
like
every
three
days,
it
notifies
them
and
says:
hey,
you
need
to
update
this.
E
You
know
sometimes,
depending
on
how
Coraline
it
is,
you
started
out
really
important
soon
and
bump
it
up
the
critical
urgent.
If
you
don't
get
a
response
now,
materially,
my
experience
has
been
that
you
have
to
ping
people
via
slack
anyway,
because
everybody
has
too
many
github
notices
and
they
miss
stuff.
A
Okay,
thanks
for
shedding
some
light
there
Josh
I.
So
how
about
we
take
an
action?
Can
you
bubble
up
how
many
critical,
urgent
or
important?
Soon
you
have
as
a
subset
of
those?
Yes
again,
just
because,
because
if
you're
saying
it's
10
or
20
or
30,
then
obviously
we
have
a
problem.
But
if
it's
1
or
0
and
we're
monitoring
that
you're
not
sure.
D
I
have
in
the
past,
pinged
sig
leads
on
the
critical
urgent
bugs
when
I
haven't
gotten
a
response
from
the
issue
from
pinging
on
the
issue.
Yeah
I
I
used
to
just
go
and
start
with
the
sig
start
with
a
sig
channel
and
just
add
some
folks,
and
if
that
doesn't
get
your
response
within
a
day,
then
DMS
and.
E
Ok
I've
done
that,
and
sometimes
that
you
have
to
do
that.
If
it
turns
out
that
the
underlying
issue
is
complicated
and
hard
to
fix
because,
like
sometimes
people
aren't
responding
because
they're
not
noticing-
and
sometimes
people
aren't
responding
because
they
are
noticing,
but
they
don't
know
how
to
fix
the
issue.
H
H
A
Know
it
helps
a
lot.
Thank
you
very
much
for
your
hard
work
there
and,
if
you
want
to,
if
you
want
to
give
the
release,
leads
a
list
of
issues
and
and
because
I
know
time
zone
wise
mark
mark.
Oh,
it
may
not
be
conducive
to
you
staying
up
really
late
at
night.
But
if
you
want
to
hand
us
a
list
and
say
hey
lucky
Quinn,
can
you
show
up
to
sig
Network,
because
we've
got
something
critical
urgent?
E
G
J
Happy
Monday
everybody
short
and
sweet
today
as
well.
We
do
have
the
first
draft
going
for
the
release.
Blog
post
I'm
gonna
be
posting
that
a
little
bit
later
today
or
tomorrow,
still
working
with
some
of
the
SIG's
to
get
their
first
drafts
for
blog
posts.
Looking
for
those
this
Friday,
and
then
we
have
a
couple
meetings
this
week
too,
just
to
go
over
some
questions.
We
were
able
to
set
all
the
priorities
for
this
release,
so
we're
looking
good
on
all
fronts,
but
obviously
always
billable.
A
Give
us
a
week
with
it.
If
we
have
any
questions,
we
can
async
it
and
if
we
really
need
a
conversation
just
to
make
sure
we
have
nothing
outstanding,
it
looks
like
you
have
had
marked
improvement
since
last
Monday.
Are
you
waiting
on
any
of
the
SIG's
to
get
back
to
you
regarding
their
themes
for
this
release
or
you?
It
looks
like
that's
been
resolved.
Yes,.
J
I
think
that,
looking
through
all
of
the
cups
and
PRS
we've
got,
we've
already
captured,
you
know
ones
from
groups
that
we
would
want
to
focus
on
anyway.
The
groups
that
have
not
responded
I,
don't
think
that
they
would
have
made
that
like
the
top
list.
As
far
as
things
to
call
out
for
this
release,
so
we
really
convert
on
that
front.
Cool.
K
A
K
A
A
Thank
you,
emeritus
Leeds,
Thank,
You
Josh
release
lead
update
with
myself
thinking
about
coloring
and
status
I'd
like
to
do
this
in
burn
down
just
to
give
an
overall
picture
I'm
going
to
go
with
red,
citing
CI
signal
and
one
failing
job
in
master
blocking
which
is
being
addressed
and
bug
triage
being
red
still.
So
we
are
making
improvements
to
understand
that
as
everybody
has
heard,
but
we
will
go
with
red
for
now.
A
What
I
would
like
to
see
is
yeah
more
visibility
on
the
bug
triage
so
that
we
can
assess
how
to
chop
that
up
and
CI
signal
looks
like
it's
in
good
shape
for
this
part
of
the
release
cycle,
up,
stop
coming
milestones
so
code
freeze.
Is
this
Thursday
end
of
day
Pacific
that
is
August
29th
if
you're
working
on
any
enhancements?
Anybody
in
the
release
team
make
sure
that
all
your
code
and
kkp
ARS
are
been
merged
by
that
date
and
if
you
think,
anything's
going
to
slip
have
an
exception
request
ready
to
go.
A
But
let's
work
towards
that
date.
9
3,
which
is
next
Monday,
is
all
Doc's
should
be
ready
for
review.
So
we
had
the
docs
team
mentioned
that
and
they're
in
good
shape,
but
please
make
sure
any
Doc's
that
you're
trying
to
land
as
part
of
this
release
are
ready
to
go
and
9/4
is
next
Tuesday,
which
is
beta,
2
being
cut.
A
Also
it's
worth
mentioning.
Next
week
we
go
into
the
2-week
lead
up
cycle
of
daily
burn
downs,
in
which
we
add
an
additional
two
meetings
a
week
on
Tuesday
and
Thursday.
My
current
plan,
unless
anybody
objects,
is
to
cancel
the
meeting
on
Monday
and
pick
up
the
conversation
on
Tuesday,
given
that
Monday
is
a
public
holiday
in
the
United
States
and
we
have
meetings
every
day.
If
anybody
feels
very
compelled
that
we
have
the
Monday
meeting,
please
let
me
know
I'm
amenable
to
making
that
happen.
A
Should
we
try
and
do
that,
but
I'm
not
currently
worried
that
we
need
to
staff
that
meeting
on
Monday
feel
free
to
speak
up
now,
if
you
think
otherwise,
I
think.
If
we
weren't
in
the
period
of
burn
down,
we
would
reschedule
it
to
a
Tuesday
or
possibly
have
it
on
a
Monday.
But,
given
that
we
have
a
five-day,
cadence
I
think
it's
ok
to
miss
one
day.
A
I
think
the
only
risk
is
not
having
an
update
for
young
in
the
release
branch
management
team
before
they
actually
start
cutting
branches
I
tend
to
see
the
work
that
they're
doing
happened
before
I
wake
up
and
being
finished
when
I
wake
up.
So
that's
probably
the
only
risk
I
can
think
about.
Is
them
not
having
a
clean
view
on
the
CI
signal
at
that
point,
but
we
will
have
an
update
on
Friday
for
them,
so
we
might
be
in
good
shape
anyway.
A
Okay,
the
only
other
thing
was
kind
of
a
call-to-action
email
on
the
mailing
list.
I
was
thinking
just
to
send
out
another
reminder
to
everybody
that
code
freeze.
Is
this
Thursday,
that's
on
kubernetes
dev,
the
release
team
and
the
sig
leads
I
wondered
if
anybody
wanted
me
to
add
call
to
actions
I
want
it
to
be
very
cold
action.
If
you
are
this
person,
you
must
do
this.
A
Kendrick
go
feedback
after
I
sent
that
email
last
week
that
a
lot
of
people
updated
their
appropriate
tickets
and
issues
and
PRS.
So
is
there
anything
we
should
add?
I
won't
kind
of
I
won't
suggest
what
I
think
needs
to
be
added,
but
if
we
can
add
a
call
to
action
to
folks
so
that
come
Thursday,
it's
of
no
surprise
and
people
have
three
or
four
days
to
get
things
in
the
right
order.
A
A
A
A
A
A
E
A
F
A
A
Document
membership
criteria-
I
have
this
one
to
do,
I
haven't
moved
it
out
or
to
do,
but
I
will
do
it.
I'm
still
willing
to
take
that
on.
This
is
with
me
as
well
same
thing
applies
survey.
Improvements
in
to
do
this
is
with
emeritus
leads
and
guessing.
That
will
happen
in
due
course
and
what
qualifies
for
a
milestone
so
jeff
has
this
one
Stefan
the
call
No
okay,
so
they
are
all
assigned
and
I
take.
It
will
be
moved.
A
Everything
in
to
do
is
assigned
as
well
I'm
going
to
call
it
there
unless
anybody
has
anything
else.
The
only
thing
I
noted
from
the
call
was
CI
signal.
Sir
George
had
mentioned
some
policy
to
regarding
the
jobs
and
how
to
get
them
on
the
boards.
Was
that
something
that
needed
to
be
tracked?
George
almost.
A
A
A
Okay,
so
before
we
close
out
reminder,
we
will
meet
again
Wednesday
at
9:00
a.m.
Pacific
and
then
Friday
at
9:00
a.m.
Pacific.
So
I
will
see
you
all.
There
excited
to
see
how
the
release
progresses
and
thank
you
very
much
for
joining
us
today.
I
will
post
this
video
to
YouTube
later
today.
Thank
you
very
much
have
a
wonderful
Monday
thanks.