►
From YouTube: Kubernetes 1.12 Release Burndown Meeting 20180924
A
A
A
A
A
Well,
I
guess
I
will
go
ahead
and
get
started
in
the
meantime
and
we
can
circle
back
depending
on
when
coal
arrives.
I've
just
dropped
the
agenda
doc-link
in
the
zoo
meeting,
just
for
reference,
oh
and
there's
coal,
so
perfect.
This
is
Monday
September
24th.
Our
final
couple
of
days
on
the
112
release,
I'm
Tim
pepper,
your
release
lead,
and
this
is
a
recorded
meeting.
It
will
be
going
on
to
YouTube
shortly
after
the
meeting.
So
please
mind
our
code
of
conduct
and
be
awesome
people.
So
today,
where
are
we?
Things
are
so
close?
A
We've
got
our
overall
status,
there
I'm
saying
almost
screen,
because
we
still
have
one
nagging
issue,
but
so
basically
almost
nothing
merged
over
the
weekend.
As
expected,
there
are
a
few
relatively
minor,
critical,
urgent
things
that
came
in
doug
has
just
done
a
branch
fast
forward
pulling
that
I
think
it
was
two
things
from
master
over
to
the
release:
112
branch-
that
is
our
last
branch
fast
forward
in
a
normal
cycle.
A
Then
next
it
was
noted
at
the
end
of
last
week
that
are
publishing,
bought,
broke
and
there's
a
bunch
of
activity
there
around
fixing.
It
I
just
note
that
in
the
agenda,
I
will
follow
up
and
make
sure
all
of
that
stuff
is
done
this
week.
Nothing
major
I,
don't
think
they're.
The
main
thing
to
talk
about
is
thawing
master
coal.
What's
your
availability
to
do
that
today
and
my
inclination
would
to
say
would
be
to
say:
let's
do
it
as
soon
as
possible?
A
B
Yeah
I
can
do
that
like
pretty
much
now.
It
should
be
a
really
simple
change.
It's
just
a
config
change,
so
I
can
all
post
a
relevant
link
in
the
chat,
but
now
we
just
have
two
queries
defined
for
the
kubernetes
kubernetes
repo
one
for
the
release,
branch
and
the
master
branch,
and
then
one
for
all
the
other
branches,
so
I'm,
just
gonna
delete
the
one
for
the
release,
branch
and
master
and
make
the
other
one
apply
to
everything.
B
B
D
B
B
Yeah,
so
we'll
still
so,
the
big
thing
about
code
does
we're.
Gonna
have
a
ton
of
qdp
ours,
obviously
we'll
still
merge
in
batches
of
5g
ours.
Just
like
this
admit,
you
did
I,
don't
expect
problems
like
we
had
with
us
to
make.
You,
though,
submit
you
really
struggled
this
time
of
year,
because
it
would
just
burn
through
all
of
its
API
tokens
like
just
trying
to
sort
this
the
queue
because
of
how
many
things
were
in
the
queue
tied
should
not
really
be
affected
by
hue
sighs
really
at
all.
B
A
A
F
A
A
Yeah,
I
and
I
guess
that's
kind
of
like
that's,
also
the
gist
of
what
I'm
saying
like
I,
think
that
this
is
more
than
flaky,
but
with
only
two
PRS
and
the
the
it
being
in
flux.
It
was
not
our
focus
last
week,
so
I
think
if,
if
this
cripples
the
project
for
the
next
day
or
two
like,
it's
gonna,
really
shine
a
light
on
the
fact
that
no
this
is
this
is
failure.
This
is
not
just
flake
well,.
E
A
A
Okay,
so
in
terms
of
outstanding
issues,
then,
on
the
release
is
the
the
weak
finish
we
were
looking
at
some
concerns
around
upgrade,
but
cue,
medium
is
looking
solid
at
this
point.
As
far
as
I
understand,
I'm,
just
gonna
look,
closer
lifecycle,
I
guess
I
do
see.
Lube
Amir
is
there
anything
that
you
think
is
important
to?
Let
us
know
about
or
continue
to
look
green
from
cluster
lifecycle
side.
So.
A
It's
a
cherry
pick
back
to
111.
That
would
make
a
downgrade
test,
go
green
and
maybe
give
a
little
cleaner,
CI
signal
on
things,
but
not
is
not
is
worried
about
that.
One
particular
the
bigger
issue
here
is
that
there's
like
there's
been
some
I
guess
I
would
say
insufficient
concern
given
to
compatibility
and
the
compatibility
story
even
beyond
just
112.
A
Okay,
although
today
I
noticed
that
there
is
a
scalability
failure.
Looking
at
the
specific
failure,
it
doesn't
look
at
all
related
to
this,
and
that
was
our
one
area
that
we
were
wanting
to
see
that
we
hadn't
caused
some
instability,
so
I've
pinged
Wojtek
there
to
get
some
updates
on
whether
they're
worried
or
not.
But
it
doesn't
look
like
it's
anything
related
to
our
anticipated
watch
area
there.
A
So
continuing
to
think
that
is
good
and
I
think
all
and
pending
confirmation
from
Wojtek
I'll
drop
that
from
the
list
of
things
we're
tracking
this
week,
Grenn
I
know
you're
on
the
phone
and
I
know
you're
starting
a
new
job
today,
so
I
really
don't
want
to
call
on
you
to
speak
unless
you
really
want
to,
but
I
can
kind
of
mention
our
current
open
issues
and
PRS.
Otherwise,.
D
A
A
My
triage,
none
of
them
are
blockers
except
the
stuff
around
the
the
no
taints
and
scheduling,
and
we've
already
talked
about
that
and
then,
of
course,
the
release
notes
bucket
anything
that
comes
in
there
would
be
important
to
pr's
open
one.
Is
this
no
taint
scheduling
issue
that
is
something
I'm,
treating
as
a
release,
blocker
right
now
and
then
storage
into
n
test,
which
is
declared
not
blocker
in
the
PR
there?
A
C
Just
one
quick
gratification
I
was
looking
at
the
failing,
scalability
ones,
since
they
are
not
in
the
release
blocking
what
I
was
just
curious.
If
you,
if
you
were
looking
for
scalability
tests,
because
you
knew
that
that's
where
exactly.
A
I
mean,
since
we
wondered,
if
anything
weird
might
happen,
there
was
just
kind
of
separately
watching
and
I
also
do
the
same
thing.
I
think
I
got
this
bit
of
maybe
paranoia
from
Josh
burkas
at
the
end,
not
just
watching
our
core
dashboards,
but
a
couple
of
the
other
ones
like
scalability
and
cluster
on
life
cycle,
depending
on
what
the
current
issues
have
been
leading
up
like
if
there
have
been
some
wobbles
there
to
kind
of
proactively
go
beyond
and
look
on
their
dashboards
as
well
and
check
in
with
the
the
SIG's.
C
G
So
the
bright
red
in
the
agenda
notes.
There
are
a
couple
of
peers
that
are
pending
mm-hmm
and
the
first
one
I
see
that
anyone
can
anyone
can
lgt
and
this
one,
because
it
has
all
the
labels
and
Mouzone,
and
is
it
ready
to
be
much
because
anyone
can
do
damage
yeah.
A
I,
don't
think
it's
ready
to
be
merged.
Klaus
who's
working
on
this
PR
is
also
the
one
of
the
sig
leaves
there
for
scale
of
scheduling,
so
I
I'm
not
expecting
any
Drive
by
LG
teams
from
somebody
else.
That
would
be
a
strange
usurpation
of
his
leadership
there,
but
I
mean
I
suppose
it
might
be
worth
putting
a
hold
on
this,
but
I
I,
don't
know
I
I,
don't
see
it
is
necessary.
D
D
D
F
E
F
A
H
D
A
D
D
F
A
We
definitely
should
have
a
documented
process
and
the
input
and
output
artifacts
having
those
visible
would
be
valuable
because
one
of
the
ways
this
fails
over
time
is
incomplete,
set
of
stakeholders
approve
and
merge
something
other
stakeholders
get
broken
by
it.
They
want
to
revert
it,
and
you
have
this
sort
of
back
and
forth
in
a
poor
feedback
cycle,
and
it
takes
time
then
for
the
the
feedback
loop
to
settle
out
into
it.
Actually,
a
coherent
state,
so
careful
deliberate,
should
be
the
rule
of
the
game.
At
this
point
for
the
release.
A
H
H
Now
what
we've
done
is
I've
gone
through
Lyndsey's
gone
through
we've
gone
through,
there's
a
bunch
of
comments
on
some
items
that
may
or
may
not
be
user-facing.
What
we'll
probably
do
is
just
contact
these
submitters
on
those
and
if
we
don't
hear
back
from
them
right
away,
we'll
just
you
know
make
a
call
on
it.
There's
a
bunch
if.
A
H
H
What
you'll
see
is
that
there
are
some
significant,
some
significant
sections
like
there's
a
lot
of
changes
listed
under
cig
OpenStack
in
the
major
things,
and
yet
we
didn't
really
see
anything
come
up
for
individual
release,
notes,
there's
a
mention
of
custom
CFS
quota
period
in
the
major
themes
for
cig
note,
and
yet
there
there
are
zero
release,
notes
that
appear
to
have
anything
to
do
with
that,
which
means
which
basically
means
one
of
three
possibilities.
Possibility
one
is
the
release
notes:
are
there
I?
H
Just
didn't
you
just
I'm,
not
making
the
connection,
because
it
doesn't
use
the
word
custom,
CFS
Porta
period
to
somebody
just
you
know,
or
at
least
note
none
date
or
I
forgot.
What
the
third
possibility
is,
but
so
I
don't
know.
What's
going
on
there
and
I
haven't
had
a
chance
to
kind
of
dig
in
and
figure
it
out.
Yet
my.
A
Would
be
on
the
release,
note
none
route
and
and
I
would
say
for
those
couple
instances
send
appointed
message
to
the
sig
leadership
there
and
say
hey.
This
is
a
mismatch
and
y'all
our
suspicion
is
that
it's
a
just
an
issue
of
release,
note
nuns
and
any
all
ought
to
try,
maybe
aspire
little
higher
quality
to
the
release.
No
comment
on
your
PRS
and
as
reviewers
we
we
need
you
to
do
that.
H
A
H
The
other
thing
I
wanted
to
ask
is
I
actually
had
a
note
here
that
taint
notes,
my
condition:
I've
got
it
okay,
it
says
taint
note
by
condition
is
removed
to
beta
is
made,
and
then
it's
enabled
by
default.
Well,
my
note
is:
is
this
true
I
thought
it
was
still
at
risk,
but
then,
if
I'm
understanding
correctly
you're
considering
out
a
blocker,
so
if
it's
not
ready
we're
not
releasing
anyway,
yes,.
D
I
A
How
I
think
things
have
settled
down
at
this
point
the
the
issues
fairly
localized,
it's
an
interesting
bug
and
it's
just
taking
them
a
little
bit
of
time
to
figure
out
how
they
want
to
address
the
compatibility
story
there.
So
I
to
that
and
I
did
add
just
a
little
suggestion
today.
Just
a
reminder
on
this
front
up
at
the
very
top
and
known
issues.
So,
depending
on
the
outcome
of
that
PR
68
984,
it's
going
to
have
a
release
note.
A
H
A
We'll
all
I'll
keep
tracking
that
today
tomorrow
and,
let's
let
you
know
there
and
the
docker
or,
however,
to
what
bubbles
out
of
them
there.
A
I
A
Well,
that
brings
us
to
the
agenda
end
aside
from
really
pushing
on
this
one
particular
issue
on
monitoring
the
thaw
today
and
the
status
during
the
week
of
the
the
breakage
around
the
publishing
bot
feel
like
we're
in
good
shape,
and
it's
good
that
we
only
have
basically
one
thing
we're
looking
at
and
we
should
have
it
hopefully
resolved
in
the
next
day.
Ish
is
my
hope,
so
all
right,
one
last
call
for
any
thoughts
comments,
concerns.
C
I've
been
sending
out,
some
calendar
invites
to
the
but
milestone
burned
down
list
for
all
the
130
meetings,
but
I
kind
of
see
that
when
folks
try
to
accept
it
they're
running
into
some
issues,
so
I'm
kind
of
debugging
it
right
now
but
yeah.
Just
if
you,
if
people
can
watch
out
for
those
invites
once
again
that'll
be
awesome.
F
C
Yeah
I
kind
of
sent
out
the
invites
from
mine
on
Google
account,
but
yeah
I,
don't
know.
What's
going
on,
yeah
I
have
to
figure
that
Thanksgiving
a.
E
F
Would
be
there's
a
separation
between
big
we
could.
We
could
chat
climate
separation,
reading
the
calendars
and
the
mailing
lists.
The
milestone
burned
down
is
one
of
the
earlier
or
a
group
like
Google
Groups
I'm,
not
separate
from
the
cig
release
mailing
list
stuffing
calendar
yeah.
So
there
used
to
be
like
an
individual's
Google
account
that
sent
out
the
calendar
invites
to
the
burn
down.
But
now
we
move
to
a
shared
calendar,
because
you
know
single
point:
failure.
E
A
A
A
I
will
and
also
in
past
in
the
past,
there's
been
sort
of
the
portion
in
the
community
meeting
for
a
broad
discussion,
and
then
we
followed
on
also
I
think
in
the
sig
release
meeting
team
I'm.
Sorry,
the
sig
release
meeting
instead
of
the
release
team
meeting
and
that
things
that
meetings
timeslot
to
have
a
discussion
focused
amongst
us
as
well
to
kind
of
follow
on
so
there's
still
opportunity.
There.
A
A
All
right,
I
think
that's
everything
that
I
wanted
to
make
sure
we
talked
about
I
appreciate
all
of
your
help.
This
cycle
and
I
appreciate
those
of
you
who
have
committed
to
helping
in
the
next
cycle
as
well,
so
thanks
and
stay
tuned.
Hopefully
we
get
this
one
issue,
cracked
in
the
next
little
while
and
all
I'll
be
letting
people
know
about
the
the
release,
theme
and
stuff
too
and
I
think
I
have
everybody's
t-shirt
size
now
too,
so
there's
gonna
be
t-shirts.