►
From YouTube: k8s 1.15 Burndown 20190604
Description
See https://github.com/kubernetes/sig-release/tree/master/releases/release-1.15 for more information
A
B
This
is
gonna,
be
pretty
short,
everything's,
looking
green
on
our
end.
So
right
now
we
are
tracking
28th,
there's
a
+1
on
there
for
the
dynamic
volume
count
that
is
waiting
still
for
an
exception
to
be
approve
or
denied
apologize
for
not
being
on
the
call.
Yesterday.
I
know
there
was
some
potential
to
talk
about
it,
so
all
waiting
kind
of
Claire.
Let
you
take
the
lead
on
that
to
figure
out
if
it's
a
thumbs-up
or
thumbs-down.
A
Those
are
the
reviewers,
but
it
looks
like
we
were
able
to
rally
a
couple
of
folks
to
review
and
it
seems
that
they
have
some
edits
and
looking
now
at
the
PR,
there
is
one
job
failing
so
I
might
try
to
sync
back
with
the
folks
who
joined
our
burn
down
call
yesterday
after
this
call
to
see
what
their
confidence
level
is
now
with
this
issue.
So
we'll
update
folks
after
that.
B
C
Couple
a
couple
things
cleaned
up:
they,
although
the
big
issue
right
now,
is
in
master
blocking
one
of
the
six
storage.
This
was
the
failure
was
related
to
one
of
the
to
one
label
for
a
certain
metric
being
it
was
changed
and
the
cost
the
cost
travels
from
the
air
for
one
of
the
heat
we
test,
that
is
only
been
fixed
in
the
a
and
seems
to
be
that's
the
only
thing
wrong
in
master
blocking.
C
Hopefully,
it's
kind
of
stayed
long,
wait
for
it,
I
mean,
hopefully
that's
gonna
be
resolved
in
master
blocking
is
gonna
stay
relatively
green
till
we
have
a
new
release
last,
even
forming
a
it's
getting
it's
getting
better.
So
one
of
the
cube
a
one
of
the
kinder
tests,
he
was
resolved
a
stands,
a
test
from
the
world
moved.
C
There
was
another
see
closed,
a
seed
cluster
lifecycle,
reboot
test
the
one.
A
double
was
flaking,
it's
looking
good
now
so
now
the
main
issues
from
mastering
forming
seem
to
leave
it
to
Kourtney,
Annette
and
six
calendars
or
in
their
work
or
DNS,
and
we
have
the
two,
the
two
piers
open.
There
was
some
doubt
about
whether
there
were
necessary
as
I
was
a
coordinate
regression
to
a
previous
court,
Ian
aspersion
good
area.
C
The
tests
are
still
failing.
So
so
probably
this
thing
still
in
Tibet
large
or
something
in
certain
losses
to
happen,
we're
gonna
get
in
there
a
try
to
get
little
bit
so
more
insider
knowledge
to
see
what
a
what
the
best
solutions
are.
This
is
an
a6
scalability.
There
were
three
of
them
that
we
were
tracking
and
two
of
them
got
resolved
and
and
some
and
so
not
the
test,
clear,
a
crop.
But
now
we
a
now
we
had
new
failures
for
some
reasons.
C
We
need
to
open
up
an
innovation,
get
the
conversation
as
soon
as
we
have
a
story.
I'll
bring
that
back
to
you
all
and
other
than
that.
That's
it
so
I
guess
the
color
for
right
now
is
a
yellow.
We
fixed
an
issue
with
the
with
the
six
storage
testing,
Lester
walking
and
that's
a
premier.
Anyone
has
any
questions,
comments,
yeah.
A
For
the
six
storage
one,
it
looks
like
that:
PR
is
only
missing
the
115
milestone,
so
I
can
add
it
to
the
115
miles,
so
no,
then,
hopefully,
that'll
get
merged
and
then
for
the
two
core
G&S
ones.
One
of
them
is
on
115
7/8
302,
the
other
one,
seven
eight,
oh
three,
three
is
right
now
tagged
for
116
are
both
of
those
needing
to
be
merged
for
115,
because
if
so
I
will
go
talk
to
sig
one
of
the
SIG's
about
these
Cardenas
wants
to
see
why
one
is
on
116.
C
D
A
E
A
G
A
A
Okay,
perhaps
no
update
from
branch
management,
then
or
I
can't
hear
anything
so
I
may
give
I
might
go
to
my
up
or
my
update
and
then
come
back.
If
we
can
get
audio
fixed
cool,
so
from
release
lead,
I
will
still
leave
yellow,
given
CI
signal
would
like
to
see
some
of
these
different
failures
got
cleaned
up,
especially
some
of
these
cube
ADM
one
since
I
think
the
cube
ADM
in
forming
jobs
have
been
failing
for
a
couple
of
weeks
now.
A
So
it
like
to
see
those
resolved
in
terms
of
upcoming
milestones,
no
changes
from
what
I
mentioned
yesterday.
Lots
of
activities
happening
as
we're
nearing
the
end
of
the
release
cycle
so
get
excited
lots
of
milestones
coming
up
and
for
all
the
leads
who
are
on
I
did
open
an
issue
for
assembling
the
116
release
team.
If
you
haven't
seen
it
make
sure
to
remember
I,
just
put
it
into
chat.
Remember
once
you
figure
out
your
secession
plan
to
note
who's
going
to
be
is
going
to
be
seceding
you
in
that
repo.
A
A
Yeah
I'm
like
nervous
to
do
it
when
it's
over
coupon
Shanghai,
just
in
case
we
miss
a
lot
of
folks
and
I,
know
that
there
have
been
a
couple
of
like
community
members,
not
on
the
team
who
added
items
around
the
various
like
milestone,
so
I'd
be
nervous.
We'd,
miss
we'd,
miss
folks,
doing
it
over
coop,
con
Shanghai
and
I.
Take
it.
The
following:
Thursday
following
the
release
is
a
bad
day
to
pick
the
20th.