►
From YouTube: Kubernetes 1.17 Release Team Meeting 20191105
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
and
happy
Monday
today
is
November
the
4th.
It
is
week
7
of
the
kubernetes
117
release
cycle.
My
name
is
Guinevere
Sankar
I
am
the
release
team,
lead
and
I'll
be
leading
this
meeting
as
well.
Today
that
came
out
wrong
now.
I
want
to
remind
everybody
that
we
are
under
the
community's
code
of
conduct.
A
B
C
C
We
have
some
flaky
jogs,
which
we
already
opened
an
issue
to
track
all
the
flaky
jobs,
and
we
are
going
to
update
this
issue
and
pick
the
required
people
to
to
figure
out
how
we
are
going
to
remove
this
strange
behavior
in
master,
informing
okay,
that
one
was
a
little
bit
messy,
but
the
right
people
have
already
happened
and
a
lot
of
progress
can
be
made.
Gosh
master
sailor
was
failing
and
with
a
skill
correctness,
master
slow
were
like
mostly
for
the
same
issues
that
is
possible.
C
Sig
is
the
storage,
so,
let's
see
Tim
I
have
already
already
pink
them
recently
is
some
guys
studying
assigned
cases
to
the
cells
so
I'm
expecting
the
next
days
to
have
some
opening
PR
screw
to
fix
it.
So
we
have
also,
with
this
master
job,
that
what
it
was
failing
a
fixed
PR
was
opened.
It's
approved
it's
in
a
multi
pool,
it
should
be
merged,
but
the
follow-up
is
needed.
I
have
already
bring
her,
so
there's
possible
people
to
do
the
follow-up
and
publish
the
images
that
we
need
for
the
jokes
to
to
succeed.
C
Other
jobs
cube
ATM
card
master
on
one
16
was
failing
the
it
emerged,
the
the
PR
that
they
were
supposed
to
fix.
It
was
much
today
and
we're
going
to
monitor
him
from
now
on.
Hopefully,
everything
is
fixed,
cube,
ATM
card
master
was
was
failing,
we
fight
out
which
PR
broke
the
test,
so
the
class
of
lifecycle
team
is
in
communication
with
there's
possible
people,
so
hopefully
they're
going
to
fix
it
in
the
next
day's
bill.
C
D
C
Okay,
so
let's
go
on
1.5
blocking
some,
only
one
flaky
tests
actually
to
you,
because
I
just
noticed
that
the
conformance
OpenStack
test
just
flaked,
but
it
was
like
only
one
flag
cream,
like
many
operons
I'm,
going
to
check
it
out
as
well,
and
if
we
need
to
open
an
issue,
I
will
also
update
the
document
and
put
the
issues.
Well,
the
digression
1.17
is
little
bit
flaky.
A
That
storage
test
that
is
failing
on
GCE
cos
Master.
Let's
see
there
are
wait.
A
C
Was
the
the
same
tests?
Okay,
so
I
think
that
the
problem
is
the
same
everywhere,
so
that
was
what
I
was
failing
over
the
week
and
we're
trying
to
communicate
with
them,
but
we
have
no
response.
Luckily,
today
we
had
some
response
from
some
of
the
guys.
I
sent
me
a
lot
of
messages
in
there.
It's
I'm
a
little
baby
spamming.
All
right,
yeah
also
North's
update
some
of
the
issues.
Thank
you
for
that,
and
they
give
me
some
details
about
the
changes
that
happened
in
the
code
by
the
broken
the
tests.
A
Okay:
okay,
great,
let
me
know
if
they
continue
to
be
slow.
I
can
make
him
I
can
throw
my.
D
A
few
comments
so
I
recently
added
a
cig
release.
Job
config
errors
board.
So
essentially,
this
is
the
aggregate
of
all
of
the
jobs
that
appeared
to
be
misconfigured,
but
I
couldn't
quite
nail
down
what
or
why
they
were
misconfigured.
Some
of
the
reasons
for
miss
configuration
might
have
been
the
job
isn't
correctly
named
or
doesn't
have
the
doesn't
have
like
latest
or
master
appended
to
the
end
of
it.
D
It's
maybe
it
was
generated
and
the
generation
script
automatically
puts
it
in
release
all
right
or
some
some
release
star
all
so
what
I
did
was
I
got
rid
of
all
of
the
all
of
the
x
dot
y
all
boards
and
moved
all
of
the
jobs
that
were
landing
on
those
boards
over
to
job
config
errors,
then
reconfigured,
the
the
config
Forker,
which
generates
the
new
release,
jobs
to
not
land
jobs
in
the
all
boards
anymore,
annulled
those
words
out.
Then
also
there
were
some
more
stuff.
D
There
are
a
bunch
of
ones
that
are
see
a
lot
like
cubes
ETL,
skew
jobs,
so
it
might
say,
like
one
twelve
one,
thirteen
when
it's
actually
referencing
stable
one
and
two,
which
are
totally
different
releases,
so
I'm
gonna
try
to
discern
what
those
jobs
actually
mean.
Some
of
them
are
also
automatically
generated,
so
I
need
to
also
like
one
fix
them
and
then
to
make
sure
that
the
generation
scripts
don't
generate
them
incorrectly.
Moving
forward.
A
D
E
F
Good
morning
evening,
wherever
you
are,
we
have
four
open
non-test
flakes.
We
are
currently
at
46,
that's
down
to
from
last
week.
We
have
also
priority
critical,
urgent
issues
that
is
at
5:00.
That's
down
one
from
last
week.
We
have
priority
open
importance
soon
and
that
is
at
23,
that
is
up
to
from
last
week.
Finally,
for
PRS,
we
have
open
53.
F
That's
up
for
critical
urgent
PRS
is
one
there's
no
change
from
last
week
and
important
soon
is
30,
and
that
is
down
one
from
last
week
for
the
open,
KK
issues
that
includes
tests
and
flakes.
We
are
at
60
that
is
up
from
last
week.
As
far
as
other
bug
triage
activities,
we
did
a
full
king
of
all
of
the
issues
and
PRS.
Last
week
there
was
only
a
few
responses.
F
A
G
Hello,
everyone
I
would
say
the
current
status
was
between
here
and
yellow,
because
we
have
a
total
of
44
enhancements
and
we
still
don't
have
any
response
on
the
docs
requirement
for
19
of
them
and
and
we
don't
have
a
placeholder
PR
for
12
of
the
enhancements
and
usually
what
we
observe
is
we
get
the
docs
in
to
what
one
day
before
the
deadline,
so
the
first
deadline
for
Doc's
is
number
8.
We
need
to
have
a
placeholder
player
by
then
so
yeah.
Hopefully
it
will
turn
green
by
a
day
or
two
before
the
deadline.
G
E
All
right,
let's,
let's
see
what
the
response
is
on
Wednesday,
because
it
is.
G
E
A
H
Monday
everybody
so
I
think
we're
looking
green.
This
week
we
have
got
the
beta
zero
release,
update
notes
and
twos
onto
the
website.
We've
also
updated
the
released
raft,
the
only
two
things
that
are
giving
me
some
kind
of
pause
this
week
are,
we
don't
have
any
known
issues
yet
and
I'm
assuming
there's
something
out
there.
I
Karen
hi
everyone
David's
in
a
hotel
room
with
unreliable
Wi-Fi
home,
so
I'll
be
giving
our
update.
Our
current
status
is,
yellow
and
and
David
will
be
meeting
with
sans
yep
on
Wednesday
to
get
dates
and
to
get
things
clean
again.
As
mentioned
we're
kind
of
just
laying
low
until
code
freeze
happens,
that's
not
it.
A
Great
thanks
so
much
all
right:
release
branch.
D
Hey
friends,
so
we're
going
to
be
cutting
the
117
0
beta
1
tomorrow,
I've
granted
sascha
access
temporary
access
to
GCB
to
do
that,
so
we're
we're
continuing
our
model
of
granting
people
temporary
access,
as
well
as
having
people
shadow
shadow,
the
release
process.
So
there
will
be
a
meeting
you
should
have
already
received
it
that
went
out
to
release
managers
as
well
as
kubernetes
release
team.
D
If
you're
interested
in
watching
Sasha
do
that
it's
going
to
be
11:00
Eastern
tomorrow,
yeah,
that's
that's
it
outside
of
that
everything's
going
pretty
well
there
going
to
be
some
updates
to
the
branch
manager
handbook
coming
very
soon
this
week,
as
well
as
an
update
to
the
release
cutting
template.
So
it's
pretty
clear.
What's
what
we're
doing
in
the
process
as
opposed
to
having
to
go?
Look
for
the
release
manager,
logs
or
the
scratchpad
to
understand
that.
A
And
me
button
all
right:
that's
sounding
like
release
brands.
Just
is
really
amazingly
well
oiled
machine.
Oh.
A
A
All
right,
Oh
next
is
me
great
all
right,
as
everyone
may
have
to
do
this
by
what
I've
been
talking
about.
This
is
the
first
week
of
burned
down.
We
are
doing
Monday
Wednesday
Friday
meetings
for
the
next
few
weeks
and
all
of
you
all
should
have
seen
that
pop
up
on
your
calendar,
I
apologize,
Monday
meeting
I
will
fix
that
as
well.
I
have
I
have
news
on
the
sixth
field
ability
collaboration
Maria
will
be
attending
the
sick
meeting
this
week.
So
we
will,
we
will
get
some.
A
We
will
get
some
collaboration
there
as
well
as
I
filed
an
issue
that
currently
links
to
a
Google
Doc
on
just
good
questions
to
bring
up
for
safe
scalability.
My
hope
is
that
we
will
work
with
that
for
the
rest
of
the
cycle
and
then
add
that
to
some
of
the
handbooks
just
make
it
part
of
the
regular
process
a
little
similar
to
the
sick
testing
on
call
semi
liaison,
so
code
freeze
is
coming
in
Thursday
November
14
I
was
just
finishing
typing.
That
I
will
send
an
announcement
today.
A
A
A
G
A
Right
right,
you
should
coordinate
with
the
enhancements
team,
which
so
far
has
been
fairly
uneventful,
but
you
know
code
freezes
less
than
two
weeks
away
and
yeah
and
I
see
what
you're
saying
because
stocks
deadline
is
on
the
eighth,
whereas
code
freeze
is
on
yes
a
bit
later.
So,
however,
we
should
know
by
the
eighth
we
should
know
by
the
end
of
the
week
whether
any
enhancements
are
going
to
not
make
it
or
we
should
at
least
get
a
better
picture
about
him.
Usually.
A
A
G
A
A
A
Love
this
done
column
yeah,
everybody
look,
I
have
to
scroll
so
much
so
many
done
things
awesome
ooh.
We
have
a
review
in
progress.
Just
do
that
in
progress,
investigate
automation,
okay,
and
to
do
and
the
backup.
Let's
see,
let
me
quickly
get
an
idea
all
right,
I'm
gonna
start
at
the
bottom.
With
the
release
perspective.
Let's.
A
E
D
For
the
it's
for
the
release,
retrospective
stuff,
no
progress
on
updating
the
issue,
but
I
know
there
was
progress
on
the
stuff
there
in
Claire.
I
didn't
get
a
chance
to
talk
to
you,
but
I
was
wondering
if
maybe
it's
a
good
idea
for
the
emeritus
advisor
to
handle
these
kinds
of
issues.
Transitions
from
a
is
between
really
cycle
to
a
release
cycle.
Does
that
make
sense
our
/?
Are
you
interested
in
taking
this
yeah.
J
F
I
A
A
D
L
No
yeah,
there
was
no
progress,
not
recent
is
still
trending.
I
have
been
trying
to
catch
up
on
all
the
all
the
what's
it
called
all
the
conversation
that's
been
going
on
on
that
and
also
I've
been
working
with
see
a
signal
to
try
to
just
get
a
rough
overview
of
how
much
we
are
testing.
What
kind
of
platforms
were?
L
Here's
a
we
using
for
testing
to
just
to
just
try
to
get
a
simple,
a
roadmap
of
what
things
we
need
to
test,
more
more
platforms
and
all
that
and
way
I
was
hoping
to
get
that
done
sometime
within
the
week
and
just
posturing
here
to
close
it
and
at
least
have
it
somewhere
in
the
keep
history.
For
this,
what
do
y'all
think.
A
L
D
L
F
D
D
D
Yeah
we
should
find
I
I
feel
like
part.
This
should
be-
and
this
is
this
is
Scoob
creepy
as
well,
but
I'd
like
enforcement
on,
if
something
lands
in
master
and
for
something
informing
or
blocking
it
shouldn't,
it
should
feel
like
we
should
have
tests
in
for
a
fail
out
if
it's
missing
an
owner
or
missing
a
missing
notification,
email
right.
D
L
D
L
D
A
So
yeah,
it's
way
more
fun
to
exist
this
way,
but
also
much
more
dangerous,
so
and
then
I
guess
Ben
is
to
help
just
person
on
test
test
SiC
testing,
so
this
should
also
be
more
codified
right.
This
is
something
we
should
read
out
to
reach
out
to
stick
testing
formulate
hey.
Who
is
your
go-to
person?
It's
fine!
If
that
has
been
for
right
now,
but
it's
probably
not
gonna
be
been
forever
and
it
doesn't
make
sense
to
have
it
be
like
resting
on
an
individual.
D
D
A
A
Know
he's
the
elder,
kubernetes
gone.I
I
don't
know
so
so
it
should.
It
should
a
fumarole,
sorry
details
yeah,
all
right,
let's
see
if
we
can
get
this
moving
great.
F
A
All
right,
I'll
round
the
wagons
on
this
with
Jeff
hi
Jeff.
You
seem
to
be
the
assignee
for
this,
that
that
may
or
may
not
be
accurate
or
appropriate.
So
I'll
take
a
look
yeah.
A
A
D
Actually,
moving
yeah
that
one
is
related
to
there
pr's
open
night,
Gwen
I
think
you
reviewed
both
of
them
about
yeah.
Exactly
about
adding
this
code
blocks
we
talked
about.
We
talked
about
the
deprecation
note
one
well,
we
talked
about
both
of
them
actually
in
the
sig
release
meeting.
So
in
the
deprecation
note,
one
I
have
opened
a
PR
to
add
the
kind
deprecation
label.
I
think
at
this
point,
multiple
people
have
approved
it,
because
it's
a
label
that
touches
everyone.
D
Will
not
once
we
create
once
that
label
merges
and
once
we
add
the
automation
to
do
what
I
had
in
mind,
which
is
essentially
if
a
PR
is
labeled
kind
deprecation
and
has
a
release.
Note,
then
the
release
note
will
be
treated
as
a
deprecation
note
right,
the
second
one
around
primary
sig.
What
I
asked
was
we
need
to
find
the
motivation
around
doing
this
right,
because,
just
just
like
the
deprecation
note,
I
don't
want
to
keep
adding
fields
to
the
PR
template.
You.
D
You
mentioned
on
the
the
review
to
that
like
it's
getting
huge
like
the
PR
templates
getting
huge,
and
it
is
kind
of
something
scary
for
a
new
contributor
to
walk
into
so
I
would
prefer
I
mean
as
especially,
if
we're
adding
another
cig
label
like
it.
It
feels
like
it's
gonna
get
confusing
quickly,
so
we
need
to
prove
that
the
motivation
for
doing
this
outweighs
the
potential
confusion,
yeah.
D
K
A
K
We
go
back
to
the
milestone
issue
because
I
have
to
blame
mr.
Augustus
for
this
yeah
blame
it
blame
Augustus.
No,
the
milestone
issue
that
you
assigned
yourself
to
work
on
with
me.
So
now
that
my
brain
has
been
refreshed,
I
cut
a
PR,
adding
a
bit
more
verbage
and
then
Tim
pepper
also
realized
that
cherry-picks
needed
a
little
bit
more
documentation,
his
PR
got
merged
and
then
Stephen
did
this
whole
tricky
thing
renaming
long
story
short
this
PR,
which
would
close
out
the
issue.
K
B
K
E
K
J
D
E
D
A
D
A
D
E
D
E
D
A
Sure,
I,
yes
and
and
everyone's
perspective
is
different.
Obviously,
I
have
a
very
different
perspective
than
other
folks.
This
is
this
seems
related
honestly
to
4:58
kubernetes,
really
steam
membership
criteria.
Yes,.
A
A
Really
disruptive
events
happen
at
work.
It's
it's
been
great,
so
sorry,
I
meant
to
do
some
work
on
that
last
week
and
all
of
a
sudden
I
was
like
one
of
two
people
left
on
my
team.
For
the
week.
That's
cool
anyway
I
investigate
automation
to
facilitate
tracking
spreadsheets.
We
are
nearing
like
doneness
on
this
one
right,
I.
D
A
B
That
was
actually
in
regard
to
stubbing
out
like
separating
enhancements
from
Docs.
They
both
still
be
in
the
same
like
sheet,
but
instead
of
having
like
this
massive
thing,
if
scroll
left
and
right
floor,
that's
actually
just
have
your
own
little
sheet
to
handle
it
on
and
then
having
like
one
sort
of
main
one
that
just
has
like
gives
you
a
quick
status
of
you
know
the
enhancements
even
perspective
in
from
the
docs
team,
so
you
can
sort
of
get
it
at
a
glance.
No.
D
That's
not
what
this
issue
is
open
for.
It
was
the
fact
that
it
was
the
fact
that
we
don't
have
a
lot
of
the
sheets
automated.
So
a
lot
of
the
work
that
you
all
have
been
doing
over
the
last
few
cycles
for
the
enhancement
sheath,
that's
part
of
it
right,
but
there
are.
There
are
multiple
roles
that
also
use
different
sheets,
that
some
of
you
might
not
even
know
about
right
that
they
might
only
use
internally
for
that
role,
so
making
sure
that
whatever
process
they
use
is
in
some
way
shape
or
form.
D
A
A
A
H
A
A
A
D
E
D
D
A
Yeah
yeah,
it
does
that's,
I
mean
I
can
work
with
it,
but
but
yeah
it's.
The
other
thing
is
that
I've
been
up
and
work
the
schedule
and
I
didn't
at
the
time.
I
didn't
entirely
know
how
those
tasks
would
align
and
exactly
when
they
were
at
so
I.
Didn't
I
didn't
edit
the
text
much
at
all
from
1:16.
No.
D
A
Feel
like
I,
feel
like
having
the
combination
of
the
schedule.
Next
to
the
content
has
been
really
working
for
me.
I
just
Nord
like
this
is
sweet.
Blah
yeah
I
mean
I
I've
gone
week
by
week,
but
mostly
for
like,
what's
the
next
big
thing
that
needs
to
happen
and
then
I
compared
it
to
the
schedule
so
anyway
yeah
it
could
definitely
be
more
cleaner
cleaned
up
anyway.
I
have
not
done
this
yet
that
is
all
it
is
two
minutes
to
ten.
So
have
we
any
information
on
the
backlog?
A
E
D
Yeah
we
were
discussing,
someone
has
a
PR
somewhere,
Jim
has
a
PR
I,
think
yeah,
so
Jim
has
a
PR
open
and
what
I
would
like
to
have
happen
is
the
work
on
his
PR
be
merged
in
with
the
recent
update
that
Tim
did
for
the
cherry-pick
guidelines
right
and
have
that
be
kind
of
like
a
reference
point
point
to
cherry-picks,
always
since
we're
talking
about
non
supported.
Releases
like
this
is
like
this
is
I
mean
this
isn't
even
a
release
team
thing:
this
is
more
release.
Engineering.
A
D
I
A
A
A
C
A
Alright,
except
for
geese,
alright
great!
Thank
you
everyone
for
your
time.
I
know
this
was
a
long
one.
My
hope
is
that
the
Wednesday
Friday
meetings
will,
just
you
know,
be
a
status
update,
discussion
on
how
to
best
approach,
blockers
and
issues
that
arise,
see
you
all
on
Wednesday
at
the
same
time
and
have
a
great
week
in
the
meantime
later.