►
From YouTube: Kubernetes 1.17 Release Team Meeting 20191106
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
A
These
are
mid
week
in
between
meetings
between
our
main
Monday
morning,
meeting
just
to
keep
track
of
things
that
need
more
immediate
attention
and
to
give
more
quick
or
updates,
because
we
are
nearing
code
freeze
and
the
end
of
the
release
cycle,
reminder
to
everyone
that
we
are
under
the
kubernetes
code
of
conduct.
Do
all
the
things
you
would
normally
do
and
without
further
ado,
my
name
is
one
of
your
Sanker.
I
will
be
the
host
today
and
I
would
love
to
hear
from
Bob
about
enhancements.
B
Linen
and
no
real
change
since
Monday
we're
still
sitting
at
44
or
with
12
alpha
13,
beta
and
19
stable.
At
this
point
we
have
pinged
all
the
enhancements.
Just
with,
like
you
know,
general
reminder
the
code
freeze
and
like
well.
Please
get
your
stuff
merged
by
then
least
so
far
like
the
random
ones.
That
I've
you
know
taking
a
look
at
things
can
be
pretty
on
track.
I'll
have
like
Jeremy
or
I
brewed.
An
have
you
seen
any
that
you
know
might
be
sticking
out
is
not
making
not
for
my
list
yet
well.
D
Pretend
I
didn't
stick
around
that.
We
have
a
meeting
like
five
minutes
before
it
started.
So
my
report
is
like
totally
totally
ready,
so
I
take
the
best
grade.
I
feel
like
we're
pretty
much
in
the
same
shape
as
we
were
on
on
Monday,
but
like
one
of
the
stuff
that
so
the
blocking
blocking
pipelines
are
still
like
no
threat
so
which
is
good,
which
is
why
I
chose
yellow.
But
we
have
like
a
lot
of
red
in
the
informing
informing
pipes
pipelines
but
like
a
lot
of
the
stuff,
is
actually
like
really
moving
forward.
D
A
E
Hello,
okay,
so
this
is
Kirsten
from
bug.
Triage
we've
been,
you
know,
slowly
burning
down
through
our
open,
PRS
and
open
issues,
since
Monday
we've
actually
gone
down
by
you
know
like
eight
five
and
then
for
some
PRS
none,
but
like
we're
doing
a
slow
burn
down,
we've
already
pinged
all
of
the
issues
and
pr's
once
and
we
started
repaying
them.
E
We're
also
going
to
be
reaching
out
to
people
via
slack
if
they're
not
responsive,
like
on
github
at
the
end
of
the
week
and
then
early
next
week,
late
next
week,
depending
on
early
next
week
late
this
week,
depending
on
our
responses,
we'll
start
moving
the
PRS
and
issues
out
of
the
milestone,
but
everything's
going
okay
and
yeah.
If
there
any
questions,
let
me
out
awesome.
A
F
Hey
so
so
last
two
days,
I'll
be
actually
leased
out
too,
although
enhancement
owners
who
didn't
respond.
So
we
got
some
responses,
so
saying
hey,
we
need
ox,
but
we
will
be
opening
a
PR
soon.
So
we
have
mark
those
enhancements
saying
we
need
dogs
still
waiting,
because
we
we
have
two
more
days
and
we
we
don't
have
responses.
B
A
The
two
of
you
could,
if,
if
we
can,
if
you
could
talk
about
the
two
that
you
mentioned,
that
might
not
even
make
it
into
the
117
that
would
be
of
interest
if
you,
yes,
I,
think
all
yeah
I've
shared
those
links
here
in
the
doc,
yeah
awesome
and
then
I
am
more
than
happy
to
throw
my
weight
around
and
yell
at
people
for
you.
So
if
you
want
to
just
send
me,
those
links,
I
will
go
and
stomp
on
some
people.
A
A
Yes,
do
that
okay
great,
when
we
can
break
it
up
so
awesome,
then
that
that
would
be
the
main
thing
to
follow
up
in
the
next
two
days
and
check
back
in
on
Friday
morning.
Tommy.
Will
you
be
there
on
Friday
or
I?
Know,
that's
probably
Saturday
already
for
you
or
likely
Friday
night
I
need
me
available.
Okay,
great
awesome,
fantastic
next
release
notes
with
Chris
happy.
G
Wednesday
everyone,
so
no
big
updates
since
Monday,
but
I
just
wanted
to
kind
of
remind
everyone
again
about
the
known
issues
and
does
it
know
what
trees
I
should
be
shaking
to
get
something
loose
for
that
for
that
one
we
haven't
had
responses.
Since
the
code
freeze,
email
went
out
on
Monday,
so
I
will.
A
G
A
A
Yeah,
it's
it's
difficult
to
detect
because
we
don't
know
which
SIG's
have
known
issues
right,
otherwise,
I
just
drove
up
in
their
meeting
and
be
like
give
me.
The
details
have
to
figure
out
who
has
details,
so
I
would
say
going
to
all
the
stake
channels
and
just
kind
of
be
like
hey.
This
is
a
thing
and
then
I
will
send
out.
I
will
send
out
the
same
text
in
a
mailing
list.
If
you
pay
me
later
today,
I
can
do
that.
Okay,.
G
A
All
right
no
Stephen
either
it
doesn't
even
is
anyone
else.
They
are
from
released
branch
and
I
hear
that
somebody
got
very
excited
yesterday.
I've
got
to
cut
their
first
beta
release
and
it
was
super
awesome,
so
it's
out
there
and-
and
we
can
we
can
you
know-
hopefully.
Hopefully
the
community
will
give
us
feedback
on
what
what
the
first
issues
are
to
pop
up
with
the
beta
cut,
some
emeritus
lead.
Do
we
have
Clair.
A
Also,
not
today,
I
will
communicate
harder
about
the
fact
that
we
have
started
burned
down
regardless
I'm,
alright,
not
having
these
updates.
Today
we
have
a
couple:
six
capability
things.
Oh
no,
this
is
the
same
update
us
from
Monday.
That's
fine!
We
don't
need
to
do
that
for
today.
So
let
me
actually
just
kind
of
take
that
ya
see
Monday,
hey
cool
and
then
next
open
discussion.
Anything
we
need
to
go
over
any
concerns.
A
All
right
it
looks
like
please,
please
keep
it
look.
Please
take
a
look
on
the
board,
see
if
there's
anything
you
can
help
with
on
our
current
work,
keep
things
rolling
any
updates
on
any
items
we'll
check
in
on
those
on
Monday
very
good
sounds
like
we
have
a
quick
and
easy
meeting
today
and
I
will
see
all
of
you
back
on
Friday.