►
From YouTube: Kubernetes 1.17 Release Team Meeting 20191203
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
This
is
a
quick
stand
up
type
burn
down
meeting
and
oh
yeah,
be
nice
to
each
other
or
else,
and
let's
hear
it
from
enhancements.
B
C
So
not
too
many
updates
from
yesterday,
but
we
did
get
response
mistake
so
scalability
thanks
for
pushing
that
steven,
I'm
so
they're
working
on
a
fix
for
that
looks
like
they've
identified
where
the
problem
was
introduced.
I'm
so
we'll
continue
to
monitor
that.
Also
a
we
have
a
new
failing
test
on
1.17
informing
reached
out
to
six
storage
today
about
that.
I
don't
think
it
would
be
released
blocking,
but
we'll
continue
to
monitor
that
as
well.
Awesome.
C
A
I'm
going
to
assume
that's
just
cool
music
moving
on
the
long
to
bug
triage
with
murky,
hey.
D
Good
morning,
good
afternoon,
good
evening,
everybody
bug
triage
is
currently
yellow
for
open
non
test
flakes
we
are
down
to.
We
have
one
open
for
open,
KK,
P
ours.
We
are
down
three.
We
have
three
open
for
open
KK
issues.
We
are
up
to
from
6
to
8
and
oops
I
missed
a
couple
for
priority
critical,
urgent
PRS.
We
are
now
at
zero.
That's
down
one
and
four
priority
important
soon.
We
are
at
three.
That
is
up
one
from
two
we
had.
D
Let
me
see
we
had
pool
request,
88
49,
20
and
847
24,
which
have
now
been
moved
into
milestone.
1
18,
as
per
their
owners,
I,
think
we're
going
to
be
reaching
out
to
some
more
people
today.
So
my
hope
is
is
that
by
tomorrow's
meeting
we
will
actually
be
green.
That
is
all
from
bug.
Triage.
A
A
F
So
I
think
we're
still
looking
green.
We
got
the
e
area
PR
for
the
RC.
2
draft
is
ready
and
should
be
put
in
shortly,
which
is
good
and
I'll.
Have
a
draft
email
for
the
cig
leads
to
take
a
look
at
the
the
draft
today
and
I'll.
Send
that
to
you,
Glenn
awesome,
every
personal
kind
of
putting
all
the
other
right
things
into
the
right
buckets
in
this
dock.
F
A
Awesome
cool
all
right.
Any
questions
for
release
notes
sounds
like
the
stakes
were
pretty
responsive.
Yesterday,
yeah,
okay,
they
were
just
like.
Oh
it's
the
afternoon
and
I
was
gonna.
Do
my
writing
in
the
afternoon,
rather
than
in
the
morning
awesome
cool?
Let's
see
I'm
going
to
ask
about
comms
yeah.
G
A
E
Everyone
so
I
cut
the
rc2
earlier
today,
I've
been
watching
over
the
last
few
days
watching
the
charity
pics
come
into
1:17.
At
this
point,
we've
got
two
remaining
in
the
queue,
but
they
don't
look
critical
enough
to
include
in
the
dot
0
if
the
cigs
change
their
minds.
I
think
we
can
talk
about
that.
E
One
is
cherry-pick
around
partial,
cherry-pick
for
a
config
for
the
Windows
nodes,
but
I
think
this
is
testing
only
and
then
one
around
the
I
scuzzy
rest
counters
that
one
yeah
it
seems
to
be
a
priority
important
soon,
I'm,
not
sure
if
I'll
be
I'll,
be
watching
the
cherry-picks.
If
anyone
kicks
up
about
getting
things
into
the
release-
I'll,
let
you
all
know,
but
at
this
point
I'm
assuming
that
we're
good
to
go
for
the
dot
zero.
A
Okay,
yeah
there's
two
cherry-picks
and
one
failing
test.
I
think
we
we
want
to
keep
an
eye
on
those
issues
for
the
rest
of
our
day
and
maybe
the
shows
there
yeah.
E
H
E
A
That
I've
considered
everyone
equally
all
right
cool,
so
my
amendments
are,
we
are
planning
for
a
release
this
coming
Monday,
it's
looking
pretty
good.
We
are
ironing
out
the
last
wrinkles,
so
let's
hope
that
nothing
surprising
happens
in
the
next
few
days.
I
have
the
retrospective
scheduled
for
what
used
to
be
the
kubernetes
community
meeting
slot
on
Thursday
Pacific
10:00
a.m.
A
I'm,
not
sure
that
that's
on
the
calendar
yet
so
I
will
get
that
on
the
calendar
as
soon
as
I.
Can
please
please,
please,
let
me
know,
even
if
it's
in
a
DM,
if
that
does
not
work
at
all,
for
you
mainly
because
there
were
a
couple
of
unavailability,
is
on
this
team
that
I
kind
of
wish
I'd
known
about
beforehand,
and
that
would
have
adjusted
that
time
slot.
So
I
will
also
get
a
retrospective
dog
up
when
I
send
that
when
I
send
out
meeting.
A
A
Let
me
write
that
yeah,
we've
already
sort
of
heard
from
six
scaleability
there.
There
were
a
couple
of
tests
that
were
timing
out,
but
that
was
because
they
didn't
dump
logs,
not
because
the
tests
themselves
were
feeling
was
the
last
status
that
I
heard
but
they're
working
on
it
all
right.
Any
concerns
any
questions,
anything
that
anybody
forgot
to
mention.
A
Let's,
let's
all
stay
on
top
of
the
final
bugs
and
make
sure
that
the
release,
notes
and
comms
are
getting
all
the
support
they
need.
So
if
you
are
a
part
of
a
sig
or
you
know,
some
sick
needs
and
have
been
dragging
their
heels,
you
know
just
and
just
just
monitoring
that
st.
release
channel
for,
for
you
know,
questions
for
help
by
Chris
or
our
max,
or
anybody
from
those
teams
cool
all
right.