►
Description
Kubernetes 1.18 Release Team Meeting Burn Down for 20200304
A
And
we
are
recording
now
so
good
morning
evening
afternoon,
a
good,
happy
Wednesday.
Everyone
welcome
to
another
burnt-down
meeting
for
the
kubernetes
release.
118
I
will
be
your
host
today.
My
name
is
my
name
is
Jorge
for
in
case
anyway,
in
case
anyone
was
wondering
and
before
we
get
the
meeting
started.
I
have
to
remind
you
all
like
always
that
we
indicate
that
we
have
a
with
the
kubernetes
community,
have
a
code
of
conduct
which
essentially
boils
down
to
please
be
nice
to
each
other
at
all
times,
as
we
get
the
meeting
started.
B
Good
morning
evening
afternoon,
global
time
so
enhancements
is
currently
read.
We
have
lots
of
issues
that
are
at
risk.
By
at
risk
we
mean
either
they
did
not
file
the
implementation,
peers
or
the
peers
are
yet
to
be
merged
or
they
are
not
getting
enough
attention.
So
we
are
trying
to
track
down
people
on
slack
email
or
whatever,
basically,
hunt
people
down
and
Pingdom.
B
Hey,
please
review,
please
can
you
please
get
it
through
the
whole
post
by
tomorrow
end
of
the
day,
17
of
them
are
still
tracked
as
at
risk,
and
one
of
the
primary
concerns
concerns
that
I
found
was
limited,
rigor
bandwidth
and
it
is
actually
not
something
new.
It
happened
in
the
last
release
cycle,
also
so
yeah
open
to
solve
it
somehow
and
that's
all
on
my
side,
any
comments,
questions
or
concerns
so.
A
As
you
mentioned,
this
is
actually
is
something
that
I
seen
well
from
previous
releases.
A
we
need
more
progress,
reviewers
people
who
are
willing
to
act
on
it
to
work
on
enhancements
with
people
a
just
again
just
to
get
an
idea
just
to
get
an
idea,
and
this
was
a
reason
why
I
asked
on
the
meeting
notes.
So
we
had
17
tracked
items
the
are
at
risk,
how
many
of
them
like
a
dogs
or
something
of
the
sort,
something
that
is
not
related
to
code
or
or
needing
a
code
review.
A
Okay,
that's
useful
information
and
I.
Guess
that's
something
that
we
we
should
try
and
surface
out
today,
a
to
the
way
to
the
rest
of
they
compared
to
the
rest
of
the
community,
because
I
definitely
I
definitely
seen
a
lot
of
contributors,
a
experience,
a
experience,
something
of
a
something
of
this
sort
and
those
a
does.
Anyone
have
any
more
comments.
Questions
suggestions
regarding
enhancements
going
once
twice
sweet.
C
I
think
I'm
I
think
I'm,
taking
that
one.
We
just
had
an
hour
slack
channel
that
he
had
yet
to
miss
so
I'm
going
to
attempt
to
see
what
he
would
would
he
wrote
down.
So
he
did
all
the
work.
I'm
gonna
try
to
summarize
summarize
the
events
for
CI
signal,
so
it
looks
like
we
have
a
couple
for
from
master
blocking
relating
to
take
GCE
both
of
those
for
informing
same
thing
actually
going
down.
C
D
So
I
can
add
a
little
bit
of
context
to
a
couple
of
these,
so
the
latest
stable,
Q
control.
We
have
not
had
a
response
from
the
CLI
team.
We
thought
it
was
being
fixed
by
a
different
unrelated,
the
get
cubed
Sh
script,
but
it
was
not
so
we
followed
up
and
slack
within
today.
All
the
other
ones
are
under
investigation,
as
it
mentions
the
Windows
ones.
D
We
had
some
Windows
folks
take
a
look
at
that
and
it
was
also
determined
that
was
related
to
6000i,
so
it
may
be
that
they
have
are
experiencing
a
similar
issue
there.
So
we'll
make
sure
to
follow
up
and
slack
on
that
as
well.
We
did
get
the
work-in-progress
test
out
earlier
this
week.
The
container
D
windows
test.
We
removed
that
from
the
1.18
informing
board.
So
it's
nice
that
we're
not
getting
that
false
negative
signal
anymore.
But
if
anyone
else
has
any
further
questions,
I'd
be
happy
to
follow
up
on
any
of
these.
A
So
couple
questions
first
off:
let's
start
with
the
easiest
one:
I
guess
the
test
from
I
believe
sick
windows,
the
wall
from
a
that
was
removed
from
a
stream
forming
a
could
you
play.
Could
you
please
add
something
about
it
on
the
retrospective?
It
just
does
I
remember
a
either
Lauer
open
up
an
issue
just
want
a
I'd,
say,
I
think
we
just
need
a
reminder
that
it's
something
like
that
happening.
A
We
need
a
either
more
documentation
or
process
or
something
in
the
way,
something
in
the
way
to
a
work
out
the
kinks
of
how
to
actually
add
tests
into
mass
informing
and
must
have
blocking
dashboards.
They
other
couple
things
that
are
seen
right
now,
so
must
be
informing.
There's
a
Windows.
They,
like
you,
know
nine
windows.
2019.
Both
balls
are
failing
because
of
something
six-year
live
related.
D
That's
what
it
looks
like
we
followed
up
and
slack
with
the
windows
team
and
they
did
not
make
any
progress
on
it.
So
I
think
that
Nick
might
have
also
added
this
in
the
windy
things
sakes
GOI
this
morning
or
the
tests
I
mentioned
earlier,
the
Q
control
stable
one.
Let
me
actually
just
take
a
look
real
quick.
Yes,
he
did
so
we
have
someone
assigned
to
that
and
they're
following
up
on
it.
A
D
That
so
that
was
also
both
both
of
these
this
morning,
the
windows,
ninety
nine
and
twenty
nine
team,
as
well
as
the
stable
latest,
were
responded
to
in
slack
this
morning
about
forty
minutes
ago,
and
so
you
see
I
said
they're
investigating,
so
we'll
try
and
I
can
actually
add
on
the
issue
so
that
others
can
see
as
well
all
sign
the
person
who
said
they're
gonna
look
into
it.
Okay,.
A
D
Yes
and
I
think
someone
responded
about
three
hours
ago
to
this
one.
The
reason
why
it
stayed
as
then
is
because,
once
again
we
thought
it
was
gonna,
be
fixed
by
a
different
fix
that
didn't
actually
make
it
I
started
passing.
So
there
is
someone
assigned
to
this
and
they're
investigating
is
a
three
hour
ago.
Looking
sweet
and.
A
There
is
no
reason
to
believe
that
the
failures
and
118
are
any
different
from
the
ones
with
master,
correct
and
other
than
the
flaky
jobs
seems
to
be
that
they
there
are
the
most
flaky
things
have
issues
attached
to
them,
and
people
are
currently
working
on
them
right,
yep,
okay,
sweet!
So
it's
good
that
we
have
people
working
on
it,
but
I
will
actually
say
that
CI
signal
is
right.
Right
now,
I'd
say
that's
public.
A
E
Good
day,
everyone
I'm
John
for
bug,
triage
I'm,
one
of
the
shadows.
Our
current
status
is
run
right
now,
as
far
as
our
numbers
go.
We
are
mostly
trending
down
for
non-test
flake
issues
in
kkward
and
12,
so
minus
one
from
monday
for
critical
urgent.
We
have
two
and
we
are
following
those
closely
I
note
in
our
notes.
Below
that
we've
got
I
got
the
two
listed
out
that
we
were
trying
to
follow
and
beeping
on
the
necessary
things
as
necessary.
Moving
on
important
soon
issues,
we've
got
four
minus
one
for
Monday
for
all
PR.
E
We
have
29.
Currently
that's
plus
one
from
Monday
for
critical
urgent.
We
have
none,
which
is
good
for
important.
Soon
we
have
19,
which
is
plus
one
from
Monday
and
for
all
issues
for
KK.
For
this
for
this
release
we
have
29,
which
is
minus
three
for
Monday,
so
we
do
trend
out
in
that
regard.
So
again
we
will
be
sending
our
final
notifications
prior
to
code
freeze
and,
following
with
the
appropriate
SIG's,
is
necessary.
E
A
lot
of
the
remaining
PRS
are
kind
of
the
long-running
ones
items
that
have
been
crossing
over
multiple
milestones
in
the
past.
Just
historically
I
think
I've,
seen
one
that
has
been
been
tossed
between
116
has
been
moved
to
119,
for
example.
So
that's
kind
of
the
stuff
that
we're
dealing
with
currently
so.
A
E
A
A
I'm
thinking
that
they
do
a
short-term
thing
that
we
can
do
is
to
help
out
and
ping
reviewers
approvers
to
take
a
look
at
them.
The
long-term
thing
is,
there
definitely
needs
to
a
we
as
a
community
need
to
do
something
to
try
to
prevent
this
and
I
think
this
might
be
related
to
the
17
in
has
817
enhancements
are
still
at
risk.
F
A
B
Hello,
everyone
so
like
we
have
we.
We
have
caused
the
first
deadline
on
February
28th
for
the
placeholder
piers.
We
had
two
to
three
outstanding
enhancements,
but
in
the
last
couple
of
days
we
have
seen
the
piers,
so
we
are
tracking
all
the
enhancements
actively
now
so
we
are
working
on
the
next
deadline,
which
is
March
8th.
All
the
docs
placeholder
Speer
should
be
in
ready
to
review
state.
So
at
this
point
of
time
we
are
30
to
40%.
Dogs
are
in
ready
to
review
state.
So
we
are
in
green
as
a
father,
yeah.
B
A
G
F
A
A
Don't
think
so
so
I'll
ping,
Carlos
or
Sasha
to
give
us
an
a
to
give
us
an
update
here,
but
if
you've
been
keeping
up
with
slack
I
feel
like
that.
The
big
thing
right
now
is
a
code
freeze.
It's
about
it's
about
to
happen
and
I
believe
that
some
of
the
work
to
enable
it
yeah.
So
it
has
already
been
started
so
we're
just
waiting
for
the
deadline
to
actuate
to
actually
happen.
A
Yeah
so
I'm
gonna
say
that
probably
the
same
update
from
Monday,
which
was
that
the
meet
released
shadow
survey
was
sent
out
so
for
anyone
in
the
call
a
please
past,
a
possible
world
wanted
possible
along
to
your
teams
and
in
in
just
mention
the
Thursday
Thursday
release,
and
we
are
still
looking
more
people
more
people
to
reply
last,
a
this
Monday.
If
we
had
around
34
percent
response
rate,
if
we
can
get
if
we
can,
if
we
can
get
it
Chloe,
if
we
can
get
it
closer
to
a
hundred
percent,
that
will
be.
A
That
will
be
amazing
and
again
all
feedback
is
anonymous.
A
only
a
very
only
very
few
handful
of
people
are
going
to
a
are
going
to
have
access
to
it.
But
hey
you
know,
it's
knuckle
is
a
the
information
is
not
going
to
be
made
so
based
economy.
Not
all
the
information
is
gonna
be
made
public.
So
again,
any
feedback
is
welcome
and
please
take
them
other
than
a
I'm
gonna
stop
for
a
moment.
Does
anyone
have
any
comments?
Questions
you
want
that
you
want
to
pass
on
to
them
Mary
to
sleep.
A
Okay,
cool,
if
not,
then
I
can
come
to
the
next
update.
So
next
up
in
my
update,
then
again
same
thing
as
a
same
thing
as
Pandey,
a
code
phrase
is
going
to
a
conference
is
coming
around.
So
what
is
it
today's
way?
Today's
Ponzi's,
so
tomorrow
a
end
up
day.
It's
going
to
be
it's
going
to
be
code
freeze,
a
the
other
important
milestone
is
next.
Monday
is
a
deadline
for
all
Doc's
peers
to
be
ready
for
review,
and
next
Tuesday.
A
We
are
planning
to
release
a
180
embed
in
beta
2
and
the
general
a
general
and
a
general
reminder
that
if
you
have
any
comments,
questions
suggestions
for
the
release
team
in
general.
Please
add
a
note
in
the
release
retrospective.
If
there
is
anything
whatsoever
that
you
that
you
learnt
throughout
this
cycle,
a
please
PLEASE,
hello,
Nolan
I,
don't
note
in
the
retrospective
as
well.
We
want
to
make
sure
that
all
the
knowledge
that
you
that
you
all
have
acquire,
we
can
pass
a.
A
Sweet
so
before
we
end
again,
another
general
reminder
that
I
in
the
open
discussion,
section
I,
put
an
I
put
a
couple
of
links
to
things
that
might
be
interested
to
some
of
you
or
people
in
your
team.
So
the
first
one
release
retrospective
again
anything
that
you
think
might
be
useful.
Just
paddle
in
there
it's
better
to
over,
discuss
things
then
for
us
to
lose
track
of
details
and
had
a
enhance,
kept
artifacts
if
you're
into
enhancements.
A
Please
check
out
that
enhancement
and
keep
a
comment
on
it,
making
the
release
team
or
a
more
synchronous
a
if
you
have
any.
If
you
have
any
suggestions
or
if
you
want
to
both
on
any
of
the
of
the
suggestions,
I
have
already
been
given.
Please
jump
in
and
add
your
emojis
and
investigate
automation
to
facilitate
tracking
spreadsheets.
If
anyone
we
have
most,
we
have
most
of
the
team's
most
of
the
release
team
teams
on
the
line.
A
If
you
think
that
you
will
get
some
benefit,
I
don't
having
a
tracking
sheet
for
something
or
if
it
doesn't
really
matter
to
your
team.
A
please
jump
in
the
issue
and
say
yes
know
something
is
something
of
the
sort
and
other
than
that
opening
up
the
floor
for
anyone
that
wants
to
discuss
anything
anything
notes.