►
Description
Kubernetes 1.18 Release Team Burn Down Meeting for 20200317
A
I
see
a
club
a
good
morning
evening
afternoon.
Everyone
welcome
to
another,
a
turndown
meaning
for
the
kubernetes
118
release.
I
will
be
your
host
today.
Hole
good,
like
always,
I
have
to
mention
a
whenever
we
started
one
of
these
things
that
we
are
on
there
under
the
kubernetes
code
of
conduct,
which
essentially
boils
down
to
please
be
nice
and
kind
to
each
other
at
all
times.
A
D
One
I
wanna
just
give
a
shout
out
to
everybody:
I'm
the
enhancements
team
I
have
a
fever
and
headache
so
like
I'm,
not
feeling
super
great
and
yesterday
was
way
worse
and
they
were
super
awesome
and
organized
who's.
Gonna.
Do
the
updates
for
the
rest
of
the
time
and
take
taken
the
lead
on
that
so
I
just
wanted
to
give
everybody
a
shout
out.
A
C
Okay,
we
are
green,
since
we
we
don't
have
any
failing
job
in
massive
Britain's
just
word
or
eight
frankie
jobs
that
are
putting
by
this
grid
master
reforming.
We
have
the
these
two
windows
jobs.
There
have
been
some
updates.
I
think
what
he
did.
You
update
the
dog,
but
what
actually
happened
with
those
jokes,
okay,
I'm
going
to
explain.
C
In
short,
the
jokes
were
totally
broken
and
we
thought
that
the
problem
was
because
what
we're
unable
to
start
in
Windows
nodes
that
was
fixed,
but
that's
of
cooking,
to
fail,
and
it
seems
that
there's
been
a
bus
flag
in
a
bus
Crete,
so
that
was
fixed
as
well,
so
those
subs
seem
that
are
being
healed
like
slowly,
slowly
and
one
of
them.
That
2019
is
good
back
to
the
original
level
that
we
had
with
and
we're
still
waiting
for
the
six.
You
know
response:
we
have
another
job
that
is
failing.
C
The
scale
correctness
is
open.
If
the
issue
today
yeah
and
yeah,
we
need
to
keep
an
eye
on
it,
but
it's
really
hard,
because
this
is
running
once
per
day
and
since
we
don't
have
any
rerun
permissions,
you
can
test
the
fix
or
whatever
so
I'm,
going
to
pink
might
say
later
on,
in
our
record
slack,
to
push
him
to
take
a
look,
and
hopefully
they
are
going
to
fix
it
right.
Okay,
so
the
release
misc.
We
have
this
CI
to
an
SEO,
backup
job
that
is
failing
again
and
it
was
an
attempt
to
fix.
C
C
There
have
been
like
a
breaking
change
in
the
February
February
pad
set
for
widows,
the
proko
dinners
and
since
being
fixed
in
the
March
but
said,
but
the
fixed
surprise
test
also
be
updated.
So
this
really
messed
up
right.
I
did
one
point:
eighteen
informing:
what
have
you
stood
with
this
doctor,
which
is
like
the
same
with
a
master
reforming,
and
there
is
another
one
that
I
guess
and
dinners
were
one
quality
with
those,
so
that's
under
investigation,
so
that's
failing
as
well,
nothing
in
flaky
jokes.
C
E
Just
I
try
to
do
that
late
afternoon
and
just
didn't
have
cycles
to
follow
up
this
morning,
so
I'm
trying
to
try
to
keep
a
lid
on
this
situation.
So
thank
you
and
I'm
also
expressing
the
urgency
back
to
them.
So,
thanks
for
all
your
patience
and
working
on
this
and
I
understand
that
you're
being
being
very
patient,
so
feel
free
to
me
and
push
me
if
you
need
needed.
George.
A
And
with
that,
no
a
will
do
and
thank
you
so
much
for
everything
that
you're
doing,
because
a
also
to
what
context
Nick
of
all
day,
a
comments
that
I
added
on
the
mini
notes.
I
got
a
I,
got
them
from
lucky,
so
they're,
so
sick
windows,
all
the
windows,
people
all
the
windows.
People
have
definitely
been
doing
a
lot
of
work.
E
F
Good
morning,
good
afternoon,
good
evening,
Cir
sorry
bug
triage
is
current
status
is
red.
We
are
trending
to
yellow,
but
we've
had
a
slight
uptick
open,
non-test
flakes.
We
are
down
to
two
four
from
yesterday
priority
critical
urgent.
We
are
at
three
which
is
down
to
four
yesterday.
We
have
had
no
change
in
priority
important
soon.
We
remain
at
zero
for
open
kkp
ours.
We
are
holding
steady
at
five
priority
critical
urgent.
We
have
went
up
one,
we
are
out
cold
at
one,
and
that
is
a
note
which
is
891.
F
Sixty-Six
priority
important
soon
PRS
we
are
holding
steady
at
four
and
open
KK
is
remaining
clear
down
to
224.
We
are
continuing
to
ping
people.
I
have
gone
through
and
done
a
lot
of
pinging
this
morning.
I
know
other
members
of
the
team
have
done
so
as
well.
That
is
off
from
bug
triage
and
if
anybody
has
any
questions,
I
will
be
glad
to
any
answer.
A
G
Everyone,
this
savita
I,
will
be
providing
the
dogs
update
today
overall
status,
hello,
and
we,
the
major
change
from
yesterday
to
today,
as
the
interview
pr's
came
down
from
seven
to
one,
and
we
do
have
one
PR
at
risk,
we
haven't
received
any
updates
from
them.
I
guess
we
have
reached
out
to
them,
reach
out
to
seek
a
PR
machinery
personally
and
still
awaiting
response.
A
So
Joe,
let
me
check
out
the
things
really
quick,
so
in
review,
you
have
a
note
that
can
be
merged
by
end
of
day
to
day
a
seven
and
oh,
they
Pacific,
and
this
is
a
capi
machinery.
One
certificate
signing
request
stock
updates
just
to
double-check
a
this
one,
a
still
been
really
technical
here,
but
this
one
is
one
day
past
the
deadline.
Why
did
you
wait?
Did
you
all
decide
to
Allah
to
live
it
a
to
live
it
in.
A
H
H
So
I
didn't
give
much
attention
to
it,
but
today
also
I
see
a
GTM
from
technical
review
as
well
as
from
dog,
so
I'm,
just
waiting
for
another
check
from
sick
dog,
so
yeah
I,
don't
think
it
might
causes
issue.
But
this
one,
the
no
response
one
is
causing
us
issue
from
mice
today.
So
still
no
response
on
that.
Okay,.
A
Okay,
so
that's
that
they
want
the
used
mention.
There
is
no
response
that
is
at
pointer
to
API
server
network
proxy
feature,
and
this
one
they
are
jaws
updating
a
some
existing.
There
is
some
existing
documentation,
Kathy
replied
they.
The
author
of
this
pier,
has
he/she.
They
replied
in
any
way,
shape
or
manner.
No.
H
A
A
A
Beneath
it
really,
if
you
have
some
thoughts
on
this
a
welcome,
but
at
least
on
my
end,
that
is
the
thing
that
I
want
to
talk.
There
is
a
thing
that
I
want
to
double
check,
I'm,
not
sure
if
this
is
like
a
critical
documentation
age,
you
definitely
need
to
do
this,
or
just
we
are
fixing
talking
a
word
fix
in
the
docs
and
just
making
them
look
a
little
bit
better.
A
H
A
smaller
need
so
I
already
see
a
technical,
LG
TM
as
well
as
another
LJ
tiem.
So
I
don't
think
this
a
signing
request.
One
is
a
major
one,
so
I
just
seemed
like
10
minutes
back
also
there
was
some
changes
within
the
beer,
so
yes
link.
The
other
one
is
in
really
in
risk.
The
with
the
CAPM
missionary,
one.
A
A
Yeah
neither
have
I
my
general.
My
feeling
right
now
is
at
least
for
the
sake
api
machinery,
one
it
the
one.
That's
in
review,
I,
don't
I
want
to
echo
what
bin
L
say
and
you
know
they're
worried,
they're
working
on.
It
seems
to
be
more
or
less
approve.
So
just
let
it
go
train.
Let
it
go
through
the
gate.
There
are
no
response,
1
I,
guess
top
would
check
and
see
how
connected
it
is
to
the
rest
of
the
documentation
for
the
enhancement.
A
A
A
J
K
Am
wear,
yellow
still
a
few
more
things
moving
around
so
60
la
will
not
be
able
to
deliver
a
blog,
but
now
SiC
auto-scaling
was
offered
to
write
a
blog,
so
I,
just
I
made
a
list
of
the
current
groups
that
were
still
waiting
to
hear
back
from.
So
there
should
be
one
from
sig
note
to
drumstick
API
machinery,
one
from
sig
network
and
then
say
auto-scaling,
which
is
the
new
one
and
still
working
on
the
release
flag
itself.
K
L
K
K
A
Okay,
you
can
completely
say
no
a
say
no
to
what
I'm
about
to
ask,
but
hey.
Could
you
ask
the
CN
CF
whether
they
be
open
to
having
a
blog
post
for
sometime
a
after
I
mean
I'm
just
making
up
the
timeframe,
but
sometime
in
the
coming
weeks,
to
get
more
day
a
to
possibly
have
more
things
from
at
least
60
Li
in
a
whatever
other
six
want
to
are.
K
A
So
so,
and
so
all
the
blocks
that
you
already
have
that
you
already
have
plan
a
also
a
just
keep
work
and
just
keep
working
on
them
with
the
same
day
with
the
same
timeframe.
But
hey
I
was
wondering
if
we
could
ask
the
CNC
have
two
beside.
Besides
all
the
blocks,
that
we
already
have
plan
to
the
possibility
to
write
a
to
write,
a
feature
report
for
sometime
it
down
the
a
down
the
road
that
is
completely
separate
from
all
it
from
all
the
way
from
all
the
ones
that
we
already
have.
Oh.
C
A
A
If
not
release
French
management
is
there
anyone
from
release
branch
on
the
team
on
the
call,
if
not
I,
think
I
can
give
the
update
their
last
fast-forward
for
these
freely
psycho
was
on
this
morning
us
and
I
at
some
point,
Kota
is
just
gonna
happen.
Hey
whenever
that
actually
happens,
it's
gonna
be
up
to
the
discretion
of
Carlos
and
Sasha.
They
got
to
merge
VR
in
testing
for
I
believe,
but
a
last
time,
I
check
plan
is
for
a
sometime
today
for
some
time
today,
code
that
will
begin.
A
E
C
E
A
E
It's
always
my
moral
quandary
of
pushing
everybody
I
like
to
let
the
release
get
to
the
point
and
not
worry.
You
have
everybody
start
to
think
about
the
next
release
until
we
kind
of
get
this
one
out
the
door,
but
you
know
I
suspect
neither
late
this
week
or
early
next
week
it
will
post
and
then
we
already
have
the
lead
locked
in,
as
you
mentioned
yesterday
for
119
so
from
there,
then
we
can
start
to
do
that,
but
we
need
to
just
make
sure
that
people
are
thinking
about
it
on
the
team.
A
I
I
H
H
J
H
A
A
If
not,
then
we
can
move
forward
so
secretly
released
late
things
and
scalability
things,
economic,
small,
a
milestones
already
mentioned.
That
would
a
talks.
As
we
mentioned
a
working
together
working
to
getting
them
complete,
a
Cota
is
gonna
happen
at
some
point
today,
I
believe
Carlos.
You
spin
me
with
the
PR
the
needs
to
be
a
tan
to
be
lurched
in
order
for
that
to
happen,
a
release
candidate,
getting
ready
to
get
a
get
up.
A
One
way
out
sometime
today
and
I'm
fixing
the
notes
right
now,
because
I
had
a
4:00
tomorrow
endowed
and
given
that
Kota
is
gonna
happen.
That
leaves
us
with
the
same,
cherry-pick
deadline
of
a
distortion,
hopefully
between
today
and
Thursday,
then
tide
pool
is
gonna,
go
down
and
allow
for
whatever
cherry
picks
we
need
to
be
properly
tested,
and,
as
luckylucky
mentioned,
you
need
to
work
on
a
schedule
in
the
retro
finding
someone
from
contracts
to
do.
A
Two
today
to
do
that
for
us
and
scalability
updates,
also
another
a
I
thought
I
need
to
put
down
is
we
need
to
reach
out
to
scalability,
to
ask
for
more
feedback
between
synchronous
and
scalability
on
a
whatever
corporations
are
are
being
tested
for
a
performance
regressions
earn
anything
of
the
sort.
Does
anyone
have
any
comments,
questions
on
a
on
milestones
or
anything
else
they
released
in
related.
A
Sweet,
if
not,
we
can
end
this
call
early.
Thank
you
very
much
for
attending
and
as
I
mentioned,
I'm
gonna
stop
recording.
But
if
anybody
wants
to
stay
in
zoom
and
hang
out,
a
synchronicity
I'm
gonna
have
a
call
for
the
rest
of
the
day.
So
people
can
just
stay
here
and
just
a
here
in
chat,
but
I'm
gonna
stop
recording
right
now
and
thank
you
very
much
for
everyone
for
everyone
for
attending.