►
From YouTube: Kubernetes 1.17 Release Team Meeting 20191108
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
we
are
live
good
morning
afternoon
evening:
everyone,
it
is
Friday
November
8,
2000
19.
It
is
still
a
week
7
of
the
117
kubernetes
release.
My
name
is
Guinevere
Sankar
and
I
will
be
your
lead
for
this
meeting
today.
Please
put
your
name
in
the
attendance
list
on
the
notes.
I
have
amazing
link
in
the
chat
and
also
remember
to
treat
each
other
with
kindness
and
respect
as
we
are
under
the
kubernetes
code
of
conduct
with
out
today
we
are
desperately
checking
in
and
it
is
also
the
docs
deadline.
A
B
B
B
B
B
A
A
B
A
C
And
they
were
they're
still
making
state
release,
1.17
informing,
pretty
red,
but
they've
been
fixed
in
master,
but
they
just
haven't
been
run
again
yet
since
the
fast
forward
this
morning,
so
we're
thinking
that
will
clear
up
and
then
there
was
one
issue
with
a6
scheduling,
related
job,
but
we've
been
in
contact
with
them
and
they're
working
on
a
fix
right
now.
So
we
should
be
clear
pretty
soon
awesome.
A
C
F
F
Right
so
for
open,
we
have
a
total
of
47
open
issues
in
which
a
reduction
by
seven
from
last,
the
last
update,
which
was
a
Wednesday
critical
issues,
are
down
by
one.
So
now
we
have
four
critical
issues.
We
have
sixteen
important
issue,
which
is
down
by
three
four
open
PRS.
We
have
an
increase
by
one
as
now
54
up
against
the
last
update,
which
was
53,
we
have
critical
edge.
Npr's
have
increased
by
two
actually
important
soompiers
have
stayed
the
same,
no
changes
there
for
total
flaky
test,
flaky
peers
and
tests.
F
We
have
44,
which
is
the
reduction
of
minus
8.
We
have
the
opinion
issues
so
far.
Some
of
the
issues
have
been
moved
out
of
the
release.
I
think
some
of
them
are
coming
along
to
you.
Just
fine
I
would
see
by
the
end
of
the
week
by
the
weekend.
So
we
have
plans
of
contacting
issue
owners
and
PR
owners,
and
they
are
six.
If
you
don't
hear
any
response
from
them,
we
have
plans
of
kicking
them
out
for
the
release.
So
that's
the
plan
for
bug
triage
and
a
questions.
Please
I.
E
Totally
ugly,
thank
you,
Bob
reaching
out
to
people
was
like
really
difficult.
He
thinks
he
had
to
like
someone
to
make
internal
Microsoft
thing,
because
everyone,
where
you
know
ms
ignite,
so
it's
kind
of
like
so
current
state
Texas,
like
we
have
five
of
the
enhancements.
While
we
still
don't
know
what,
if
they
need
dogs
or
not-
and
it
also
looks
very-
it-
looks
like
they-
it
might
not
happen
form
on
one
one,
seven,
because
there
is
really
no
update
on
the
enhancement
side
as
well.
E
So
if
we
also
reached
out
personally
and
then
still
no
response
anyway
and
that
we
have
three
enhancements
where
they
said
it,
they
will
be
dogs,
but
there
are
still
no
drafts
among
them.
One
of
them
said
that
they
will
be
opening
your
dog
sphere
by
today,
because
we
still
have
some
time
and
two
of
them,
maybe
like
five
or
four
days.
They
said
like
yeah
with
dogs
and
we
will
open,
but
we
still
don't
have,
and
it
also
expecting
them
to
open
it
today.
So
this
is
what
all
it
looks
good.
We
have
yeah.
A
G
A
E
A
E
A
A
H
Friday
everybody
totally
updates.
This
week,
we
sent
out
notes
to
all
the
SIG's
about
the
known
issues
free
for
speech
or
received
one
thanks
for
the
update
their
heads
response,
but
no
one's
added
anything
into
the
issue
yet
planning
on
giving
them
to
the
end
of
the
weekend
before
sending
out
another
reminder,
aside
from
that
reached
out
to
comms
and
got
some
started,
communicating
about
the
release,
themes
as
well,
the
beta
1
notes
should
have
a
PR
in
some
time
today.
A
A
A
All
right,
I
will
I
will
actually
follow
up
on
that
today.
Just
and
it's
also
a
long
weekend
for
some
folks,
so
that
my
Sunday
thing
might
not
work
what
l,
because
people
might
have
plans
who
knows
so
I'll
I'll
yell
at
people
again,
Oh.
H
A
A
Do
we
have
anyone
from
comms
today,
I
know
that
it's
David's
birthday,
so
I
was
going
to
totally
publicly
sing
happy
birthday
on.
Actually
that
works
really
poorly.
It's
really
hard
to
all
sing
together
with
video
anyway,
whatever
so
we
don't
have
any
comms
updates.
Today
is
anyone
from
the
release
branch
management
team
here.
G
G
H
A
Traveling
we
have
six
scaleability,
that's
still
the
same
as
from
Monday
I.
Believe,
let's
check
see
Monday,
oh
okay!
No,
we
have
new
updates,
maybe
I
don't
know.
I'll
follow
up
on,
seek
scalability
I.
D
Can
give
a
very,
very
quick
update
on
that
one?
Okay,
there's
a
joint,
the
regular
cig,
there's
a
regular
sake
meeting
yesterday.
There
isn't
something
something
much
happening
ice
and
like
is
there
something
that
worries
you
or
that
is
breaking
at
the
moment
that
you
think
might
affect
the
release
in
any
way,
but
there's
nothing
for
now
very.
A
Good,
just
right,
no
known
issues.
Great,
oh
I,
skipped,
really
sweet
update.
Okay,
docks,
free
docks
deadline
for
our
placeholder
pr's
is
today.
We
already
mentioned
that
code.
Freeze
is
coming
next
Thursday.
A
Because
all
caps,
fantastic,
alright
does
anyone
have
any
interesting
concerns
we
should
be.
We
should
be
looking
at.
I
will
be
looking
at
the
final
work
on
the
enhancements
in
the
next
few
days.
If
anyone
notices
anything
unusual
or
anything
worrisome,
let
me
know,
unfortunately,
we're
always
checking
for
a
lack
of
a
signal,
which
is
why
we
have
this
team.
That's
much
harder
to
check
on
than
an
existing
signal.
A
H
H
H
A
Great
so
that
means
we
can
just
focus
on
Docs
and
making
sure
that
everyone
meets
all
the
requirements
cool.
That
will
be
the
theme
of
the
day.
Thank
you.
Everybody.
Thank
you,
Maria
for
attending
six
scalability
and
getting
getting
getting
us
some
really
good,
direct
signal
there.
That's
awesome,
all
right,
it
is
9:20.
Does
anyone
have
any
other
topics,
concerns
comments,
thoughts,
compliments.