►
From YouTube: k8s 1.16 - Week 8 - Release Team Meeting 20190823
Description
Release details: http://bit.ly/k8s116
A
Recording
and
kick
this
off
hello
and
welcome
to
week
8
of
the
1/16
release.
This
is
burned
down
on
Friday
August
23rd,
welcome
to
everybody
before
we
get
into
it
can
I
get
a
note-taker.
If
you
would
like
to
take
notes,
please
place
your
name
in
the
note-taker
section
at
the
top
of
today's
agenda
and
if
you're
present,
please
add
your
name
to
the
attendees
section,
with
your
Associated
role
on
the
release
team
be
very
much
appreciated
before
we
get
into
it.
A
This
meeting
is
being
recorded
and
will
be
posted
to
YouTube
after
it
finishes
today,
and
I
would
like
to
remind
everybody
that
all
conversations
are
subject
to
the
kubernetes
code
of
conduct,
which
says:
please
be
awesome
to
each
other,
and
with
that
we
will
get
right
into
it
and
Kendrick.
Can
you
please
take
us
away
with
the
enhancement
updates,
yeah.
B
I'll
I'll
update
this
in
the
notes
here
in
a
few
minutes,
so
we
had
one
enhancement
drop
off
earlier.
Today
it
was
the
sidecars
which
was
number
753.
B
Just
looked
like
it
said
that
it
wasn't
going
to
get
the
PRS
in
on
time
before
code.
Freeze,
so
good
to
see
people
are
paying
attention
to
the
emails
that
locky
sending
out.
So
that's
fantastic.
There
was
another
message
about
758
that
will
might
be
dropped
as
well.
There
were
some
concerns
that
there
are
a
pr2
that
just
won't
make
it
in
on
time
as
well,
I'm
waiting
for
response
back
from
the
issue
owner,
but
other
than
that
everything
should
be
looking
pretty
good.
B
C
So
we
have
very
recent
issues,
and
so
all
of
this
has
been
recorded
in
this
document,
but
I
might
add
up
like
little
details
after
disco
ordering
this
often
but
yeah.
So
let's
say
so.
Our
status
read
due
to
one
blocking
issue
in
in
116.
Blocking
sorry,
no
sorry,
sorry
in
mustard,
so
it's
a
new
test.
It's
under
investigation.
It
has
no
green
runs,
so
the
link
is
there.
We
also
have
for
flaking
nothing
critical.
C
There
are
sporadic
failures
and
mostly
things
that
have
been
happening
during
other
other
cycles
and
that
have
been
addressed
but
either
have
been
decided
that
it
that
are
not
a
big
deal
or
or
whatever,
but
there
are
not
not
critical
time
passing
then
and
116
blocking.
We
have
to
play
King
14
passing
so
in
general,
everything
looks
like
good,
even
though
we're
red,
but
everything
is
being
addressed.
D
Ci,
because
we're
going
through
this
whole
thing
of
trying,
you
know,
of
applying
the
master
block,
blocking
test
drop
criteria,
etcetera.
Could
the
CI
single
team
record,
which
of
these
jobs
are
flaking
within
blocking,
because
it
may
be
that
we
need
to
actually
demote
a
bunch
of
jobs.
I
would
have
bought
it.
Yes,.
A
A
E
Everyone,
so
for
now
our
current
status
is
that
we
are
red.
We
still
have
high
number
of
open
interest
right
now.
We
are
at
70.
This
is
minus
6,
since
Wednesday
it
is
getting
better
but
I
certified
it
way
too
much.
Considering
that
we
are
approaching
code
freeze
in
less
than
six
days
or
something
like
that,
we
got
it.
Prs
is
getting
better
with
better
every
day.
We
are
842
right
now,
which
is
several
ways
that
we
headed
by
the
state
and
regarding
total
number
of
open
issues,
acrylic
tests,
efflux
rated
votes.
E
We
are
at
84
5
less
than
we
had
audio
aesthetic.
We
will
start
peaking.
We
may
be
distressed
peers
of
all
day
for
now.
I
think
we
hear
Pickett.
Most
of
us
appears
we
have
platitude,
but
as
I
mention
it,
the
number
of
70
issues
is
the
one
I
still
fight
large
and
we
plan
it
initially
to
being
48,
but
we
managed
to
do
only
38.
It
is
okay
and
I
hope
we
will
get
to
other
issues
as
soon
as
possible,
so
yeah
nine
of
those
38
are
bigger
today.
E
E
As
the
godfrey
starts
so
yeah,
it
is
still
a
little
bit
a
problem
and
a
lot
of
issues
we're
not
acting
like
for
a
long
time
and
they
were
just
moved
from
the
milestone
to
the
milestone
and
we
ended
up
just
coming
for
this
one,
a
lot
of
them
like
if
there
are
a
lot
of
issues
that
they
started
like
113
and
114,
and
very
much
fix
it
then
they're
not
even
act
event.
I
think
it
is
going
to
be
okay
if
you
just
of
them,
if
you
don't
receive
any
response
by
godfrey's.
A
Wondering
if
we
just
send
an
email
out
to
the
the
mailing
list
and
just
say,
look
we're
really
trying
to
clean
this
up
before
code.
Freeze,
we'd
appreciate
it.
If
these
are
still
active
issues
that
you
at
least
provide
a
comment
or
an
update
on
them
as
to
the
status
so
that
we
can
make
a
decision
as
to
how
to
treat
them.
Okay
code
I
can.
A
Yeah,
we
just
need
to
make
it
really
clear
as
to
what
people
need
to
do,
because
sometimes
they
don't
understand
what
the
milestones
mean
and
what
this
means
in
context
of
the
milestone.
So
if
we're
very
clear
that,
if
you're
an
issue
or
an
owner
or
a
razor
of
these
issues,
at
least
if
we
can
get
an
update
on
the
PRS
and
as
to
what
it
means
to
get
them
done
before
code
freeze,
so
that
at
least
then
we've
said,
we've
done
our
due
diligence
on
getting
them
moved
along.
But
it's
good
to
see.
A
F
Everyone,
so
things
are
looking
good.
We
are
going
to
meet
the
deadline
right
now.
We
only
have
two
announcements,
which
is
which
is
758
and
and
556
now
for
the
556,
which
is
our
residance
support
for
CSI
problems,
we
got
a
feed
back
and
the
dog
should
be
out
before
the
end
of
today.
Now
for
758
I
was
just
aware:
I
will
just
meet
aware
of
the
fact
that
the
announcement
might
not
make
it
into
1.16.
F
So
can
it
is
talking
to
the
to
the
to
the
state
orders
about
the
status
of
this
announcement
so
based
on
that,
we
are
going
to
decide
on
dogs
updates.
So
if
it
doesn't
go
into
1.16,
then
dogs,
then
it's
going
to
drop
off
from
dogs,
so
those
are
only
two
things
that
we
are
waiting
on
the
rest,
we
have
some
dark
wired,
no
dogs.
We
have
a
lot
of
dogs,
PR
and
draft
right
now
and
we
have
kaku
they've
been
merged,
so
things
are
looking
good
on
the
I
agree
right
now.
A
G
H
H
A
A
Okay,
moving
on
emeritus
leads
have
no
update.
So
that's
on
to
me,
I'm
gonna
call
this
read
based
on
the
signal
I'm
getting
from
CI
signal.
I,
don't
like
have
any
I,
don't
feel
comfortable
with
anything
in
master
blocking
failing
al
beard.
I
took
a
look
at
that
and
it
is
a
new
entry
to
master
blocking.
So
that
raises
questions
about.
A
You
know
the
acceptance
criteria
to
that
dashboard
and
getting
that
updated,
but
no
doubt
I
know
the
people
that
work
on
that
test,
that
it
will
get
resolved
in
a
timely
matter
and
I
think
it's
probably
good,
given
that
we
have
some
ipv6
things
going
in
and
getting
more
coverage
on
those
tests.
So
let's
give
it
a
couple
more
days
or
a
couple
more
bone
down
meetings
and
see
if
there's
no
progress
change
there
and
we
don't
actually
have
a
code
cut.
A
So,
even
though
we're
trying
to
clean
up
as
much
as
we
can
before
code,
freeze,
I
still
think.
Let's
call
it
read
for
today
and
see
how
it
goes
milestones.
One
day
briefly
touched
on
it.
But
today
is
the
docs
PR
deadline,
and
has
he
mentioned?
There's
only
one
outstanding
and
that's
going
to
be
based
on
whether
that
actually
we've
been
told
by
the
maintainer
that
they're
going
to
get
that
in
by
the
end
of
the
day,
so
I
think
we're
in
good
shape
for
the
docs
PR
deadline.
A
At
the
end
of
the
day
code
freezes
next
Thursday
I
just
sent
out
an
email
to
the
mailing
list,
just
encouraging
people
to
update
all
the
things
that
they
have,
that
we're
tracking
so
that
it
makes
it
easier
for
Kendrick
and
bug
triage
and
folks
like
that
to
make
decisions.
So
we
will
continue
and
I
might
send
out
another
email
to
the
mailing
list
on
Tuesday
next
week,
just
so
with
the
final
ping,
but
we'll
be
going
into
code
freeze.
A
And
then
we
continue
this
track
of
burn
down
for
the
next
week
where
we
have
Monday
Wednesday
Friday.
The
other
thing
worth
mentioning.
That's
a
little
bit
further
out
I
think
it's
two
weeks
out.
It's
Labor
Day
weekend
in
the
US
MX.
Not
this
weekend,
the
weekend
after
I
believe,
which
means
we
have
a
Monday
off,
which
is
the
2nd
of
September.
So
we
will
just
continue.
A
A
Moving
on
to
open
discussion,
I
took
a
quick
view
of
the
project
board,
which
we
typically
walk
for
any
changes.
I
will
walk
it
again
on
Monday,
but
if
you
have
anything,
that's
in
progress
on
the
project
board
for
the
release
team,
please
keep
that
updated
all
issues
in
in
progress
to
do
and
backlog
have
been
assigned.
So
if
there's
any
decisions
that
need
to
be
made,
please
get
that
updated
and
I
will
walk
that
on
Monday.