►
From YouTube: Kubernetes 1.18 Release Team Meeting Burndown Meeting
Description
Kubernetes 1.18 Release Team Meeting Burndown Meeting
A
A
If
there
is
anyone
who
wants
to
take
notes
for
a
trial,
this
call,
please
feel
free
to
add
your
name
as
a
note
as
a
official
top
taker
and
before
we
get
started
like
always,
I
need
to
I
have
to
mention
that
we
have
a
data.
Coburn
ADEs
community
has
a
code
of
conduct
which
essentially
well
done.
Please
be
nice
to
each
other,
be
kind,
and
with
that
let's
get
started
with
enhancements
John.
Please
take
it
away
great
thank.
B
You
so
since
I
think
Monday
when
we
were
last
here,
the
we've
had
a
couple
more
people
drop
out.
It
has
to
drop
out
of
the
release,
we're
tracking
45.
Now
20
of
those
are
at
risk
and
we've
pinged
everybody
on
github
and
most
people
I
think
on
slack
as
well.
So
we
need
to
go
through
and
see
if
we've
got
many
more
responses
to
any
of
those,
but
essentially
yeah
25.
A
C
C
This
don't
be
sudden
investigation,
so
we're
waiting
response
from
CLI
team.
Hopefully
we'll
get
read
this
this
week
we
have
many
jobs.
Failing
in
massive,
informing
deceive
course:
master
serial
there
are
two
participant
fixes
opened
one
of
those
is
merged,
so
we're
hoping
also
to
just
hope
to
be
fixed
as
well.
We
have
the
deceive:
witness,
2019,
good
energy
master,
which
is
like
a
work
in
progress
test.
C
This
would
have
also
at
least
opened
to
mention
the
conformance
test
to
release
blocking
jobs
and
criteria.
You
could
take
down
to
our
adults
that
are
failing
because
of
Windows
problem.
There's
an
issue
opened
in
their
dust
port.
Also,
there
is
in
2090
master
job,
there's
one
CLI
this
case.
That
is
failing
and
I
open,
another
issue
for
it.
Hopefully,
after
the
the
fix
of
the
witness
problem,
would
be
merged,
those
jobs
would
be
fixed
and
only
the
CLI
problem
would
remain
bill
package
steps.
C
Okay,
this
is
failing
because
of
the
one
point
anything
sir
I
tools
doesn't
exist.
Yet
I
would
refer
this
comment
from
from
help.
You
could
say
here
in
the
release:
misc
a
test
part
only
five
finicky
jobs,
nothing
to
worry
about
those
reported
from
disputable,
1.18
blocking
it's
actually
the
same.
One
job
is
felling.
It's
like
the
same
result
like
master
blocking
job.
The
latest
cube
City
all
still
waiting
for
their
CLI
team
to
be
respond.
C
Also
in
the
1.18
informing
though
the
serial
this
eCourse
will
is
better
serial.
This
is
the
petitioner
fixes
well
up
in,
like
the
same,
which
is
the
same
reason
with
a
master
blocking
job
muscle
informants
of
glory
and
also
we
need
to
cherry-pick
these
fixes
through
1.80
brands.
I
left
a
comment
in
the
AP.
Are
so
hopeful?
C
C
Ok,
so
I
some
flick
jobs
here
in
the
pre
summits,
where
it
is
blocking
dust
where
there
are
few
few
flaky
test
cases
that
other
investigation,
most
of
them
are
like
the
series
you
see
it
so
preserve
meat.
There
are
three
different
test
cases
that
are
still.
There
are
flaking
a
lot
and
there
are
some
investigate
some
missus
open
forums,
and
there
are
some
potential
fixes
open
as
well
and
pool
of
apparatus
verify
there
is.
C
C
Didn't
to
monitor
the
top
and
see
if
it
will
be
see
flaky
also,
there
are
some
other
test
cases
that
are
flaking
time
to
time
and
there
are
certain
two
different
sources
like
a
cuckoo
bird
good
to
see
and
I
tweeted
the
CI
to
see
so
the
industry
is
opened.
There
are
many
cases
are
flaking,
and
this
is
not
an
investigation.
A
Couple
questions
from
so
from
the
bay
from
the
Muslim
forming
a
dashboard
in
the
grand
scheme
of
things
it
seems
like
other
than
the.
So
there
is
a
master
CA,
there's
a
master
serial
issue
and
other
than
that.
Most
of
them
are
Windows
related
mmhmm
yeah,
the
windows
related
ones.
Is
it
a
governance
issue
on
how
kubernetes
a
supports,
uses
wind,
a
windows
or
is
strictly
a
windows
issue?
Do
you
know.
C
I,
don't
have
any
clue.
It
seems
that
it's
like
Windows
issue
because
it's
they
opened.
They
swing
their
dashboard
as
well,
and
there
are
some
PR
something
for
to
fix
them.
I,
don't
know
more
details.
I
can
try
to
get
in
touch
with
them
after
the
meeting
and
kind
of
some
details,
because
this
is
really
really
that
of
actually
is
is
failing,
like
many
many
days
like
more
than
a
month
right
there.
So
we
explode
like
all
these
windows
problem.
We
have.
C
The
master,
reforming
dashboard
looks
good
no,
but
still
we
need
to
fix
them
right.
Iii
I
tried
to
ping
there's
possible
that
this
is
working
on
one
of
the
windows,
job
that
it's
like
working
progress.
I've
I
tried
to
ping
him
no
response
yet
so
I
try
to
pick
him
in
slot
as
well.
Then
say
it's
like
the
progress
there
was.
D
A
So
closing
remark
for
that
one
I
might
be
super
a
might
be
useful
to
know
whether
it
is
covered
a
whether
any
of
these
are
covered.
A
strictly
kubernetes
failures
testify
issues
or
some
isolated
wind,
a
windows
issue,
as
we
get
closer
to
confess
I,
just
don't
know
whether
we
shall
delay
covet
or
to
something
special.
A
And
let's
see
what
was
the
only
other
comment
that
I
had
it
that
I
heard
of
mine
a
wanted
to
say
thank
you
for
adding
the
flaky
jobs
from
the
piece
of
meats
and
super
useful,
a
super
useful
to
help
those
in
there,
especially
because
I'm
pretty
sure
that
we
get
into
countries
we're
gonna
have
a
humongous
to
a
PRQ
put
other
than
that.
Does
anyone
have
any
more
comments?
Questions
suggestions
come
once
twice:
Thank
You
Niko,
the
next
stop
dr.
Josh.
E
Martin
good
morning,
everybody
afternoon
evening,
unhappy
Friday
for
open
non
test.
We
are
down
one
from
our
last
meeting
to
2500
sorry,
we're
current
status
is
yellow
by
the
way
for
priority
critical,
urgent
issues,
we're
remaining
the
same
to
open
for
priority
important
soon.
We
are
remaining
the
same
at
12
for
open,
KK
PRS.
We
are
up
to
234
and
priority
critical
urgent.
We
are
remaining
the
same
at
one
priority
important
soon.
We
are
up
to
222
and
for
all
open
KK.
We
are
remaining
the
same
at
43.
I.
E
A
E
Out
to
cichlids
about
just
on
issues
that
were
not
reading
response
on
so
now,
we'll
start
increasing
the
frequency
to
the
leads
to
say:
hey
we're
right
at
code
freeze.
We
need
to
a
response
on
this
well
good.
That
might
be
interesting.
Let's
see
how
responsive
everyone
is
last
release,
they
were
pretty
responsive,
so
I
feel
fairly
good
about
that
sweet.
F
F
F
G
So
I'm
gonna
work
with
my
two
shadows:
to
figure
out
we're
gonna,
scrape
the
list
and
see
which
ones
are
relevant
to
which
cigs
and
hopefully
figure
out
the
last
two
cigs
caps
for
this
release
and
then,
when
we're
done
with
that,
we
will
finally
vote
on
the
topics
for
the
blog,
so
I'm
hoping
but
up
either
by
today
or
a
Monday,
so
we're
yellow.
That's
it.
Thank
you.
G
A
G
G
G
It's
definitely
an
option.
I
feel
like
using
the
enhancements
list
is
like
actually
like
a
very
good
suggestion,
though
just
cuz
like
a
lot
of
the
work
has
been
chopped
elsewhere
and
like
there's,
like
that's
one
of
the
things
like
we're
working
on
right,
it's
just
like
figuring.
How
does
she
mind
stuff
and
like
not
necessarily
do
you
duplicate
work,
so
I
mean
I,
feel
like
going
through
that
list
and
like
it
already
lists
which
cigs
are
responsible
for
it.
G
I
think
that's,
probably
one
of
the
quickest
ways,
because
it's
not
necessarily
trying
to
like
get
an
answer
from
a
specific
person
more
so
that
the
information
we
get
from
these
people
are
usually
the
links
to
the
issues
anyway
and
you're
already
tracking.
That
so
I
feel
like
that's.
Actually
like
the
quickest
shortcut,
yeah
and
I
mean
the
networking
is
definitely
helpful.
Is
law
I
mean
I,
feel
like
even
just
talking
to
you
and
you
giving
us
suggestions
was
like
very
useful
yeah.
D
A
H
So
yes,
so
we
have
a
deadline
today,
as
a
dogs,
placeholder,
PR
and
I'm,
not
sure
we
are
in
Red
Door
I
look
but
definitely
like
we
are
wrong.
Like
five
enhancements
are
like
we
need
to
get
like
if
I
updated,
the
links
to
the
five
enhancements
which
have
no
rocks
placeholders
because
in
place
at
this
point
of
time,
so
I
have
four,
as
they
told
me
that
initially
they
need
dogs.
H
The
total
they'll
be
good,
putting
the
placeholder
PR
just
by
the
deadline,
but
they
fail
to
do
it
so
I
personally
reached
out
to
him
them,
but
I
do
see
no
response.
There
are
four
enhancements
and
one
is
in
blog
post
versus
official
user-facing,
Docs
and
rec
AIDS
website,
so
that
is
still
in
unknown,
so
total
five
enhancements,
which
are
which
don't
have
any
place
for
this
PRS
today.
A
E
A
A
A
Don't
hear
anything
and
don't
see
any
names
and
emerita
slit-like
is
that
online
right,
yeah,
so
I
guess
we
jump
all
the
way
to
my
update,
which
other
than
everything
that
has
been
mentioned
again
just
a
reminder.
Today's
the
deadline
for
hoping
placeholders,
a
ok,
placeholder
pr's
and
the
big
thing
for
the
a
one,
a
one
of
the
biggest
things
for
the
entire
release
code
phrase
is
gonna,
be
Thursday,
which
hopefully,
a
channel
are.
A
Getting
reminders
of
this
all
over
the
place,
but
still
a
good
to
have
another
one.
I
have
another
one.
In
this
meeting,
a
six
color
bill,
advice,
I
haven't
heard
and
a
anything
from
them.
So
hopefully
things
are.
Hopefully
things
are
still
looking
good
and
does
anyone
have
any
comments
for
a
delete
team,
myself,
Bob,
Taylor
or
scalability
wise?
Then
we
can
pass
on
or
someday
run
it,
and
then
you
want
to
discuss.
A
10
months
points,
okay,
so
with
that,
thank
you
very.
Thank
you
very
much.
Everyone
for
attending
this
meeting,
like
always
I'll,
make
sure
to
curate
the
this
document,
to
make
sure
that
we
have
all
the
information
that
we
and
that
we
need
for
everyone
to
every
day
for
everyone
to
do
their
thing
and
for
anyone
who
wasn't
available
to
join
this
call
to
keep
up
with,
what's
going
on
in
their
release,
team
and
other
than
that
and
I
want
to
wish
you
all
happy
Friday.
Thank
you
very
much.