►
From YouTube: k8s 1.15 Burndown 20190610
Description
See https://github.com/kubernetes/sig-release/tree/master/releases/release-1.15 for more information
A
C
Master
blocking
one
piston
Balkan
are
looking
good,
nothing
nothing's
broken
since
last
week,
going
back
so
that
leaves
us
with
mustard
trying
to
fix
mustard,
informing,
so
master
informing
is
currently
suffering
from
sick
scalability.
In
close
to
lifecycle,
this
color
will
attest.
We
get
by
a
we
get
by
a
we.
We
reached
out
to
extend
ability.
A
apparently
is
not
a
prowl
issue
is
actually
it's
actually
and
there's
actually
something
a
so
something
interesting
going
on.
Somebody
somewhere
in
there
apparently
is
some
of
the
feel
is.
C
Some
of
the
figures
are
we've
been
observing
are
due
to
the
jobs,
taking
a
lot
away,
taking
a
lot
of
just
taking
a
lot
of
memory,
but
that's
under
investigation
a
really
have
made
a
really
a
that's
all
today.
That's
all
we
know
right
now,
and
that
leaves
us
with
everyone's
favorite
tissue
core
DNS.
So,
after
a
lot
of
conversation,
we
I
think
there's
a
consensus
of
not
trying
to
do
the
upgrade
to
one
eight
one:
five,
a
virgin,
a
we're.
C
Just
gonna
revert
to
a
work
on
a
river
to
one
three
one:
the
PAPR,
that's
open
for
us
just
waiting
ages,
winning
approval.
We
got
a
bunch
of
comments
from
our
and
from
some
sick,
scalability
people
and
so
just
final.
A
final
approval,
some
of
them
and
I
included
a
I
wrote
it
in
the
notes,
a
78-51.
A
this
one
is
supposed
to
be
Joe's
where
you
know
long-term
worth.
What
should
we
be
able
to
specify,
but
a
one
version
of
Courtney
and
s?
C
You
actually
want
to
bootstrap
your
cluster
with
and
then
the
plan
right
now
seems
to
be
the
first
work
on
a
work
on
getting
a
on
lurching.
The
the
regression
to
our
DNA
is
1
3
1,
which
was
the
thing
that
we've
been
using
in
part
and
after
that
work
on
away
a
Excalibur.
Excalibur
is
scalability
its
kind
of
work
on
getting
78
851
a
working
to
work
into
what
should
you
be
able
to
specify
what
coordinates
version,
the
one
in
your
test
and
other
than
that
everything's
good.
A
A
A
C
With
the
coordinates
issue
is
actually
good
enough,
totally
holder
a
photo
release,
a
testing
at
the
upgrade
signal.
We
actually
been
getting
it
for
a
from
the
kinder
test
they
and
they
are
actually
they
are
actually
already
doing
the
a
already
doing
upgrades
and
all
that
and
everything
since
to
end
everything
seems
to
be
working.
So
as
far
as
worried
as
first
we
know
all
the
diseases
are
failing.
C
C
A
The
current
plan
is
to
enter
code
thought
tomorrow,
like
as
CI
signal.
How
are
you
feeling
about
that
plan?.
A
Cool
any
other
questions
for
CI
signal.
D
A
D
There's
a
lot
of
activity
over
the
weekend,
particularly
around
the
cube
or
the
core
dns
issues.
We
have
three
open
PRS,
the
only
one
this
really
I
would
consider
released.
Blocking
is
the
core
DNS
one
in
cube
up
the
other
core
dienes
issues
already
been
merged
or
the
other
PR
has
already
been
merged
or
closed,
I'm,
actually
I'm,
not
sure
but
kind
of
amusingly.
During
the
meeting
we
people
have
been
closing
the
accordion
s
cube
up
issue,
so
that
one
should
be
closing
pretty
soon
so
I
may
actually
shift
from
yellow
to
green.
A
Cool
and
then
same
question
for
you.
How
are
you
feeling,
with
the
current
plan
of
doing
code,
saw
tomorrow,
I'm.
E
Didn't
want
to
mention
the
meeting
links
the
links
to
the
issues
and
PRS
and
we're
actually
pointing
to
114
milestones
both
in
the
template
and
in
like
previous
meetings.
So
I
went
in
the
fix
codes,
but
if
you
opened
those
links
like
before
an
hour
ago,
you
are
actually
looking
at
114
issues
and
PRS
so
make
sure
you're
looking
at
the
right
milestone.
Thank.
A
Thank
you
for
fixing
that
cool
anything
else
for
bug
triage.
F
Hey
everyone
we
heard
about
32
PRS
March
since
last
seven
days,
one
PR,
since
yesterday,
I
did
only
one
day,
but
here
in
the
last
week
from
the
last
report,
they
were
filed
issues
because
testin
Farrell
is
going
away
and
we
are
merging
into
other
roles
of
oil
issues
that
each
of
the
new
role
whoever's
getting
new
responsibilities.
They
can
start
updating
handbooks,
but
from
that
I
think
Tim
pepper
had
mentioned
a
few
changes
that
other
handbooks
would
require.
Well
data
for
test,
infer
a
role
so.
F
F
The
branch
protector
was
put
on
the
broken
due
to
some
PRS,
which
were
reverted
and
the
bumps
are
in
so
everything
seems
to
be
fine.
We
lost
some
data
with
respect
to
metrics
and
the
middleware.
We
don't
know
how
the
what
the
pool
size
was,
etc.
If
you
look
at
velodrome,
you
might
miss
some
data
there,
that's
it,
but
everything
seems
to
be
back
now
and
we
are
able
to
monitor
okay.
A
Cool
well,
how
are
you
feeling
with
the
plan
to
go
into
code,
thought
tomorrow,
I'm.
A
F
That
we
are
close
to
the
end
of
the
release
and
it
should
be
good.
It
would
be
good
to
update
the
handbooks.
Yes,
there
was
one
confusion
around
the
guitar
and
the
code
freeze
phase
who
was
going
to
take
it
up.
There
was
some
communication
on
the
PR
around
release
manager
running
it
instead,
but
there
was
no
clarity
on
it,
so
it
would
be
nice
to
understand
who
is
going
to
take
it
up.
We
can
take
it
offline
and
update
the
issue.
F
F
F
A
Also,
just
to
close
the
loop
for
our
discussion
on
Friday,
where
we
left
off
is
we
were
going
to
defer
the
decision
to
or
the
final
decision
on
what
to
do
in
116
to
lock
e
as
the
incoming
release
lead
for
116
little
refresh
for
folks
is
on
Friday.
We
had
a
discussion
about
dissolving
the
test,
infra
roll
and
merging
those
responsibilities
into
branch
management,
and
then
CI
signal
and
the
majority
of
folks
on
the
call
thought
that
there
was
no
risk
to
doing
this.
A
F
H
So
we
have
18
PR
that
have
not
been
approved
yet
on
the
five
of
them.
Doesn't
have
a
look
good
to
me,
so
we
are
trying
to
leach
out
to
speed
up
the
process
so
that
I
can
have
look
good
to
me.
The
rest
which
f18
would
go,
but
we
we
can't
leach
the
openness
of
the
content
so
that
I
can
they
can
approve
those
those
PR.
The
reviewers
I
mean
have
given
the
thumbs
up,
the
the
the
PR
ready
to
be
more
to
be
made.
H
A
H
H
A
I
Yet
we're
a
bit
yellow
today,
trending
green-
hopefully
at
least
because
we
didn't
get
as
much
as
we
had
hoped
to
get
done
over
the
weekend.
There's
been
some
copy
editing
of
release,
notes
of
the
release
notes
draft.
As
far
as
editing
from
cig
leads.
It
seems
that
only
Jordan
has
been
accessing
the
document.
I
But
that's
one
thing
that
I
just
noticed
we'll
be
working
on
the
changelog
and
the
themes
over
the
week
and
the
weekend
and
I
still
haven't
gotten
the
release,
notes
Lee
decided,
but
it
will
be
decided
shortly
after
this
meeting.
So
I
will
update
the
pr
as
soon
as
I
have
that
information
and
have
made
it
from
us
cool.
A
A
F
F
E
H
E
J
J
Like
the
cloud
provider
idea,
we're
kicking
off
starting
in
the
steering,
steering
his
review
the
proposal
for
consolidation,
so
as
of
116,
everyone
should
be
full
steam
ahead.
The
hope
is
that
we've
got
most
of
the
things
that
we
need
to
be
done
by
cube
con
San
Diego.
So
that
might
be
a
good
time
to
highlight
it,
and
is
that.
E
Something
that
is
that
like
to
inside
baseball
at
this
point
like
once,
it
gets
closer
to
being
something
that
end-users
are
done.
That
makes
a
lot
of
sense
to
me,
but
one
thing
that
came
to
mind
was
the
deprecation
or
not
no
longer
serving
a
lot
of
the
extensions
resources,
like
that's
a
thing
that
in
the
115
timeframe,
we
really
want
everybody
in
the
world
switching
to
using
the
G,
a
workload
api's,
and
so
that's
like
a
thing
that
we
could
explain
and
say
this
is
coming
in
116.
E
E
There's
a
bunch
of
associated
stuff
there
examples
of
what
we've
done
for
other
projects
as
we
migrated
them.
I
can
like
you
to
kind
of
a
the
main
issue.
That's
tracking
all
this
we
can
sync
like
the
cloud
provider.
Stuff
I
think
would
be
fantastic
to
do
when
it's
like
one
release
away
from
being
a
thing.
We're
gonna
require
everyone
to
switch
to,
so
maybe
in
another
release,
or
so.
K
Hello
Oh,
so
it
looks
like
the
wall
assignment
issue,
which
was
to
merge
the
responsibilities
from
testing
front
into
branch
management,
so
it
wasn't
clear
Friday
whether
we
were
going
ahead
to
that.
But
since
this
issue
was
open,
I
am
assuming
that
or
it's
confirmed
or
yeah
in
in
terms
of
the
issue
that
we
are
bridging
those
responsibilities.
K
Well,
there
was
a
discussion
about
whether
or
not
those
were
going
to
be
automated
because
we
were
discussing
or
someone
brought
up,
that
the
release
tools
will
be
reflected,
and
perhaps
those
responsibilities
might
be
part
of
that
refactoring
process.
K
But
in
this
case
I'll
go
ahead
and
add
those
to
the
handbook
other
than
that
tomorrow
release
candidate,
one
will
be
cut
and
released
and
from
you
know,
hearing
what
George
doesn't
say
from
Stacy.
No,
it
looks
like
we're
in
the
green
and
yeah
so
that
looks
like
I
mean
it
looks
like
we're
good
to
go
with
that.
So
I
guess
that's
it
well.
A
Thank
you,
Cheryl.
Any
questions
for
a
branch
management
just.
J
A
comment
so
not
to
be
pessimistic,
but
let's
make
the
assumption
that
nothing
is
going
to
happen
with
release
engineering
cooling
for
116,
not
saying
that
that's
true
I
want
that
to
happen.
I'm
just
saying:
let's
take
everything
that
already
exists
in
the
handbooks
and
transfer
them
over
to
the
Associated
roles
and
then,
as
the
release,
engineering,
tooling
changes.
We
can
update
that
accordingly.
K
A
Thank
You
Cheryl
I'll
pass
it
over
emeritus
lead,
update.
L
Yeah,
so
we
have
nominations
for
successors
for
release.
Lead
of
course
comes
enhancements
in
branch
manager.
So
thank
you
all
for
nominating
folks,
I.
Think
out
of
your
shadows.
In
order
to
take
on
those
roles
for
1/16
for
CI
signal
bug,
triage
Doc's,
release
notes.
It
would
be
nice
to
get
a
nomination
sometime
this
week
for
who
to
take
that
over.
L
If
none
of
your
present
shadows
are
available,
for
whatever
reason
you're
not
be
able
to
do
shadow
succession
for
116,
then
please
contact
me
and
I'll
try
to
help
find
a
different
potential
lead
for
the
next
one
or,
if
you
having
trouble
deciding
within
your
shadows,
you
can
also
contact
me
and
I'm
happy
to
be
a
sounding
board.
Thanks.
A
Yes,
as
I
mentioned
at
the
very
we're
about
a
week
out
from
our
release
date,
so
you
should
know
by
now
or
have
a
really
good
idea
who
you
would
like
to
succeed
you.
So
we
can
end
this
release
cycle
with
a
fully
staffed,
116
team
and
the
sooner
we
get
the
leads
in
place.
The
sooner
we
can
get
the
shadow
survey
out
so
for
a
successor
can
get
their
shadows
so
try
to
do
it
as
soon
as
possible.
A
Those
are
my
reasons
for
yellow
the
upcoming
milestones
today
is
Doc's.
Last
call
tomorrow
we
are
planning
to
go
into
code,
fo,
we'll
check
in
tomorrow
at
our
regular
at
our
morning,
release
meeting
and
see
if
that's
we're,
still
in
a
good
place
to
go
into
code.
Thaw
assuming
we
are,
will
enter
code.
Thaw
will
also
have
the
115
hour,
see
release
and
then
on.
June
13th
is
the
cherry-pick
deadline.
A
Then
June
17th
is
our
target
release
date
and
then
the
current
plan
is
to
have
our
retro
on
June
20th
at
the
community
meeting
again
a
friendly
reminder
to
add
content
about
the
release
to
the
retro
dock.
Anything
you'd
like
to
discuss
how
things
went
things
that
you
think
we
should
keep
doing
things
you
think
we
should
stop
doing
things.
A
You
think
we
should
start
doing
put
it
there
and
then
again
nominate
your
successor
if
you
haven't
and
also
leads
make
sure
you
start
taking
some
time
to
update
your
handbooks
going
through
them
and
seeing
what
information
is
useful.
What's
out-of-date
what's
missing,
since
it
helps
both
your
successors
and
the
potential
shadows
get
an
idea
of
what
they're
going
to
need
to
do
during
the
release
and
it's
a
great
way
to
make
sure
that
context
is
easily
spread,
as
we
have
changing
of
leaves
and
shadows
cool.
A
J
J
J
There
have
been
a
lots
of
discussion
around
what
to
do
with
the
release:
engineering,
tooling,
how
we
function
as
a
group,
lots
of
things
to
be
said
there
and
more
PRS
and
I
have
time
to
link
there
right
now.
But
what
I
think
should
happen
is
that
there
has
been
discussion
about
what
the
process
and
procedure
is
for
patch
release,
management
and
I
know
that
patch
release
management
no
longer
lives
in
the
release
team,
but
the
branch
management
position
currently
lives
in
the
release.
J
Team
and
I
would
like
to
move
that
position
out
of
the
release
team
for
the
next
cycle
right.
So
the
proposal
which
I
will
write
at
some
point
will
be
that
the
release
managers
team
we're
not
going
to
call
it
a
tumor,
just
call
them
release
managers
because
that's
kind
of
what
is
set
on
github
and
different
contact
points
right
now.
The
release
managers
will
be
composed
will
live
under
release
engineering
sub
project
and
will
be
composed
of
both
the
patch
release,
man
team
and
the
branch
managers
right.
J
What
this
will
start
to
allow
us
to
do
is
build
a
succession
path
from
branch
management
into
patch
release
management
and
also
build
a
larger
pool
of
people
right.
So
nothing
will
change
with
the
people
who
are
currently.
Branch
managers
are
currently
branch
manager.
Shadows
will
keep
everyone
where
they
are,
but
what
I
want
to
do
is
get
those
people
to
the
point
where
they
start
to
know
about
the
security
disclosures
process
and
are
part
of
certain
lists
like
that,
and
we
can
start
to
build
a
right
now.
J
Alexandra
and
and
ping
Fei
right
as
branch
managers
right,
so
they
will
can
as
patch
release
managers.
So
they
will
continue
as
patch
release
managers,
but
I
want
to
start
building
that
pool,
and
you
know
whether
it
makes
sense
to
look
at
the
way
the
product
security
committee
is
doing
their
associates,
pool
and
graduating
people
into
full
full-time
at
release,
managers
or
full-time
release
managers.
We
want
to
start
seeing
what
works
for
that
and
the
only
way
to
happen.
J
C
So
on
is
yes
or
I'll.
Listen
the
CI
signal
world
a
we.
There
are
a
handful
of
flags
that
we
are
the
we
are
that
we
are
looking
at
other
than
that
we
are
gonna,
spend
a
rare
kind
of
spend
the
rest
of
the
release
it
just
just
going
to
the
drawer
project
or
and
see
which
ones
are
still
flakes,
and
we
need
to
keep
a.
We
need
to
keep
keeping
track
for
next
release
cycle
and
which
ones
they
have
resolved
and
I.
C
E
A
Yes,
George
or
Nicolas
is
that
something
y'all
can
help
with
today.