►
From YouTube: Kubernetes 1.17 Release Team Meeting 20191028
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
C
B
Great,
we
are
recording,
I,
see
awesome
anyway.
Good
morning,
release
team
is
Monday,
October
28th.
This
is
week
six
of
the
kubernetes
117
release.
Please
put
your
name
in
the
attendance
sheet
and
and
also
let
us
know
if
you
are
giving
the
update
right
next
to
the
update,
just
put
your
name
and
handle
just
so
we
can
keep
track
of
who
did
what,
when
also
at
this
point,
I
will
remind
you.
We
are
under
the
kubernetes
code
of
conduct,
tweet
each
other
with
kindness,
and
let's
get
this
started
with
enhancements.
B
E
This
will
be
our
special,
our
special
cut,
because
this
will
be
the
first
time
network
we're
actually
cutting
the
release
branches,
as
well
as
establishing
the
test
jobs
for
117.
On
that
branch,
I'm
going
to
be
finding
a
time,
I
gotta,
look
at
my
calendar
when
I
get
back
to
a
computer
when
we
can
do
a
recording
and
I'll
send
out
a
calendar.
Invite
for
that.
It
seems,
like
people
are
interested
in
seeing
the
live
stuff
again.
So
I
will
do
this
time.
The
recording
will
be
of
the
release
process
itself,
not
the
staging
stuff.
E
I'll
do
the
staging
ahead
of
the
recording
that
way
we
can
walk
through
the
release,
as
well
as
the
branch
cut,
as
well
as
the
creation
of
all
the
PRS
which
I,
which
is
fun
because
it
only
happens
once
a
cycle
right.
So
it's
easy
to
replicate
the
other
stuff
but
the
but
the
the
the
job
creation
all.
But
all
that
stuff
only
happens
once
a
cycle,
so
it'd
be
good
to
record
it.
That
is
all
I
got.
If
anyone
has
questions
like
yeah.
B
One
two
three
great
Steven:
if
you
wouldn't
mind,
could
you
could
you
write?
I
know
it's
just
the
beginning
of
the
meeting,
but
if
you
could,
if
you
or.
B
Absolutely
thanks
Steven
appreciate
it
by
okay:
let's
get
let's
hear
from
enhancements.
B
H
I
H
So
the
status
is
pretty
much
the
same
as
last
week.
The
biggest
change
so
far
is
that
number
five,
six
five,
the
CSI
block
storage
support-
has
been
deferred
to
118.
They
didn't
think
they
were
going
to
get
enough
testing
and
before
the
end
of
code,
freeze,
so
they've
deferred
to
118.
Everything
else
is
still
pretty
much
the
same
as
last
week.
We're
still
tracking
44
things.
Now,
instead
of
45
19,
stable,
13,
we're
going
beta
and
12
will
be
launching
the
Alpha
very.
F
Yeah,
so
hello,
guys
so
Elena
is
unavailable
today,
so
I'm
going
to
be
doing
the
report
today.
Okay,
let's
begin
with,
we
are
green
in
general,
so
there
are
a
couple
of
flaky
jobs
that
we
still
are
trying
to
monitor
them
and
fix
them
if
there
is
a
possibility
to
fix
it
to
fix
them.
So,
let's
start
with
master
blocking,
we
have
node,
Cabella
master
is
failing.
F
We
have
an
issue
open
8,
4
2,
3
6,
but
there
is
no
response.
Yet
we
still
we
already
pink
they're
responsible
people.
So
we
are.
We
hope
that
the
next
days
they
they
try
to
check
it
out.
We
have
also
the
Windows
master.
Failing
that
one.
There
is
an
already
PR
open
for
the
fix
the
last
activity,
or
this
PR
was
20
hours.
F
Algol
was
a
review
activity,
so
we
we
believe
that
the
next
days
we
this
will
be
fixed
as
well,
so
in
the
master,
reforming
9,
flaky
jobs
and
only
one
job
is
failing,
and
this
one
is
related
to
an
issue
rate
for
one
five,
one
which
say
this
should
be
already
fixed,
and
we
can
see
that
this
failure
is
flag.
So
we're
going
to
keep
monitor
it,
and
if
it's
okay
tomorrow,
we
can
close
it
pretty
much.
That's
all
any
questions,
guys.
B
Yeah,
if
there
is
no,
if
it's
still
flaking
tomorrow,
that
last
one,
please
ping
me
on
slack
and
let
me
know
again
this
week
on
it,
we
do
want
to
keep
an
eye
on
that.
I
also
have
put
a
bookmark
on
to
the
sick,
node
one
because
take
know
it
has
the
most
code
and
the
fewest
maintain
errs,
and
we
want
to
make
sure
that
that
we
check
that
out
and
follow
us
cool.
F
Actually
we
this
flaky
jobs
like
we,
they
are
stopping
flaking
time
to
time.
Sometimes
they
are
grading.
Sometimes
they
are
flaky.
Now
we
have
a
few
issues
opened
for
flaky
jobs,
but
not
for
all
of
them,
but
we
all
of
the
suddens
are
still
monitoring
them
and
in
case
we
found
a
better
way
how
to
fix
it
and
stop
deflecting
this
we're
going
to
do
it
so
we're
going
to
see
the
next
days.
This
is
like
a
twirly
situation
right.
B
L
B
M
Hopefully,
one
had
a
good
weekend:
I
don't
have
any
updates
on
the
themes
today,
but
that's
something
I
need
to
think
work
with
calms
a
little
bit
closely
with
this
or
that
as
for
updates.
For
this
week
we
got
the
alpha
2
&
3,
release,
notes
up
on
the
rel
notes
website.
The
link
is
in
the
doc
I
want
to
thank
Bridgette
and
Geoff
for
alpha
note
again,
those
out
as
well
as
sasha,
was
able
to
help
sort
out
one
of
Tim's
issues
that
he
had
last
week,
number
88
9
9.
M
B
Awesome
thanks,
Chris
I,
looked
at
I
did
look
at
the
release,
notes
and
the
enhancements
sheet
last
week
and
kind
of
so
I
feel
like
one
of
the
major
things
that
I
saw
just
from
glancing
at
it
is
we're.
Gonna
have
a
lot
of
exciting
things.
Going
on
for
windows.
Related
updates,
right
am
I,
am
I,
am
I
totally
Ashley.
B
B
B
Okay,
great,
let's,
let's
keep
an
eye
on
it.
If
you
have
any
updates
during
the
week,
just
feel
free
to
ping
me
on
slack
or
send
a
message
to
seek
release.
Definitely,
and
at
me,
thank
you
sure.
Thank
you
great.
We
already
heard
from
Steven
who's
Sam
has
stone,
come
in
shadow
mood,
clear
hi,
I'm
we
haven't
seen
univ
it.
B
Okay,
as
for
my
updates,
I
believe
in
the
next
yes,
sue
Steven
already
mentioned
that
we're
having
upcoming
patch
releases
those
wait.
Actually,
he
didn't
go.
Steven
already
mention
that
we're
going
to
cut
beta
this
week
tomorrow,
which
is
super
exciting,
and
the
there's
also
going
to
be
patch
releases
plans
for,
but
that's
in
a
couple
weeks.
That's
November,
8th
I,
believe
if
I
have
this
right,
yes,
November
8th
and
we
are,
as
of
this
week,
no
longer
supporting
113.
We
will
also
start
removing
justice
for
113
this
week,
so
that
is
exciting.
B
J
B
Than
that
that
would
be
all
of
my
updates
for
this
week,
so
get
ready
for
burn
down
for
a
state
of
burned
down,
Monday
Wednesday
Friday.
Do
we
have
actually
that's
a
good?
That's
a
good
point.
I
may
want
to
have
one
of
those
meetings
be
a
little
bit
earlier
for
the
EU
folks
and
as
far
as
I
know,
we
should
be
back
to
regular
sync
with
daylight
saving
time
next
week.
Daylight
saving
ends
in
the
u.s.
this
coming
weekend.
So
if
anyone
has
input,
please
let
me
know
a
sink
or
speak
up.
B
B
B
B
B
C
B
B
J
B
Q
B
B
E
B
B
Yeah
I'll
I.
I
B
I'll
be
good,
let's
see
we
have,
let
me
actually
yeah.
Let
me
just
go
ahead
and
assign
myself
for
now,
so
that
it's
on
my
sheet
and
on
assign
there
we
go
them
done
at
least
there's
a
little
bit
of
movement
on
it
document
criteria
by
which
we
decide.
This
is
the
CI
thing
and
our
CI
lead
is
not
here
today,
but
perhaps
one
of
the
shadows
can
update
I'm.
R
B
Fantastic
right,
so
let's
go
ahead
and
put
that
into
right
here:
yeah
boom
shadow
halo
process.
B
C
B
Honestly,
that's
that
part
of
the
UI
is
my
least
favorite,
but
you
didn't
hear
me
say
it
in
public
PR
boilerplate
to
improve
release,
notes,
oh
yeah,.
J
E
So
I
think
the
same
statuses
last
time
I
have
to
again.
This
is
something
I
think
I'll
have
time
this
week.
We
basically
have
to
open
up
a
either
an
issue
or
a
full
PR
on
creating
a
kind
deprecation
label
and
then
kind
of
dropping
some
notes
in
regarding
the
code
blocks
on
that
that
should
this
should
be
handled
by
automation
and
not
not
an
additional
code
block
yeah.
B
B
E
Q
B
B
See
I
have
not
either
I
must
be
crazy,
so.
E
I'm,
essentially
trying
to
land
a
bunch
of
things
before
code
freeze,
so
my
my
PR
documentation
stuff
has
been
minimal
and
it's
been
more
commits,
but
I
should
again
have
time
this
week
to
start
banging
out
some
of
that
stuff,
not
completing
it,
but
at
least
tying
issues
to
all
of
these
things.
A
lot
of
these
are
already
in
progress.
Yeah.
B
Yeah
I
know
and
feel
free
to
go
ahead
and
communicate
in
st.
release
and
tag
people
when
you're
doing
this.
Just
so
that
we
can
stay
I
mean
yes,
everyone
can
go,
read
this
issue,
but
at
the
same
time,
it's
nice
to
just
kind
of
have
a
little
bit
of
ping
back
on,
like
hey
I'm
doing
this
or
who
was
it?
That
did
this
kind
of
thing
so
anyway
feel
free
to
loop
me
into
that,
and
ask
me
if
that's
fine.
E
R
P
R
N
E
E
E
E
B
E
B
It
if
you
know
the
right
people
and
and
can
make
can
make
this
happen,
because
yeah
I
mean
tell
them
that
I
want
it,
but
every
time
I
talk
to
them.
It's
like
yeah,
you're,
scared
of
it.
So
so
the
updates
have
been
consistent
and
unhelpful.
Where.
B
Q
E
F
Well,
it
seems
that
they
are
answering
the
our
calls
right
so,
every
time
that
we
have
an
issue
that
needs
to
be
fixed,
there
are
people
that
are
trying
to
work
on
it.
So
I
think
that
the
cooperation
is
like
it's
getting
better
every
day.
Only
if
we
still
meet
the
face-to-face
meetings,
but
in
I
don't
know,
maybe
the
meetings
are
good
enough
to
get
know
each
other
and
have
a
better
communication
or
not.
E
B
Yeah
I
do
feel
like
there
are
this.
The
communication
and
the
signal
back
and
forth
has
has
improved
if,
since
we've
gone
billing,
we
need
help
on
this
issue.
We
have
this
and
they've
been
sending
updates
pretty
consistently
the
last
three
weeks.
So
in
that
sense
we
have
seen
improvements.
Just
it's
the
meeting
time.
That's
been
not
quite
happening.
Okay,.
R
B
Yeah,
actually,
let's
go
ahead
and
do
two
meetings.
Can
I
edit
I
can
add
it
right.
E
Q
Q
D
G
Quick
thing,
I,
don't
know
if
we
want
to
leave
on
the
backlog
whatever,
but
I
did
comment
on
the
handling
the
exceptions,
DMO
mm-hmm
awesome
honestly,
at
this
point,
without
further
automation,
it
seems
kind
of
redundant
where
we're
keeping
track
of
everything
in
the
sheet.
We
have
keep
track
of
everything
on
the
mailing
list.
Yeah.
E
Know
the
yeah,
so
the
mailing
list
is
that
the
mailing
list
is
supposed
to
inform
the
sheet
right
are
supposed
to
inform
the
exceptions
IMO.
What
we
do
afterwards
is
a
question
mark.
Do
we
want
to
pull
this
in
to
a
site
or
something
that's
kind
of?
What's
this
issues
about?
Okay,
so
I
mean
it's.
It's
it's
lived
for,
I,
don't
know
how
many
cycles,
if
we
want
to
close
this
out,
I'm
not
opposed
to
it.
B
Yeah
well,
basically,
just
like
make
a
change
in
the
enhancements
handbook
that
says:
hey,
listen!
We
don't
really
want
to
do
this
anymore
right.
We
can't
just
we
can't
just
close
it
out
and
then
just
leave
everything,
because
then
the
next
enhancements
think
it's
gonna
be
like
what
about
exceptions.
So
I'm
just
gonna
write
a
couple
of
notes
here,
given
the.
I
E
B
E
E
L
E
O
J
E
G
I
I
P
G
I,
don't
know
we
should
actually
close
if
we,
this
is
one
we
do
eventually
want
to
handle.
I
do
like
the
idea
of
setting
it
to
like
lifecycle
frozen,
though
yeah.
E
I
Q
E
Okay,
what
do
we
want
to
do
here?
We
should
we
should
get
this
in
this
cycle.
This
has
been.
This
has
been
almost
a
year
and
I
think
it's
simple
enough
to
say
what
it's
essentially
documenting,
what
we
will,
what
we're
willing
to
do
in
terms
of
critical
bug
fixes
for
about
to
be
non-supported
branches,
okay,
yeah
I
think
it's
I
think
it's
enough
to
write
up
a
blurb
on
that
I,
wonder
if
I
can
give
that
to
someone.
E
C
L
E
A
E
B
B
A
So
basically,
if
you
look
at
the
invite,
it
looks
like
it's
pointing
to
the
right
place,
but
if
you
mouse
over
in
the
invite,
it
shows
a
different
link
behind
the
text
in
it.
So
when
you
click
on
it,
you
go
to
something
different
than
what
you're
clicking
on
so
that
that
are
all
right.
There
is
what
you
want
to
put
in
the
link
in
the
calendar:
okay,.
B
Great,
let
me
assign
myself
oh
I'm,
already
saying
yay
awesome.
B
I
B
For
your
time,
everyone
see
y'all
next
week.