►
From YouTube: Kubernetes 1.17 Release Team Meeting 20191115
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everyone
welcome
to
another
lovely
burn
down.
This
is
November
15th.
There
is
a
cat
in
front
of
me
and
I
can
barely
see
the
screen
just
want
to
remind
everyone
that
this
is
being
recorded.
So
this
is
super
embarrassing
and
make
sure
that
your
excellent
to
each
other
and
kubernetes
codes
conduct
one
thing
really
quick,
just
a
reminder:
there
will
not
be
a
release
meeting
on
Monday
I,
don't
remember
what
day
it
is
I
think
it's
the
19th
so
from
something
18.
Thank
you
yeah.
A
So
please
don't
join
zoom
caulk,
because
no
one's
gonna
be
on
it
or
you
know
a
couple.
People
might
be
on
it,
but
yeah
there's
not
a
meeting
on
Monday.
What
I'm
getting
at
cat
is
super
distracting.
Please
put
your
name
in
the
attendees
list
and
notes:
I
will
lazy,
link
them
again
in
the
zoom
chat
and
with
that
Bob
or
actually
Jeremy?
Kick
it
off
hey.
B
What's
up
happy
Friday
for
coop
con
super
exciting
code
freeze
happened
yesterday,
so
this
should
be
like
the
most
stable
of
the
updates.
From
from
here
going
forward.
We
went
ahead
and
removed
everything
from
the
milestone
that
didn't
meet
all
the
requirements,
and
that
leaves
us
with
20
tracked
items,
four
of
which
are
going
to
be
new
alpha
features,
three
of
which
we
graduating
beta
and
13
will
be
graduating
to
stable
I
dropped.
All
of
the
things
we
removed
from
the
milestone,
the
things
that
people
specifically
asked
to
defer.
B
B
Two
of
them
missed
LG
TMS
because,
like
they
had
been
approved
an
LG
TM,
but
then
things
pushed
to
them
that
dismissed
the
flag,
so
they
weren't
able
to
to
be
merged,
and
then
one
had
an
unmerged
PRS
like
everything
else
was
finished,
but
there
was
a
PR
that
flips
the
feature
gate
from
false
to
true,
because
it's
going
to
beta
that
didn't
get
merged.
So
we
removed
that
from
the
buy
also
as
well
we've
gone.
B
A
B
Yeah,
like
this
week,
is
kind
of
slow
for
me,
so
it's
been
good
times.
There's
a
there's,
a
like
a
pretty
good
pattern
of
things
that
have
slipped
from
one
release
to
another,
and
a
lot
of
them
urges
like
things
not
getting
finished,
but
I
should
have
it
done
by
ended
today.
So
hopefully
I
can
share
it
next
week.
Really
that.
D
Hey
everyone
happy
Friday
yeah,
it's
not
the
most
stable
one
for
us
for
now,
but
we're
definitely
in
my
third
flight
annular
and
on
Wednesday.
So
the
infrastructure
issue
that
we
had
was
like
the
tests
not
even
like
starting,
they
are
resolved,
but
we
still
have
like
a
lot
of
red
in
the
indie
master,
affirming
there's
like
seven
failing
jobs
that
are
like
failing
constantly.
There
are
like
identified
like
free
issues,
I
reached
out
to
the
six
and
pretty
impressed
how
how
fast
they
are
with,
like
all
the
reverts
and
everything
so
yeah
things
are.
D
A
D
So
far,
like
I'm
waiting
for
response
from
six
storage,
I
think
all
the
other
guys
were
like
super
responsive
I,
even
like
talked
with
the
six
scalability,
because
we
had
like
issues
with
them
in
the
past
and
the
jobs
that
are
around
scalability
are
like
not
really
like
constantly
failing,
but
there
are
like
more
red
that
I
would
like
to
see
them
and
they're
like
super.
On
top
of
that,
they
are
like
investigating
the
the
possible
fixes
and
I'm
pretty
I'm,
pretty
happy
with
their
involvement.
D
E
Josiah
for
bug
triage
today
we
have
removed
all
issues
and
pr's
that
aren't
going
to
make
the
release
since
its
code
freeze,
so
we're
left
with
six
issues.
One
of
those
is
our
release.
Docs
and
the
other
four
critical
urgent
release
blocking
issues
and
the
remaining
one
is
potentially
a
release
blocking
issue.
E
So
that's
these
critical
urgent
issues
have
matching
PRS
critical,
urgent
PRS,
so
everything
seems
to
be
in
line
with
later
cherry
picks,
but
we
have
12
open,
PRS
total,
so
the
remaining
ones
have
left
in
the
milestone,
because
four
or
five
of
them
are
blocked
by
what
looks
like
a
flaky
container
D
test.
So
I
think
the
github
issue
to
that
and
their
release
notes
so
I'm
going
to
give
that
some
time
to
resolve,
there's
a
few
more
that
are
just
waiting
for
like
a
retest
or
an
approved
or
an
LG
TM.
E
F
E
C
G
You
guys
had
steady
talking
for
Christie,
so
we're
all
green
everything's
up
to
date.
We
just
have
to
hopefully
with
all
the
cute
Kong
kind
of
mess,
when
I
try
to
I'm
gonna
try
to
get
out
the
next
patch
for
the
notes
before
Monday,
but
we
have
to
kind
of
go
Wednesday,
but
hopefully
my
try
to
get
that
done
before
Monday.
So
we
don't
have
to
do
a
busy
work
from
them,
otherwise
that
we're
opening.
H
A
A
A
A
F
I
have
I,
have
one
update,
I
just
open
up
here
against
against
release
schedule.
I
originally
had
daily
burn
down
starting
this
coming
Tuesday,
that's
a
mistake.
It
should
be
the
week
after
cube
con.
So
if
anyone
has
extra
cycles,
please
approve
that.
Then
I
had
a
question
for
branch
management
who
learned
he
or
so.
Maybe
if
there
is
somebody
who
can
help
I
want
to
know,
because
I'm
actually
not
clear
on
this.