►
From YouTube: Kubernetes 1.17 Release Team Meeting 20191125
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
Good
morning,
everyone
it
is
that
Monday
after
coupe
con
and
I
am
a
horrible
release
lead.
Actually,
that
was
a
joke.
Thank
you,
everyone
for
being
here,
the
Monday
after
cube
con.
This
is
week
10
of
the
117
kubernetes
release.
My
name
is
Guinevere.
Sanger
and
I
will
be
leading
this
meeting
today.
A
Welcome
everyone.
Please
put
your
name
in
the
attendance
sheet
and
adhere
to
our
code
of
conduct.
I
have
a
couple
things
to
say
right
at
the
start
of
this.
This
is
our
first
week
of
daily
burn
downs
and
we're
going
to
talk
a
little
bit
later
about
what
that
means.
For
those
of
us
who
live
in
the
u.s.,
or
rather
what
that
means.
For
those
of
us
who
do
not
I
see
a
chat
message.
Okay,
thank
you.
Mark
II.
There
is
a
lazy
link
in
the
chat
and
with
that,
let's
hear
it
from
enhancements.
B
Sorry
I
was
typing
something,
so
enhancements
is
largely
green
still.
We
have
no
real
status
things
to
update
22
track
things
for
alpha
or
beta
14
stable,
went
through
today
to
see
if
anything
had
dropped
out.
While
we're
at
coop
car
seems
like
everything
is
still
going
along
as
planned.
A
couple
of
things
have
docks
that
haven't
merged.
Yet
what
can
they
have
docks
update
on
that
I
have
the
numbers.
If
we
want
to
circle
back
on
that
after
after
Cox
goes,
that's
pretty
much,
it.
C
Oh,
we
are
mostly
green
muscle
blocking
us
to
flake
eat
us.
Marcin
farming
is
bad
son
flaky
to
failing,
but
117
blocking
is
all
green
and
117,
and
farming
just
has
one
flaky
test
and
then,
like
Elina,
wrote
this
document
both
in
the
chat
and
it's
also
linked
with
a
release
stock,
which
has
most
of
the
updates
for
her.
A
Check
that
out,
thank
you
also.
Your
background
is
incredible.
I'm
really.
That
was
that's
amazing
for
all
those
who
cannot
see.
This
is
a
perfect
moment
to
say.
D
A
E
Hi,
it's
Kirsten
just
for
recording
for
bug.
Triage
we've
seen
a
couple
PR
like
we've
seen
one
PR
close
that
was
from
last
week,
but
everything's
still
kind
of
holding
steady,
I
marked
it
as
yellow,
but
it's
like
an
optimistic
yellow
so
because
I
added
some
notes
so
like
for
the
critical
urgent
issues
to
have
open
PRS
one
is:
has
the
PR
that
was
merged.
So
it's
waiting
to
close.
So
those
are
almost
closed,
the
important
one.
It
was
just
one
issue
that
was
reopened
to
cherry-pick
and
then
for
the
PRS.
E
There
are
three
that
are
waiting
for
final
approval
and
then
three
for
the
important
soon
that
are
waiting
for
final
approval
and
then
out
of
the
all
open
kubernetes
issues
to
our
I
think
DIMMs
requested
that
they
were
be.
It
would
be
relabeled
as
not
blockers
and
then
the
other
ones
like
correspond
to
PR.
So,
even
though
there
are
PRS
open
and
there
are
issues
open
like
they're,
all
kind
of
just
waiting
for
that
final
push
either
to
be
cherry
picked
to
be,
you
know,
finally,
approved,
etc,
etc.
A
Alright,
thank
you
so
much
for
for
the
report
and
for
going
into
details
about
the
particular
issues.
This
is
definitely
something
we
should
keep
an
eye
on
this
week,
but
it
is
also
the
thing
that
we
are
solving
for
in
the
last
few
weeks
of
the
release
cycle.
So
thank
you
so
much
Kirsten
any
questions
about
many
of
those
specific
issues.
A
A
F
Chris
tells
me
and
he's
going
to
be,
sending
out
the
known
issue
reminders
today
to
the
six,
so
he
wasn't
able
to
join
for
this
call
but
said
that
will
be
happening
today
and
other
than
that
we
are
green.
We
are
good
and
we
were
excited.
A
Yay
I'm
really
excited
to
reminder
that
we
should
get
started
on
that
blog
post.
So
that's
a
collab
between
release,
notes
and
comms
to
make
sure
that
we
all
talk
about
all
the
right
things
and
you
know
warn
everyone,
but
also
like
show
everyone
what
a
cool
stable
release
we've
got.
So
thank
you.
Any
questions
for
release
notes.
G
A
H
A
A
I
I
So
don't
expect
anything
this
week,
but
it'll
probably
come
out
of
sometime
next
week
and
yeah.
If
any
folks
need
to
reach
out
because
they
have
questions
about
what
they
want
to
do
for
the
next
release
cycle
or
any
other
feedback.
You
would
like
to
provide
you'd
rather
give
directly
to
myself
or
Quinn
feel
free
to
us.
A
A
Okay,
everyone
started
thinking.
Next
is
me:
I
have
a
few
updates
off
the
top
of
my
head,
I
already
mentioned,
rc1
was
released
on
Friday
coda
is
enabled
masters
being
flooded
with
things
that
we
should
not.
Most
of
them
be
worried
about
things.
To
think
about
this
week
is
making
sure
the
docs
merge
any
time
that
we
come
up
with
a
cool
release.
Blog
post
between
coms
and
release,
notes
and
I
will
help
with
that
as
well.
A
We
should
make
sure
to
proofread
a
lot
and
avoid
any
weird
phrasings,
confusing
phrasings
and,
of
course,
typos
think
about
your
next
means.
What
did
I
forget?
Yes,
alright
for
many
of
us
this
week
is
us
Thanksgiving.
However,
I
believe
we
have
enough
folks
on
this
team
to
have
a
stand
up
at
the
least
on
the
Friday
after
Thanksgiving.
So
let
me
go
into
a
grid,
lock,
grid
mode
and
see
a
show
of
hands.
I
am
going
to,
let's
see
who
is
there?
A
Anyone
who
is
planning
on
being
here
on
Friday
I
was
not
planning
to
be
on
here,
but
I
will
be
if
I
cannot
forget.
One
of
my
leads
to
lead.
Instead
I
was
hoping,
Maria
would
take
it,
but
it
seems
she's
on
vacation
this
week.
So
I'll
get
back
to
you
on
who
will
be
hosting
someone's
nodding.
That
looks
like
the
pivotal
office.
A
Confirming
I
appreciate
it
all
right,
it
looks
like
we
have
critical
mass
for
Friday.
Does
anyone
feel
the
need
to
have
daily
burn
down
on
Thursday
I?
Don't
want
to
be
us
specific.
So
if
there's
enough
of
us
who
do
not
celebrate
Thanksgiving
that
day,
we
should
have
a
meaning
again.
I
will
definitely
not
be
there
on
Thursday.
A
Okay,
wait:
two
yeas
lots
of
hands
for
definitely
nay,
definitely
new,
all
right,
okay,
so
I'm
gonna
go
capybara,
shrug
on
this
one
and
definitely
the
top
up
turned
down
on
Friday
and
we
can
all
take
a
break
on
Thursday.
Hopefully
most
of
these
burn
guns
are
going
to
be.
You
know
ten
minutes
just
checking
in
that.
A
So,
let's,
let's,
let's
see
I,
think
we
can
do
it
without.
In
fact,
things
have
gone
fairly
smoothly
so
far
that
having
the
having
the
in-person
check-ins,
almost
almost
I,
don't
wanna
jinx
it,
but
almost
feels
a
little
bit
like
overkill
at
this
point.
I
don't
want
to
be
too
confident,
however,
alright.
A
A
Alright,
let
me
read
up
the
sixth
capability
update
I
will
make
sure
that
someone
attends
their
sick
meeting
at
their
next
sick
meeting,
just
because
we
are
nearing
release
date
and
we
want
to
make
sure
that
we
don't
have
any
delays
they
mentioned.
They
had
some
failures
on
GC
scale,
correctness
and
the
GC
scale
performance,
but
all
of
them
were
flakes.
You
should
still
double
check
on
that.
A
A
Ok,
so
with
that
we
should
walk
the
board,
but
before
we
do
so,
I
am
thinking
that
this
releases
theme
it
might
not
do
really
like
that.
Disappointment
feel
like
after
cube.
Con
is
a
good
time.
I
feel
like
this
should
be
the
chillest
release
because
listen
everyone,
it's
just
code.
It's
just
code,
all
right.
A
This
will
be
the
chillest
release
and
our
mascot
will
be
the
capybara
because
it
gets
along
with
everyone,
and
so
yeah
I
will
come
up
with
something
cool
I
do
not
have
a
design
yet,
but
let
the
memes
fly
and
perhaps
inspiration
will
strike,
but
so
far
I
wanted
to
thank
everyone
for
being
super
chill
and
super
helpful
and
just
making
this
making
this
and
relaxing
as
much
as
it
can
be
experience
for
everyone.
Thank
you
all
right,
switching
gears
from
relaxing
to
going
through
the
board,
which
is
not
relaxing
at
all.
A
Where
is
where's
the
board
project.
I
know
it's
project
number
29,
because
I
only
ever
have
to
type
29
into
my
search
bar.
A
Can
everyone
see
my
screen?
Okay,
let's
go
and
see
if
there
is
new
things,
new
things
release
notes,
draft
is
open
and
presumably
being
worked
on.
It
has
a
hold
on
it.
So
that
means
it
is
review
in
progress
and
then,
let's
pull
that
over
here
fix
broken
links,
has
an
LG,
TM
and
I.
Don't
know
what
that
is,
but
and
house
analogy
TM.
So
let.
G
A
A
Still
can't
take
my
fingers
broken
and
yep
not
broken
it's
but
yeah
anyway,
but
I
can't
use
it
perfect.
So
what
I'm
gonna
do
is
I'm
going
to
girl
and
I.
G
A
G
A
I
expect
that
a
lot
of
this
is
going
to
get
punted
for
next
week
because
of
coop
con,
so
it
was
really
great
seeing
some
of
you
at
coop
common,
really
sad,
not
seeing
some
of
you
at
Q
Khan.
But
honestly,
you
people
are
why
I
love
coop
con
and
there's
just
yeah.
That's
that's
just
a
reason
to
alright.
A
A
A
That's
really
cool.
Thank
you.
Any
improvement
that
we
can
get
well
take.
Thank
you
so
much
so,
let's
leave
it
open
document.
Kubernetes
released
he
membership
criteria.
I
did
I
did
some
work
in
my
head
because
I
was
giving
a
talk
about
this
last
week,
so
that
will
definitely
help
me.
Do
some
work
that
everyone
else
can
read
on
here.
A
A
M
A
A
A
A
G
A
One
hit
any
boxes:
I'll,
do
it
I
believe
him
I,
just
they're
all
really
really
busy.
So,
however,
speaking
of
retrospective,
we
should
open
a
117
retrospective
dock
and
I'll,
make
sure
that
happens
sometime
this
week
and
watch
the
channel
for
that.
Take
notes.
Think
about
everything
you
all
want
to
say
for
the
retrospective
and.
A
A
A
A
I
haven't
seen
any
incoming
PRS
on
the
dock
release
handbook
this.
This
issue
is
good
to
have
in
here
by
the
way,
as
a
reminder
that
everyone
should
keep
updating
their
handbooks
as
they
go
if
there
is
a
flurry
of
docks
of
documentation,
a
handbook
documentation
updates
at
the
end
of
a
release
cycle.
That
is
a
good
thing.
Some
of
the
timelines
are,
of
course,
always
a
little
squishy,
because
every
release
has
a
slightly
different
timeline.
A
A
Not
done
these
okay,
we
have
not
really
well
we've
kind
of
done
this,
but
we
need
to
make
sure
that
we
follow
up
with
them.
Six
scalability
has
been
really
good
about
giving
us
a
written
update
every
week.
We
do
need
to
make
it
a
habit
to
send
it
when
these
team
representative
to
ther
meetings
I,
believe
that
is
the
correct
way
to
engage
with
them
and
have
that
be
the
expectation
on
both
sides
that
would
be
yeah.
We
have
to
be
yeah
short
of
creating
a
six
scalability
role
on
the
release.
A
D
I
think
your
assessment
spot
on
there
and
it
would
be
reasonable
to
on
milestone
this
I
think
for
117
and
call
that
part
done
like
you
can
give
the
give
a
boot
check
to
the
first
bullet
there.
The
for
117.
Like
that's
happened,
we
got
to
decide
what
we
do
in
terms
of
changes
to
handbooks
for
going
forward,
but
could
unwell,
stone
and
assign
it
to
Stephen
and
I.
Okay,.
A
Yeah,
let
me
I'm
just
putting
it
in
my
other
screen
just
because
I
might
waste
everyone's
time,
checking
up
block
thanks,
ten
awesome
and
then,
and
we
have
a
really
exciting
one
Jack
enhancement
slip
across
multiple
releases
and
I
know.
There's
been
work
being
done
on
this,
so
I'm
moving
not
to
in
progress
unless
somebody
says
no
wait.
Stop
to
me
right
now.
Nope.
B
A
A
A
Okay,
all
right
awesome
after
everyone
has
watched
me
grope
for
this
job
share
button.
Do
we
have
any
last
minute
words.