►
From YouTube: k8s 1.15 Release Team Meeting 20190506
Description
Info: http://bit.ly/k8s115
Calendar: http://bit.ly/k8s115cal
Team: http://bit.ly/115-releaseteam
Enhancements: http://bit.ly/k8s115-enhancements
Retro: http://bit.ly/115-retro
Handbooks: https://git.k8s.io/sig-release/release-team/role-handbooks
Slack: #sig-release on kubernetes.slack.com
Mailing List: kubernetes-release-team@ (the team) kubernetes-sig-release@ (the sig)
Youtube Playlist: https://bit.ly/k8s-sig-release-videos
A
Then
you
can
start
recording
hello.
Everyone
welcome
to
the
kubernetes
115
release
meeting.
It
is
week
five,
we
are
recording
this
and
it
will
be
posted
to
a
public
YouTube
channel.
So
please
remember
to
observe
the
kubernetes
code
of
conduct,
which
basically
means
don't
be
a
jerk
and
with
that,
let's
kick
it
off
and
I
will
pass
it
hold.
B
On
a
second
I'm,
actually
gonna
make
it
announcement
really
quick.
So
two
things
to
note:
there
is
a
new
release.
Managers
channel
within
slack,
so
I
would
like
for
everyone
to
direct
any
release,
related,
really
see
things.
Building
branches,
cutting
releases,
anything
like
that
directed
into
the
release
managers
channel
moving
forward.
The
second
one
is:
we
have
a
release
team
board
now
a
project
board
and
I
will
pop
that
in
the
chat
soon
I
did
some
loose
prioritization
on
the
release
team,
the
release,
engineering,
cig
release
overall
and
the
licensing
sub
projects.
B
There
are
a
lot
of
things
to
burn
down
at
this
point,
I
mean
like
over
150
issues.
So,
if
you're
actively
working
on
an
issue,
if
you
don't
have
anything
to
work
on
and
would
like
to
work
on
something,
there
are
things
that
are
tagged
with
help.
Now,
if
there
are
things
that
are
on
the
board
that
you
are
already
working
on,
be
sure
to
move
them
and
in
progress
there,
you
can
so
everything
has
been
prioritized
by
milestone
priority
kind
areas
so
on
and
so
forth.
If
you
see
anything,
that's
missing,
please!
B
C
Good,
just
what
I
wanted
another
Monday
morning
is
yet
another
slack
gin
on
you
to
now
maintain
and
watch.
So
it's
fantastic
I'm,
just
messin
thanks
team,
but
with
what's
going
on
we've
got
pretty
much.
We
had
an
instance
breeze
Tuesday,
it
kind
of
trickled
in
so
about
this
morning
with
exceptions
and
everything
like
that.
That's
what
I
came
through
we've
got
one,
that's
still
sort
of
outstanding
waiting
to
kind
of
see
what's
happening
with
that
one,
because
the
kept
is
still
in
provisional
state,
but
at
this
moment
we're
looking
pretty
good.
C
We've
got
46
that
are
on
the
board,
ready
to
start
the
interact,
as
we
start
heading
into
code
freeze.
So
that's
that's
pretty
good
from
what
we
had
it
was.
It
was
pretty
chaotic
for
I'd,
say
a
good
Monday
and
Tuesday
with
new
things
that
were
coming
online,
some
things
that
were
dropping
off
because
we
had
like
36
last
week
and
then
all
of
a
sudden
it
kind
of
bumped
up
and
then
it
sort
of
started
leveling
out.
So
it
there
was.
There
was
a
lot
of
activity
that
was
happening
in
regards
of
that.
C
Some
of
the
statistics
are
on
the
sheet,
as
everybody
can
probably
see.
So
we
have
really
just
down
says
down
one
from
last
week,
but
really
there
were.
There
was
actually
about
ten
additions
because
there
were
12
that
were
moved,
the
milestone
and
two
that
were
also
deferred,
so
there's
a
lot
of
activity
that
was
technically
happening
inside
of
the
particular
repo.
So
what
we
got
going
forward,
we
got
2300
features
19,
beta
and
4
with
inside
a
stable.
So
that's
what
we
had
to
look
forward
to
for
our
115
release
cycle.
D
Everyone
hope
everyone
is
having
a
wonderful
Monday.
So
in
the
world
of
CI
a
signal,
everything
is
looking
a
little
bit
clunky,
but
it's
actually
not
that
bad.
So
mastering.
For
me,
a
mustard
walking
the
one
thing
to
account
for
is
that
there
there's
a
unit
test,
I
went
straight
and
has
been,
has
been
cast
in
one
of
the
jobs
to
fail
everything
else,
everything
else
that
is
flaking
hey
again.
We
just
need
to
give
it
more
time
and
see
how
it
behaves,
but
nothing,
nothing
looks
too
bad
right
now,
master
upgrade
so
for
jobs.
D
Failing
for
flaking,
again,
nothing
serious.
Some
of
the
some
of
the
jumps
with
a
lot
of
failures.
I
don't
have
consistent.
It
is
failing
so
that
makes
that
makes
me
think
that
people
are
just
doing
our
work
on
KK
and
put
other
than
that
everything
looks
stable.
A
master
in
forming
a
town.
One
needs
a
little
bit
of
a
needs.
A
little
bit
of
love.
There's
a
so
one
of
the
one
of
the
people.
One
of
the
issues
of
we've
been
tracking
for
a
couple
of
weeks.
We
were
actually
we
actually
mislabeled
it.
D
It
turns
out
it's
for
it's
one
of
the
tests
that
is
shown
by
six
color
bill,
a
scalability
and
we've
a
weaker
in
contact
with
the
with
six
scalability
every
day,
they're
doing
they're
doing
the
work.
Apparently,
there
are
a
couple
issues
that
came
up
with
the
bomb
to
go,
want
off
some
performance,
some
performance
issues
that
they
are
seeing
some
work.
If
you're
interested
in
those
type
of
things,
you
can
click
on
the
link
and
follow
and
follow
the
conversation
alone.
We
interesting
other
than
that.
D
To
tell
there
yet
a
OpenStack
they're,
still
unopened,
they're
still
an
open
issue
with
open
labs,
the
police
work
they're,
actually
doing
they're
running
their
CI
jobs,
but
everything
on
the
on
the
master,
informing
job
itself
seems
to
be
behaving
okay,
and
that's
it.
That's
it
for
this
week.
Any
questions
comments,
concerns
that.
F
Everyone
Nicholas
couldn't
make
it
today,
so
I
will
be
given
the
update
on
of
behalf
I'm
Nina
bug
triage
shadow,
nothing
much
in
bug
triage
this
last
week,
Nicholas
has
created
a
bug
issued
truck
out
based
on
issues
and
PRS
are
on
the
currently
accepted
caps.
I
have
shared
a
link
to
the
spreadsheet
in
the
meeting,
notes
and
I'm
sure
every
updates
will
do
anybody
interested
can
follow
up
and
the
progress
there.
Thank
you.
G
Actually,
merging
the
mole
of
1.7
jobs
with
the
addition
of
1.15
jobs,
because
that
makes
the
task
easier,
I
think
we
merged,
as
we
split
this
past,
for
that
number
of
wanted
file
changes
are
lesser
and
you
could
spend
less
time
making
minor
changes,
but
I
think
that
actually
makes
the
job
doubles
the
job,
because
we
have
to
be
part
about
the
same
convict
files,
so
I
recommend
margin,
disliked
annoyed,
I'm,
doing
it
twice
and
making
a
permanent
change
in
the
timeline
template.
That's
it.
We
did
this
in
the
last
cycle.
G
H
That
was
one
so
the
enhancement
fleas
was
last
week
and
we
started
tracking
both
issues
and
starting
asking
owners.
If
those
issue
need
dogs,
I
have
disputed
the
task
among
the
members.
So
all
the
members
have
been
assigned
issue
so
that
I
can
start
ask
ish
owners
if
those
enhancement
need
Noakes
another
thing
fit
in
the
placeholder
PR
that
we
made
at
the
end
of
dailies
and
I've
been
teaching
the
dogs
I.
Think
that's
it.
So
we
focus
from
these
clips
from
this
week.
I
Okay,
we
have
a
bit
more
of
a
lengthy
update
this
week,
not
so
typical
for
release
notes,
but
anyway,
so
we
have
I've
put
up
the
draft
PR
for
this
week,
there's
a
link
to
it
and
we
got
together
to
have
a
meeting
last
week
that
all
the
members
of
the
release
notes
team.
So
we
had
a
couple
of
things
to
discuss
that
I'm
just
going
to
update
everybody
on
so
we're
continuing
development
of
the
release,
notes
website,
with
the
first
version
being
targeted
for
this
release.
I
1:15,
so
Jeff
is
working
on
finding
a
website
to
host
their
release.
Notes
website
currently
like
an
address,
and
we
had
some
questions
that
came
up
for
the
initial
design
that
we
thought
we
could
ask
the
members
of
the
release
team
just
for
some
initial
feedback,
so
I
created
a
survey
with
Survey
Monkey
is
here
if
I
come
and
drop
it
in
the
chat,
but
it's
it's
in
the
notes.
The
team
meeting
notes
for
everybody
and
it's
really
short.
It's
like
three
questions.
It's
very
simple,
straightforward.
I
Hopefully,
so
if
you
could
just
take
a
couple
of
minutes
and
fill
it
out,
that
would
be
great
we're
hoping
to
create
a
more
in-depth
survey
for
the
website
once
it's
actually
released
to
get
feedback
from
users
to
guide
development
for
the
second
version
of
the
website.
That
would
be
targeted
like
116
or
117
going
forward,
and
we
still
have
a
lot
of
questions
about
release,
notes
that
don't
have
great
answers
right
now
like
what
is
a
release
now,
even
it
as
the
most
basic
one
like
do.
We
include
all
the
bug
fixes.
I
Do
we
not
include
some
smaller
bug
fixes,
so
those
are
questions
that
are
still
out
there.
We
are
also
hoping
to
add
some
new
labels
that
developers
could
hopefully
tag
onto
their
PRS
like
primary
SIG.
That
would
help
release
notes
to
sort
their
the
notes
more
effectively
and
whether
or
not
they're
released
note
is
a
dependency
or
has
dependencies
that
we
wouldn't
be
able
to
recognize
otherwise,
or
it
would
just
make
it
easier
for
us
to
sort
them
and
to
make
sure
we
include
everything,
that's
important
in
the
release
notes.
I
I
J
A
B
B
B
E
Going
great
just
one
thing
for
tomorrow
would
I'd
be
cutting
for
l43
and
in
preparation
for
the
beta
cut.
I
would
be
gonna
sync
with
George
on
finding
a
time
to
do.
A
branch
forward
would
happen
sometime,
May
14th.
One
more
thing.
I
like
to
add,
is
that
my
it's
gonna
be
my
finals
week
soon.
So
this
week
and
the
following
week,
it's
gonna
be
super
busy
for
me.
E
A
E
So
I'll
do
that
and
then
thanks
Steven
for
making
that
PR
I'm
a
little
bit
swamped
right
now,
but
yeah
he's
doing
it
friends
trying
to
fit
everything
in
other
than
that.
I
think
that's
about
it
and
I
think
my
shadows
are
getting
the
hang
of
the
process
so
far
so
yeah,
that's
it
for
me.
Thank
you!
Cool.
A
E
It
was
I
thought
this
whole
time,
for
the
first
alpha
cut
was
because
of
my
setup,
so
I
thought
what's
going
on
what
am
I
not
doing
right,
but
it
turns
out
that
was
just
that
particular
commit
on
the
slash
release
repo.
So
it
was
from
there
and
I
kind
of
learned,
like
the
you
know,
workings
of
how
like
put
my
changes
onto
GCP
and
run
run
it
there
and
yeah
I've
kind
of
learned
a
lot
from
that
very
first
cut.
B
More
of
a
question
for
the
audience
I
was
I
was
thinking
about
it
recently
and
I
realized
that
I'm
not
sure
that
everyone
has
visibility
into
this
and
it
primarily
came
up
because
I
don't
have
full
visibility
into
this.
But
what
does
cutting
a
release?
Look
like?
Would
it
be
valuable
for
people
to
see
a
recording
of
a
branch
manager,
patch
release
manager,
cutting
a
release?
I
think
yes,
I!
Think
yes
and
it
would
be
a
cool
like
kind
of
a
mentoring,
starting
starting
opportunity
for
mentoring.
E
B
B
E
A
A
A
So
moving
on
to
release
lead,
update,
so
I've
put
in
some
of
the
upcoming
milestones
that
we
have
in
the
calendar,
so
this
Tuesday,
the
Alpha
3,
will
be
cut
and
the
111
jobs
will
be
removed.
As
already
mentioned,
May
14th
we're
planning
to
have
the
115
branch
cut
and
the
115
beta0
cut
again
Cheryl.
Let
me
know
if
we
need
to
adjust
those
dates
for
your
final
schedule.
I
don't
want
you
to
feel
totally
overwhelmed
and
school
is
really
important,
so
we
can
be
flexible
if
needed.
A
115
you
time
zone
meeting.
Thank
you
to
everyone
who
filled
out
the
various
polls
on
this
subject.
I've
sent
out
a
calendar,
invite
that
will
be
starting
these
on
Wednesdays.
They
will
be
at
9:00
a.m.
Eastern
to
9:30
Eastern,
so
only
half
an
hour,
don't
feel
like
you
have
to
attend
both
this
meeting
and
the
Wednesday
meeting.
The
Wednesday
meeting
is
offering
an
alternative
time
slot
to
people
who
are
in
EU
or
East
Coast
time
zones.
A
Who
may
be
this
particular
slot,
isn't
super
friendly
for
their
calendars,
though
I
would
still
like
to
get
a
representative
from
all
groups
on
the
Monday
call
to
give
updates
and
then
Wednesday.
We
can
do
any
follow-up
updates
that
happen
afterwards
or
just
do
sort
of
a
general
overview
for
those
released
team
members
who
can
attend
on
Mondays.
A
A
Think
the
last
update
I
had
that
I
forgot
to
put
in
here,
but
Cheryl
had
asked
me
via
slack
and
I,
think
there
are
any
PRS
that
are
specifically
related
to
this
current
release,
so
1:15
that
you
need
help
getting
approval
on.
You
all
should
be
able
to
at
me
to
get
the
lg
TM
/
approved
labels
applied.
So
if
you're
having
PRS
that
just
need
to
be
merged
through
and
you
need
someone
to
look
at
it.
You
all
can
feel
free
to
use
me
as
someone
to
do
that
again.
A
A
A
L
Okay,
yes,
so
I
don't
actually
put
back
there,
but
it
has
my
name
on
it.
So
I
will
talk
about
it,
so
I
am
working
or
have
worked
on
something
to
fully
automate
all
the
feet.
Things
for
me,
our
test
in
for
a
role
in
Billy's
team
is
supposed
to
do
I'm,
not
sure
what
to
say
about
it.
To
be
honest,
it's
a
thing
it's
going
to
happen.
It
will
make
things
easier
for
people,
I,
guess
one
fun
thing,
wife.
L
Bringing
up
perhaps
is
what
I
have
discovered
foots
in
k,
slash
release.
There
is
one
of
you.
Many
gigantic
bash
scripts
is
full
of
bad
assumptions
and
deprecated
lookups,
and
some
of
those
are
going
to
break.
So
if
anyone
knows
who
actually
owns
verse
so
that
we
can
talk
about
not
breaking
releases,
that
would
be
good.
L
Live
dot,
sh
or
liberal
e,
so
I
forget
which
way
around
forwards
go.
It's
assumes
that
the
test
grid,
config
Toyama
file,
is
authoritative,
which
it
isn't
there's
a
photo,
but
supposed
open
should
be
red.
Instead,
that's
the
bad
assumption.
It
also
assumes
that
some
file,
but
there's
only
maintained
by
deprecated
tool
that
we
are
moving
away
from,
will
continue
to
exist,
which
is
less
evident
from
participation,
but
is
also
an
issue.
B
L
M
B
B
M
B
B
So
so
one
more
time,
I'm
really
gonna
hammer
on
the
project.
Boards
I'm
gonna,
send
an
email
out
later
today,
as
well
as
talked
about
this
on
the
cig
release
meeting
tomorrow,
but
we
have
too
many
issues
up
and
we
have
too
many
issues.
We
have
too
many
open
PRS
like
it's
it's
kind
of
reading
through,
like
the
Tim
Hawk
and
oh,
my
god.
I
have
too
many
things
to
triage
mailing
mailing
lists
threads
like
we
have
the
same
issue,
so
please
make
it
your
priority
to
walk
that
that
release
team
board.
B
In
fact,
I
would
like
to
make
it
a
requirement
that
you
walk
the
release
team
board
for
the
release
team
meetings.
It
should
be
like
I.
Don't
want
to
do
it
this
time
around,
because
you
just
found
out
about
the
board,
but
for
next
week
we
should
start
doing
that
and
and
making
sure
that
everyone's
issues
are
up
to
date.
What
usually
happens
is
these
issues
bit
rot
over
time.
The
assignees
are
from
the
Sinese
from
previous
release.
Teams
are
still
assigned
to
them;
they
they
go
stale
and,
and
they
don't
get
done
so.
A
A
All
right,
if
not
the
I,
think
I'll
give
everyone
the
rest
of
their
Monday
back
as
a
reminder,
there
is
an
EU
meeting
on
Wednesday,
don't
feel
pressure
to
attend
both,
but
if
you
can
attend
that
you
won
and
it
works
better.
It
should
be
on
everyone's
calendar.
If
it's
not
on
your
calendar
ping
me
on
slack
and
I
will
add,
you
write
happy
Monday.
Everyone.