►
From YouTube: k8s 1.15 Burndown 20190617
Description
1.15 is imminent!
See https://github.com/kubernetes/sig-release/tree/master/releases/release-1.15 for more information
A
Cool
welcome
to
kubernetes
115
burned
down
on
june
17th
week.
11,
it's
our
target
release
date.
Are
we
going
to
ship
or
not
stay
tuned
to
find
out
and
as
always,
this
meeting
is
being
recorded
and
will
be
posted
to
a
public
YouTube
channel.
So
please
observe
the
kubernetes
code
of
conduct,
which
basically
boils
down
to
don't
be
a
jerk
and
I
will
pass
it
over
to
Kendrick
for
enhancements.
B
C
A
Okay,
the
failures
from
this
weekend:
they're,
not
something
that
needs
fixes
for
yeah.
C
I
think
everything
my
everything
involves
so
currently,
115
blocking
has
a
couple
jobs
listed
as
flakes,
and
they
really
they
really
just
been
a
bunch
of
flakes.
The
only
one
that
we
were
watching
this
morning
is
a
GC
reboot
test,
which
has
been
a
flaking
since
the
dawn
of
time
and
the
last
run
for
it.
It
was
Green,
so
effect
is
yeah.
D
C
C
E
C
E
Solve
those
two
issues,
but
though
some
seem
to
be
a
problem,
there
is
one
open,
PR,
Claire,
I
pinned
you
on
it.
Yesterday
it's
about
the
HPA
feedback,
writing
status,
7
I,
know
35,
I.
Don't
think
that
this
is
blocking.
It
looks
like
it's
additional
like
work.
Basically,
it
is
a
it's
trying
to
change
the
way
that
the
horizontal
pod
Otis
killer
gets
metrics
back
from
the
metric
server.
It
will
I,
don't
think
this
is
release
blocking,
but
I
just
wanted
your
feedback
on
on
this
one.
A
This
one
was
possibly
opened
on
Friday
after
our
meeting,
so
I
would
hope.
This
is
not
release
blocking
coming
in
so
late
yeah,
let's
confirm
with
sig
apps,
since
it
looks
like
that's
the
sig
linked
with
this
just
to
confirm,
but
I'm
gonna
say
unless
they
have
a
really
compelling
reason.
This
should
not
be
really
sparking.
Okay.
E
E
A
D
G
A
A
A
A
A
A
Cool
yeah
is
there
anything
comms
needs
from
myself
or
enhancements
or
anything.
G
Just
as
Claire
said
earlier,
we
started
meeting
will
be.
Will
today
be
the
official
release
for
1:15.
So
far
it
looks
like
everyone's
going
agreeing,
so
it
seems
likely
so
just
continuing
with
Friday.
So
there
were
a
couple
of
PRS
that
were
released
blocking
those
are
mentioned
on
the
meeting
notes
and
they
were
checked
by
a
the
PR
that
I
also
mentioned.
G
So
those
were
what
happened
Friday
and
then
something
that
I've
discussed
with
Tim
yeah
and
whether
or
not
7
9,
0,
3
0
should
be
cherry
picked
over
seems
that
it's
an
API
change
and
it's
relatively
big.
So
the
discussion
was
that,
instead
of
having
it
as
a
patch
addition
to
one
15.1,
we
should
bring
it
over
to
the
actual
release
branch
so
Tim
what
you
want
to
continue
this
discussion.
H
I'm
just
refreshing
my
memory
Monday
morning,
so
the
this
one,
so
the
I
think
the
main
differentiator
in
this
one
is
priority
important
soon,
so
that
should
not
block
the
release
and
seems
implicitly
like
something
they
couldn't
land
in
the
dot
1
patch
release.
So
it's
an
open
shirt,
big
against
115,
but
based
on
the
labeling,
blackbell
GTM
and
other
merge
criteria
and
not
be
labeled
critical,
urgent.
It
looks
like
one
15.1
patch
picture.
G
A
Thank
You
Cheryl,
so
if
we're
once
we
get
the
response
from
Sig
ups
that
their
issue
is
not
release
walking.
Let
me
know
how
I
can
help
with
the
cut
cutting
activities
today.
I
should
have
a
fair
amount
of
the
afternoon
free
to
help
you
any
way
you
need.
A
I
The
shadow
form
is
open
and
the
walkie
and
the
new
team
about
filling
in
a
contact
sheet
as
leaders
realized
I,
can't
share
the
results
with
people
until
I
actually
have
people's
Google
email
addresses,
and
the
other
thing
would
remind
everybody.
The
115
team
is,
please
update
your
your
team
handbooks,
your
release,
role,
handbooks
based
on
your
experience,
this
cycle,
there's
almost
certainly
something
that
changed
this
cycle
or
wasn't
complete
in
the
handbook
or
has
isn't
accurate
in
the
handbook
that
could
use
an
update.
This
is
not
limited
to
the
leads.
A
Cool
Thank
You
Josh
all
right.
If
there
are
no
any
other
questions
from
different
leads
today,
I
will
move
over
into
my
update,
so
the
upcoming
milestone
that
we
have
today
is
hopefully
it's
a
release
date.
We
are
going
to
try
to
get
a
quick
answer
on
this
open
issue
from
sake
apps.
If
they
don't
get
back
to
us,
given
it
doesn't
sound
like
it's
a
regression
and
they
submitted
the
cherry
pick
relatively
late.
A
I
will
probably
say
we
should
push
it
out
unless
somebody
tells
me
that
that's
an
absolutely
crazy
idea,
an
additional
update,
I
sent
out
an
email
this
morning
to
put
swag
sizes
into
the
115
contact
sheet.
So
I
would
ask
that
everybody.
Please
try
to
do
that
relatively
quickly,
so
we
can
get
all
of
y'all
the
swag
once
it
comes
through,
which
then
leads
to
the
next
item,
which
is
release
theme
and
the
person
from
the
CMC
f.
Who
is
helping?
A
Hopefully
this
is
our
last
burn
down
and
I
just
want
to
say
thank
you
to
everyone
for
all
the
hard
work
that
you
put
in
this
release
and
all
the
many
hours
of
meeting
time
and
dedication
and
all
of
the
effort,
because
truly
this
is
a
whole
group
effort
and
we
could
not
get
this
release
out
with
all
of
y'all.
So
I
wanted
to
thank
everyone
for
their
commitment
and
time
that
they've,
given
this
past
quarter
anything
else.
Anyone
wants
to
talk
about
today.
Anything
outside
to
the
agenda.