►
From YouTube: k8s 1.15 Burndown 20190614
Description
1.15 is imminent!
See https://github.com/kubernetes/sig-release/tree/master/releases/release-1.15 for more information
A
Well,
welcome
to
burn
down
Friday
June
14th.
As
a
reminder,
this
meeting
is
being
recorded
and
will
be
posted
to
a
public
YouTube
channel.
So
please
follow
the
kubrana
use
code
of
conduct,
which
basically
boils
down
to
don't
be
a
jerk
and
I
will
pass
it
over
to
Kendrick
for
enhancements,
update
yeah.
A
C
A
C
A
Cool
any
questions
on
the
CI
signal
things
going
on.
A
Ok,
perhaps
not
I,
do
see
what
looks
to
be
three
open
issues
against
or
the
reopen
P
ours
against
the
115
milestone.
So
I
might
see
if
the
bug
triage
team
and
myself
can
check
on
these
and
see
if
these
need
to
be
cherry
picked
in
or
if
they
can
go
in
subsequent
patches.
D
The
round
trip
testing
can
go
in
a
subsequent
patch
release,
I
think
the
IPV
s
and
the
nil
pointer
ones.
The
null
pointer
especially,
would
be
a
regression,
so
I
think
that
needs
to
go
into
115.
The
I
PBS
one
is
fixing
an
issue
that
is
also
in
the
114
release
as
far
as
I
know,
but
it
is
a
fairly
critical
issue,
so
that's
kind
of
on
the
bubble
whether
it's
really
considered
release
blocking
okay.
D
E
E
F
Hey
everyone.
We
had
a
happy
quarter,
so
we
have
about
51
PRS
merged
since
seven
state,
seven
days
and
37
cents.
One
day
since
our
last
meeting
so
yeah
we
had
a
quota,
so
we
can
see
a
bump
waiting
on
pull
requests
for
both
the
issues
that
we
for
for
splitting
the
tasks
of
tests
intra.
So
that's
the
status
looks
green.
A
G
G
H
I
I
E
J
Hello,
so
all
right,
the
official
release
since
June
17,
if
all
goes
well,
then,
will
happen
on
that
day,
but
I've
been
keeping
an
eye
on
the
issue.
Seven
eight
triple
nine,
which
is
on
the
meetings
note
and
a
couple
of
others
that
were
just
mentioned
by
Jordan
earlier
so
yeah,
just
I,
think
yeah
keeping
an
eye
on
slack
and
whatever
that
needs
to
be
cherry
picked
over.
A
All
right,
then,
for
my
update
target
date
is
Monday
for
the
release
and
I
think
that
is
our
last
target
milestone
again,
if
all
goes
well,
I'm
gonna
say
that
the
release
color
right
now
is
for
me,
yellow
just
because
we
do
have
these
two
issues
that
it
sounds
like.
We
want
to
be
able
to
get
into
the
release
before
we
hit
Monday
and
given
that
today
is
Friday
and
I'm,
assuming
no
one
wants
to
work
over
their
weekend.
So
I
should
be
sad.
A
J
Yes,
so
there
was
one
yesterday,
I
was
just
in
like
you
know.
How,
like
slack,
has
this
message
thing
and
you
should
don't
send
its
thumb
trance.
So
that's
what
happened
was
still
in
dress,
so
there
was
one
that
happened
yesterday.
Only
one
PR
was
merged
over
so
today
I
will
do
another
one
around
2
p.m.
actually.