►
From YouTube: Kubernetes 1.17 Release Team Meeting 20191014
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
Oh
mm
anything
we
are
recording
so
good
morning,
good
afternoon,
good
evening,
a
world
welcome
to
the
once
a
welcome
to
the
117
kubernetes
released
in
meeting
or
Monday
October
14
Happy
Thanksgiving
by
the
winner.
Let
me
start
off:
we
take
a
kubernetes
Code
of
Conduct,
which
pretty
much
pretty
much
bubbles
down
to.
Please
be
nice
to
each
other
and
dumped
in
don't
be
a
jerk.
With
that
note,
let's
get
started
so
enhancements
update
with.
C
Okay,
there
we
go,
we
are
currently
yellow.
We
have
actually
quite
a
few
more
caps
sort
of
came
in
from
the
last
update.
We
are
tracking
51,
with
16
at
risk,
with
more
stapl
coming
this
release
than
the
previous
ones
we
are
currently
at
16.
Alpha
15,
beta
and
20,
stable
Oh
sounds
looking
pretty
good.
There
I
have
a
breakdown
of
which
cats,
which
enhancements
are
sort
of
still
at
risk.
C
A
good
chunk
are
either
don't
have
it
kept
out
there
or
have
like
a
kept
PR
in
flight
I
with
the
amount
of
activity
that
that's
been
going
on.
I
already
know
that,
like
I
put
this
in
there
this
morning,
that's
already
out
of
date,
so
you
know,
probably
by
well
probably
by
this
time
tomorrow.
We'll
have
a
better
idea
of
how
things
are
going.
A
D
A
C
C
Going
once
I
did
you
actually
have
one
last
thing:
we're
good
I
have
each
meeting
I
have
forgotten,
you
call
and
introduce
my
shadows
each
time.
C
E
A
G
Okay,
so
for
this
week,
I
actually
chose
the
color
red
I
actually
started
with
yellow,
but
that
I
was
like
filling
out
a
report
and
I
I
got
more
and
more
depressed
and
I
moved
to
red.
So
it's
like
red,
slash,
yellow,
depending
on
my
mood,
so
so.
First
of
all,
there's
there's
two
jobs
that
are
like
constantly
red
for
master
blocking,
which
is
which
is
pretty
bad.
So
it's
actually
a
known
issue.
It's
there's
there's
some
busco's
failure.
That
already
happened
last
week
and
the
test
in
frog
was
pretty
much
on
top
of
that.
G
They
actually
fold
that
as
a
result,
but
like
we
can
prove
that
it's
it's
not
really
resolved.
So
I
think
that
once
was
the
guys.
Wake
up.
I
think
that's!
That's
gonna!
Keep
moving
so
we'll
keep
we'll
keep
poking
that
that's
like
both
both
of
those
jobs
are
both
of
those
jobs
are
affected
by
that
failure
when
it
comes
to
master,
informing,
there's,
also
free
failing
jobs.
G
That's
actually
like
things
that
are
consistent,
parrot
would
really
just
like
flaking.
So,
first
of
all,
its
cause
first
of
one,
is
called
bite
caused
by
oh
storage
test.
There
was
already
an
issue,
but
there
wasn't
that
much
activity
to
be
honest,
so
it
was
created,
but
there's
like
no
one
who's
taking
care
of
it.
So
I
guess
we'll
need
to
start
really
like
poking
around.
For
that
there's
one.
That's
actually
like
a
sig
release
issue.
G
H
Sorry
go
I
can
hear
me
yeah,
so
those
are
those
are
probably
failing
because
of
the
things
that
I'm
moving
around
in
the
K
release
repo
right
now
they
are
based
on
they're
based
on
build
package
Sh
and
then
the
the
make
targets
which
are
builds,
build
debs
and
build
rpms.
That
package
that
Sh
was
also
doing
the
build
of
the
dr.
container,
which
didn't
really
need
to
happen.
So
now
that
I'm
wiring
the
dev
and
rpm
containers
to
build
on
co
cement,
we
should
be
able
to
pull
that
part
out
of
the
job.
H
A
A
G
A
A
I
Bug
triage
here
today
is
looking
good,
we're
green
the
number
of
issues
and
PRS
that
we're
seeing
is
relatively
stable.
Last
week,
they've
gone
up
quite
a
bit
from
the
week
before
this
week,
they're
pretty
close
to
what
they
were
last
week.
So
it's
63
open
issues,
non-test
flake
issues.
We
have
three
critical
urgent
issues
that
have
been
around
for
a
while,
so
these
are
two
of
them.
I
think
we're
six
month,
six
month,
open
issues
and
one
had
been
open
for
a
while,
but
they
look
to
be
making
progress
on
this
release.
I
So
we'll
see
there's
still
plenty
of
time.
There
are
24
important
soon
issues
as
well.
So
that's
it!
That's
an
okay
number,
we're
fine
with
that.
It's
in
terms
of
open
PRS.
We
have
53
that's
up
only
one
from
last
week
one
critical
soon
PR
was
opened
and
we
have
a
good
chunk
of
important,
soon
PRS,
but
it's
too
early
for
us
to
start
pinging,
those
yet
so
31
important
soon
PRS
are
open
and
our
total
number
of
open
KK
issues
for
one
not
seventeen
is
72
and
is
the
same
number
we
had
last
week.
J
D
J
Welcome
Emily,
thank
you.
So
we
had
our
first
team
meeting
last
week.
Then
we
gone
through
some
of
the
important
tasks
which
we
need
to
keep
a
track
and
also
had
a
look
at
the
timeline
for
dogs.
And
then
we
had
a
question
open
question
regarding
the
timeline,
so
so
the
the
current
timeline
for
the
documentation
is.
J
We
have
to
get
a
placeholder
dots
PR
by
number,
eight
that
is
close
to
three
and
half
weeks
after
the
enhancement,
our
deadline
and
immediately
we
have
another
deadline
on
number
19
saying
all
the
dogs
PR
should
be
ready
for
with
you.
That
is
that
is
around
ten
days
after
the
after
creating
the
placeholder
PR,
and
the
third
deadline
is
on
November
22nd,
where
all
the
people
code
talks
political
should
be
ready
to
ready
to
get
merged.
J
So,
looking
at
this
timeline,
we
had
a
question
saying
we
have
cube
economy
happening
from
eighteen
to
twenty
first
right
so
and
as
as
you
all
know,
at
the
end
of
the
deadline
will
be
getting
lot
of.
We
need
to
do
lot
of
follow-ups
with
the
owners
and
try
to
get
the
first
PR
sin.
So
I
want
to
just
make
sure
that
we
have.
We
are
on
the
correct
timeline.
J
A
H
Also
on
the
readme
for
the
for
the
117
cycle,
there
was
a
there
was
a
question
about
the
docks,
ready
deadlines,
come
up,
I
believe
maybe
a
week
and
a
half
ago
or
so,
or
there
was
a
different
deadline
between
the
TLDR
and
the
actual
full
timeline.
Yes,
I
believe
the
earlier
one
was
the
one
that
was
decided
later,
but
I
think
we
settled
on
the
later
one
I'm,
not
sure
what
the
background
was.
H
J
J
A
K
So
we're
in
pretty
good
shape
right
now
we
do
have
a
pull
request
that
the
821
that
it
looks
like
it's
possible.
It
just
doesn't
have
the
right
labels.
So
if
somebody
who
can
merge
that
would
take
a
look
at
it,
that
would
be
fantastic,
and
then
we
have
an
issue
open
that
Eddie
open
to
collect
known
issues
for
this
release
so
and
we've
we've
just
started
working
on.
K
You
know,
adding
releases
to
the
website
and
pastor
new
releases
and
patch
releases
say
that
to
be
times
fast
so
and
our
I
am
a
shadow
on
the
team.
Our
lead
is
celebrating
Canadian
Thanksgiving,
so
he's
hopefully
eating
lots
of.
You
know
turkey
that
says
a
bhoot
other
than
that.
Hopefully
we
can
get
a
sacral
Issa
821
looked
at
and
other
than
that
I've
got
nothing
else,
we're
in
pretty
good
shape.
Right
now,.
A
L
A
D
H
So
nothing
too
exciting
going
on.
We
will
be
cutting
the
alpha-2
on
tomorrow
tomorrow,
as
well,
and
a
slew
of
other
releases,
a
bunch
of
so
stay
stay
tuned
for
that
I'm
going
to
be
making
some
I
have
made
some
changes,
but
I
haven't
pushed
them
out
just
yet
I'm
new
making
some
changes
to
be
the
Kate's
cloud.
Golder
image
I
noticed
that
hasn't
been
updated
since,
like
September
2018,
so
probably
time
for
an
update
I
on
the
release.
H
So
I
had
pushed
a
new
one,
but
I
I
removed
it
because
we're
about
to
cut
a
bunch
of
releases
and
I
don't
want
to
risk
that
just
yet,
but
for
the
next
alpha
I'll
push
the
new
image
and
the
only
thing
I
would
mention
is
just
watch
for
any
weirdness
during
the
staging
or
releasing
processes.
So
for
the
for
the
Alpha
to
that's
happening
tomorrow,
Carlos
will
be
cutting.
That
Carlos
is
kind
of
my
my
shadow
for
this.
So
we'll
make
sure
he
has
access
to
all
the
things
you
need
and
yeah.
That's
it.
A
A
A
We
have
enhanced
industries,
so
you
know
if
any
of
you
are
reviewers
and
perverse
and
or
are
working
on
any
features,
please
a
local
bridge
gaps
and
make
sure
that
things
are
in
order
other
than
that
I
wasn't
told
of
anything
that
a
Wayne
didn't
mention
anything
to
or
anything
specific,
the
Reg
way
that
I
should
mention
in
today's
call.
So
I
guess
that's
it,
and
unless
someone
has
any
more
quest
a
questions
or
comments,
we
can
move
on
to
the
six
color
memory
object.
So
questions
comments.
A
Nothing
so
I
was
just
is
almost
taking
a
brief
look
at
this
one.
A
little
a
little
while
ago
in
one
of
the
a
one
of
the
issues
that
is
being
mentioned
here
is
related
to
a
bunch
of
failures
on
one
other
jobs
big
today,
because
of
pastas,
but
also
this
morning,
I
saw
a
I
saw
a
message
pop
a
popping
on
tests,
testing
options
lag
and
the
failures
and
the
failures
not
coming
back
so
Hornet
so
hopefully
says
a
hopefully
see
a
signal
and
it's
testing
people
will
have
a
will.
A
Have
this
one,
a
control,
the
other
one.
The
other
date
is
TC
pack
a
performance,
a
has
had
some
tracing
failures
over
the
weekend,
both
days
they
were
testing
from
related,
so
I
guess
nothing
to
worry
on
the
kubernetes
only
cover
nicer
things,
and
with
that,
let's
move
on
to
open
discussion.
Anyone
has
anything
that
you
all
want
to
talk
about
anything
down
in
the
agenda.
H
If
you
see
there's
no
action
on
those
issues,
please
like
take
it
upon
yourself
to
take
that
up
right
to
ping
them
and
see
if
they're
still
working
on
it.
I
have
not
to
pick
issues
up
right
as
well.
We
should
be
trying
to
walk
the
release
team
board
during
these
meetings,
so
we
do
have
quite
a
bit
of
time.
I,
don't
know
if
you
want
to
go
through
that
George
yeah.
Absolutely
let.
A
H
A
A
H
So
everyone
should
be
taking
a
look
at
this
issue
and
seeing
if
it
refers
to
something
that
they
own
already
I
will
try
to
backlink
each
of
the
some
of
these.
Yes,
some
of
these
already
have
issues
or
PR
is
open
for
I'm,
so
trying
to
do
some
investigation
and
tied
them
together.
But
if,
if
one
of
these
look
like
you,
then
then
just
drop
a
note
on
this
this
issue,
what
I
want,
like
the
reason,
I
open?
This
is
what
I'd
like
to
do.
Moving
forward
is
I
think
towards
the
end
of
the
cycle.
H
We
look
at
the
retrospective
sheet
from
the
previous
cycle
and
go
oh
wow.
Those
are
things
that
we
did.
We
do
them.
Did
we
not
do
them?
Let's
talk
about
them
and
it
kind
of
like
there's
a
snowball
effect
of
the
things
from
the
previous
cycle
it
may
have
had
a
is
that
we
hadn't
checked
from
the
retrospective
sheet
of
the
previous
cycle,
so
this
tracking
issue
is
essentially
open
to
so
that
we
can
draw
it
out
on
each
of
those
issues.
A
Okay
sounds
good,
makes
sense
and
we'll
also
control
this
issue
and
try
to
pin
people
play
in
and
link
the
appropriate
peers
that
I
today
to
try
to
make
it
to
try
to
clean
something,
a
calico
and
other
than
that
I
can't
think
of
anything
else
right
now.
So
next
one
document
governor's
release
team
membership
criteria
and
Bakley
remember
lucky
working
on
it.
K
H
K
A
H
So
this
is,
this
is
another
one,
that's
on
walkie,
essentially
what
it
is
is
there
have.
There
are
people
who
are
on
the
release
team
and
then
and
then
they
leave,
and
we
want
to
see.
If
there
is
a
we
should
kind
of
fly
a
process
for
bringing
people
back
onto
the
release
without
having
to
oh
well,
you
have
to
serve
that
X
amount
of
times
as
a
shadow,
or
do
this
they
should
have
some
emeritus
status
granted
and
so
my
count
towards
yeah.
H
A
H
Understanding
it's
really
about
like
okay.
Well
see,
I
still
exists
for
a
certain
amount
of
time,
mom
for
the
last
supported
release.
So
at
what
point
should
we
turn
down
see
I
at
what
point
all
the
kind
of
fixes
are?
We
still
would
we
still
consider
merging
into
those
branches
and
they're.
You
know
they're,
honestly.
The
answer
is
just
super
critical
ones
right
if
they're
the
security
vulnerabilities
or
something
there's.
H
A
H
So
we've
had
more
of
maybe
four
or
five
PRS
come
through
for
this
and
various
fashions
from
I.
Think
Sasha,
as
well
as
all
we're
close
I
think
there
are
two
more
that
are
open,
one
around
deprecations
and
and
something
else
my
suggestion
is
to
have
a
kind
deprecation
label
and
instead
of
adding
another
field,
that's
like
a
release,
notes
deprecation
warning
field.
Instead,
the
tool
would
look
at
whether
or
not
the
label
is
kind
deprecation
and
make
a
determination
on
that.
H
But
we
just
keep
the
old
release
notes
so,
like
less,
I
think
it's
less
confusing
and
like
we're,
we've
been
adding
more
and
more
things
to
to
the
template,
and
you
know
I
already
noticed
that,
depending
on
depending
on
who's
doing
the
PR,
they
may
not
add
like
the
additional
documentation.
I
don't
want
to
add
another
field
that
won't
get
filled
out.
I
just
need
time
to
write
that
up
somewhere
and
propose
it
propose
the
label.
H
Yeah
yeah
yeah-
and
this
is
also
when
I'm
on
the
hook
to
review.
H
A
A
A
A
A
H
H
If
we
find,
because
this
has
been
open
for
a
bit
and
if
we
find
that,
like
it's
not
generally
useful
to
have
it,
then
we
maybe
remove
it
or
maybe
we
just
closed
the
issue
right,
like
ideally
its
Y
animal,
so
we
should
process
it
with
some
machine
and
do
what
is
that
food?
If
there's
no
food
to
do,
let's
just
close
it
you've
made
a
rhyme
there
by
the
way,
the
food
that
you
do.
C
A
Do
you
want
me
to
move
it
to
somewhere
so
waited
to
do?
Leave.