►
From YouTube: Kubernetes 1.17 Release Team Meeting 20191113
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
And
it
looks
like
we
are
live
good
morning
afternoon
evening:
everybody,
it
is
at
least
in
this
part
of
the
world
Wednesday
November
13.
It
is
the
eighth
week
of
the
kubernetes
117
release.
This
is
one
of
our
Wednesday
burndown
meetings.
My
name
is
Guinevere.
Sankar
I
will
be
your
host
Danny.
Please
treat
each
other
with
kindness,
as
we
are
unrecoverable
on
place,
your
name
in
the
attendance
sheet.
B
Good
morning
afternoon,
/
evening,
everyone
so
we
are
currently
yellow.
Actually
we
might
be
green,
yellow
and
red.
We
will
discuss
about
it.
Sometime
later,
we
are
currently
tracking
35
enhancements
and
out
of
the
15
enhancements
are
at
risk,
mostly
because
they
have
open
PRS
and
since
only
2
days
are
left
to
code
freeze,
there
is
limited
reviewer
bandwidth
and
we
have
started
reaching
out
to
all
the
enhancement
assignees
about
the
impending
code
freeze
and
to
help
them
have
already
reverted
back
saying
they
might
not
be
able
to
make
it
by
the
code.
B
A
A
A
C
C
This
from
our
stats
from
the
116
released,
almost
half
were
removed,
either
deferred
or
kicked
out.
So
we're
not
too
far
off
from
that
benchmark.
Good.
A
E
I'm
curious
about
two
things:
one:
how
many
of
these
are
carryovers
from
the
previous
release
and
two
are
the
same
SIG's
having
the
same
problems
with
reviewer
and
approve
annual
flight?
Is
there
data
that
we
can
use
be
like
y'all
need
more
approvers?
You
all
need
to
get
more
people
going
in
your
sig,
because
I
think
that
would
be
like
a
really
good
metric
for
the
embassy.
We.
C
Don't
have
a
good
compiled
list
of
that
stuff.
There's
some
information.
It's
like
going
back
to
the
previous
spreadsheets.
We
can
find
you
know,
features
and
and
manually
map
them
to
our
the
current
ones,
but
it'd
be
essentially
a
bunch
of
manual
reconciliation.
I,
hear
you're
good
at
that
yeah,
but
that's
a
post,
cube
contest
for
me.
F
C
C
C
A
Other
than
that,
we'll
do
some
milestone
chopping
at
the
end
of
day
tomorrow,
I'm
happy
to
do
that
as
I
sit
at
the
western
edge
of
the
time
zones
very
cool,
so
I
also
saw
some
disturbing
news
from
CI
signal.
G
All
hell
breaks
loose.
This
is
great.
Oh
yeah!
It's
it's
actually
yeah.
What
we're
read
right
now,
but
it's
it's
I
would
say
it's
like
very,
very
simple
Aries.
So,
like
12
hours
ago,
there
wasn't
much
that
basically
much
of
PR
and
kubernetes
that,
like
restructured
the
license
files
with
which
basically
like
open
like
the
health
room
in
all
the
jokes,
so
there's
like
pretty
much
all
the
jobs
as
I
read
right
now
are
because
of
that.
So
there's
like
a
test
startup
issue.
G
A
A
Okay,
thanks
bug
triage:
this
is
the
best
I
love
it
I'm
not
needed,
no,
never
mind.
Let's
see
from
bug
triage.
F
A
Let's,
let's
give
him
a
couple
minutes
and
let's
hear
from
Doc's
instead,
but
can
we
can
run
back
later?
Anyone
here
from
dogs.
D
So
yes,
we
agree,
and
the
update
is
that
we
have
37
enhancements
happening
right
now
and
we
have
14
merge
two
already
and
considering
the
deadline
of
ready
for
review
on
November
15th.
We
have
two
days
from
now,
so
we
have
2l
already
ready
for
review
and
we
have
11
in
draft,
so
out
of
11
I,
see
again
7
peers
at
risk
for
code
freeze
tomorrow.
So
it's
a
bit
of
chaos
for
us.
So.
A
A
D
A
F
You
sorry
about
the
confusion
for
non-open.
Excuse
me
open
non-test.
We
are
at
11:00
that
is
down
one
from
last
meeting
priority
critical
urgent.
We
are
holding
it
to
no
change
priority
important
soon.
We
are
at
five
that
is
down
one
for
PRS.
We
have
open
PRS
33.
That
is
up
six
from
our
last
priority,
critical,
it's
holding
at
three
no
change
priority,
important
18,
no
change
and
open
KK
issues,
including
Tessa
and
flakes
that
is
26.
That's
down
seven.
F
A
A
H
A
H
A
A
Cut
on
Monday
so
beginning
of
coupe
con,
we
are
also
releasing
a
branch.
So
that's
how
that'll
be
pretty
exciting
man
I
feel
like
this
is
a
missed
opportunity.
We
should
have
just
done
this
live
at
coupe
con
in
a
session
that
contributor
summit,
Wow
I
can't
believe.
No
one
thought
of
that.
That's
that's!
That's
very
sad!
Anyway.
Moving
on.
A
Clear
and
there
just
lead,
no
updates
from
me
awesome
thanks
I
have
the
usual
updates.
Oh
I
actually
do
have
a
couple
of
a
couple
of
things
to
think
about.
So,
first
of
all,
it
is
coupe
con
next
week
on
Monday
and
there
will
be
no
release
team
meeting.
It
is
the
contributor
summit
and
there
is
just
not
really
a
good
way
for
us
to
have
a
meeting
on
Wednesday.
A
We
will
have
a
meeting
and
it
is
okay
if
we
have
a
skeleton
crew,
but
I
will
attempt
to
have
the
meeting
on
Wednesday,
but
not
on
Monday
the
week
after
is
Thanksgiving,
I
haven't
quite
figured
out
what
the
schedule
will
look
like,
but
we
will
most
definitely
not
have
a
meeting
the
Friday
after
Thanksgiving
or
well.
I,
don't
know
about
most
definitely
but
I'm
I'm
tending
towards
no
again
I
apologize
for
the
extreme
us-centric
ness
of
this
of
this
of
these
release
meetings
we
might
anyway
I'll
think
about
the
Thanksgiving
week.
A
A
F
A
I'll
definitely
try
and
make
that
happen.
It's
going
to
be
like
the
larger
coop
calm.
So
I
don't
know
if
I
can
just
randomly
book
a
conference
room,
but
you
know
maybe
we
can
hijack
the
speaker
lounger.
Oh
that
sounds.
Maybe
maybe
we
can
hijack
a
corner
somewhere
and
just
sort
of
yeah,
we'll
see
we'll
see
what's
possible.