►
From YouTube: Kubernetes 1.10 Release Burndown Meeting 20180315
Description
A
B
The
issue-
yes,
sorry
great,
thank
you.
Energy
problem,
alright
folks
are
going
to
get
it
started.
I
have
already
hit
the
record
button
because
I
wanted
to
get
that
update
on
that
bisection
work
that
is
continuing
will
be
hopefully
get
some
more
results
soon
and
Indo
say
if
you
want
to
drop,
feel
free,
but
you're
welcome
to
stay
around.
If
you
want
that
I
know
it's
late
there,
so
so.
B
Thanks
to
you,
it
is
Thursday
March,
15,
2018
I.
Am
your
host
and
release
leader
Jay,
singer
Dumars
and
we're
gonna
go
through
the
meeting
minutes
which
are
available
after
the
fact
at
bitly,
slash,
kids,
110
burn
down,
and
if
you
want
an
invite
to
this
meeting,
you
can
join
the
criminalities
burn
down.
Google,
Group
or
cig
release
and
you'll
get
an
invite
right
now.
The
community
meeting
is
happening.
B
B
If
we
need
it,
I
think,
given
that
we've
done
a
lot
of
work
already
on
trying
to
identify
issues
and
improvements,
it'll
be
a
pretty
quick,
retro,
quick
rundown
on
the
metrics,
we're
at
17
open
issues
in
the
milestone,
all
of
them
critical,
that's
up
to
date
or
up
three
and
over
the
course
of
two
days.
I
feel
like
we're
at
least
getting
traction
on
those
for
the
most
part,
so
we'll
get
an
update
from
Josh
in
just
a
moment
on
that
all
the
other
indicators
are
trending,
neutral
or
slightly
positive.
It's
all
good!
B
There's
a
list
of
open
PRS.
There
are
seven
and
they're
broken
out
by
status
in
here
and
basically
looks
like
everything
is
working
or
being
worked
on.
We
do
need
some
approvals
from
folks
and
some
a
couple
of
LG
teams
needed.
We
need
to
get
Janet
to
look
at
the
the
PR
that
is
six
zero.
Nine
eight
five
I'm
gonna
ping,
her
in
slack
and
see
if
I
can
get
some
attention
there
and
pretty
much
that's
the
size
of
things.
It's
these
seven
PRS
and
the
issues
that
josh
is
gonna
go
over.
B
C
As
usual,
I'm
still
in
the
process
of
updating
the
board,
the
so
some
of
the
items
in
the
issue
tracking
spreadsheet,
post
the
link
there
and
chat
it
hasn't
moved
but
always
convenient
to
have
it
posted
in
chat.
So
some
of
the
items
in
the
tracking
spreadsheet
have
been
updated.
Some
have
not
notable
update
since
yesterday,
cig
scheduling
says
the
rest
of
the
demon
set
feature
probably
will
be
punted
to
1:11,
but
I'll
know
more
when
I
attend
their
cig
meeting
today,
because
some
things
have
been
committed
and
I
wanted
to
know.
C
Something's
have
been
committed,
and
one
of
the
PRS
associated
with
that
feature
needs
to
be
committed,
because
right
now,
castes
are
broken
with
some
things
committed
in
other
things.
Not
so
we'll
see
what
that
actually
means
in
terms
of
bumping
it,
the
scalability
stuff
you
all
know
about
it,
hasn't
changed
beyond
what
we
already
know.
C
C
It's
just
that
it's
it's
after
we
were
supposed
to
have
closed
the
tree
that
it
doesn't
look
so
great.
The
the
issues
that
were
worried
about
remain
the
scalability
issues.
The
thanks
largely
to
the
efforts
of
Jordan
Lee,
get
all
of
the
upgrade
downgrade
things
are
getting
closed,
they're
not
all
closed
yet,
but
they
are
all
getting
closed,
yeah
and
should
be.
You
know,
based
on
that
close
one.
The
next
couple
of
days,
with
the
exception
of
the
PVC
protection,
one,
the.
C
B
D
Note
out
is
we
got
a
g-cloud
failure,
so
g-cloud
pushed
a
new
staging
and
kill
date
every
deprecated
flag,
and
that
makes
ologies
me
to
fail
for
like
the
entire
afternoon
yesterday,
so
that
fabricated
issue
was
open
half
year
ago
and
nobody
is
watching
it
and
fate
about
is
about
to
close
it
and,
like
yesterday
it
finally
they
get
rid
of
the
deprecated
flag
and
like
it,
by
thirst
like
crevalle.
In
I
added
item
to
ritual,
maybe
that
issue
is
fixed.
F
D
Then
that
it
looks
like
the
Alpha
feature,
a
failure
is
being
worked
on
and
the
PR
is
open.
I
saw
Janet
just
south
assigned
to
that
PR,
hopefully
that
one
can
go
E
as
soon
as
possible.
D
F
H
Doc's
are
more
or
less
in
the
same
shape
as
yesterday.
Josh
I'll
be
real
interested
to
hear
about
the
pieces
of
the
daemon
set
stuff,
since
that
Doc's
PR
is
already
merged
on
the
assumption
that
everything
is
complete
and
it
looks
oh
no,
it's
not.
No,
it's
not
it's
one
of
the
outstanding
ones.
C
H
H
If
you
forward
me,
the
meeting
and
ight
I'll
join
if
I
can
just
in
case
it
helps.
You
know
more
ears
more
eyes.
We.
C
H
And
I
look
there's
like
right
at
the
moment
we
seem
to
have
a
stable
number
of
Doc's
PRS
every
day
and
they
are
not
ever
the
same
PR.
So
little
things
are
continuing
to
roll
in.
They
are
fortunately,
at
this
point,
small
enough
I,
don't
think
any
more
big
ones
that
are
gonna
have
to
make
it
in
no
matter
what
are
gonna
happen,
but
Never
Say
Never
in
any
case,
pushing
out
the
release
is
helping
a
lot
on
this
front.
C
Originally,
when
I
realized
that
it
hadn't
made
any
progress
in
a
while
I
was
suggesting
bumping
it
to
111,
because,
partly
because
with
an
uncommitted,
technical
PR
were
like
wait.
We're
gonna
commit
this.
It's
gonna
hit
the
test
and
then
we're
gonna
do
our
see
a
day
later,
but
it
seems
like
the
other
parts
of
the
feature
that
have
already
committed,
have
already
broken
the
tests,
because
there's
a
bunch
of
tests,
a
bunch
of
tests
failed
stuff
associated
with
that.
It
almost
feels
like
we
already
paid
the
price
getting
the
feature
out
of
it
right.
H
Right
yeah,
so
I'll
join
if
I
can
I'm
I
also
put
this
in
the
notes
I'm
flying
tomorrow,
so
I
won't
be
able
to
attend
the
meeting
but
I'll
ping
I'll
picnic
or
look
at
the
notes.
I,
don't
think
I'll
have
any
updates
of
any
particular
utility
for
you
tomorrow
and
I'm
monitoring
a
channel
I'll
be
around
later
in
the
day,
I'm
just
not
I'm
in
the
air.
During
the
meeting.
Okay.
B
H
Right
and
really
exactly
so
and
yeah,
that's
all
I
got
cool.
B
E
E
So
that
section
is
small,
so
I'm
not
sure
if
networking
has
anything
additional
to
add
sim
with
security
as
well,
and
so
I've
spent
note
around
to
all
the
SIG's
just
asking
them
to
make
sure
that
we're
highlighting
the
main
features
that
they
wanted
to
highlight,
and
they
are
loaded
correctly
and
there's
a
couple
additional.
There
was
one
additional
feature
that
we're
going
to
be
removing
which
is
API
aggregation,
but
the
other
ones
looks
like
are
fine,
so
you're
working
with
a
cig
that
is
mentioned
in
the
blog
announcement.
E
Please
ask
them
to
go
in
today,
and/or
tomorrow,
just
to
review
their
section
and
make
update
and
then
I
look
towards.
You
know
your
and
Angie's
to
you
guys
to
go
in
here
and
make
sure
that
we
are
highlighting
everything
that
should
be
highlighted
in
this
I'd
really
like
to
have
a
solid
draft
that
we
would
be
open
to
sharing
with
media
for
interviews
by
like
Monday
end
of
day.
F
B
E
H
E
So
I
was
going
to
see
which
ones
have
made
edits
of
storage
on
top
of
it
and
then
kind
of
ping
apart
and
Brian
tomorrow,
and
just
saying
like
these
are
the
edits
that
have
been
made.
This
means
your
review,
but,
like
I
said,
security
and
networking
do
need
a
lot
of
attention
and
storage.
An
additional
feature
seems
to
be
on
top
of
it
right
now.
Okay,.
B
All
right
well
we'll
see
what
we
can
do
to
try
and
get
that
tidied
up
and
ready
to
go
so
I
noticed
also
the.
E
I'm
sorry,
before
moving
on
I
was
just
going
to
mention.
Some
of
these
changes
are
affecting
the
five-day
blog
series
for
topics
that
we've
already
highlighted
in
there.
So
if,
if
things
and
yourself
and
your
can
give
that
some
attention
as
well,
two
of
the
book,
two
of
the
five
blogs
have
been
typed.
So
we
need
to
replace
those
and
that
series
is
supposed
to
start
the
day
a
day
or
two
after
the
release
comes
out,
so
we
may
be
a
little
behind
there
just
because
some
of
the
laws
are
changing.
Oh
boy,.
B
B
E
E
Those
are
questions
that
we
get
in
interviews
and
every
single
release,
and
so,
if
we
can
pre
answer
those
ahead
of
time,
the
reporters
that
do
not
take
interviews
but
will
write
based
off
of
the
blog,
will
include
our
responses
and
their
stories,
and
so
that's
why
I've
created
that
additional
document
and
I
think
it's.
It's
really
important
for
companies
using
this
technology
and
companies
building
products
around
the
technology
to
to
read
to
read
your
answers.
There
right.
B
Okay,
this
feels
like
I,
don't
know.
This
is
just
sort
of
a
zeitgeist
thing
for
me,
but,
like
word,
we're
not
really
delivering
a
ton
of
stuff
this
time
around.
It
doesn't
feel
like
this
is
one
of
those
earth-shattering
like
hey.
It's,
you
know,
break
out
the
champagne
it's
more
like
yeah.
This
is
a
sakuni's
Rainey.
E
Yeah
and
you
know
what
that's
fine-
that's
completely
fine!
It's
just
hey!
You
know.
This
is
an
earth-shattering
here,
some
of
the
updates
that
we've
made
there's
the
progress,
we're
making
and
here's
what
what
the
things
have
been
working
on.
I
think
that
is
completely
fine,
but
the
media
will
be
very
interested
in
it
and
the
people
reading
their
stories
will
be
interested
in
it.
I've
already
been
pinged
multiple
times
asking
what's
coming
out,
so
does
not
have
to
be
earth-shattering
whatsoever.
E
C
B
Say
that
in
in
the
pinch
or
if
it
gets
down
to
the,
where
and
yank
out,
things
that
seem
superfluous
and
and
let's
go
with
the
shorter,
more
concise
blog
and
feel
free
to
yield
your
editors
pen
liberally,
because
I
do
think
that
it's
more
damaging
in
some
ways
to
make
a
lot
about
a
little.
You
know
or
make
a
lot
out
of
a
little
I'd.
Rather
have
it
just
be
a
just
an
interstitial
update
in
the
in
the
grander
arc
of
the
years
delivery,
yep.
E
J
H
B
Thank
You
Jennifer
sincerely
appreciate
it
on
another
related
note
sort
of
so
obviously
scalability
has
been
an
issue
or
a
bit
thorny
for
us
this
time.
Around
I
did
bring
this
up
as
a
concern
in
cig
architecture,
and
it's
not
really
a
cigar.
Contexture
thing
it's
really
about
more
at
the
steering
committee
level,
but
essentially
I
think
that
this
whole
thing
is
elucidated
that
we
need
to
get
more
people
involved
in
cig
scaling
and
widen.
I
Bit
here
actually
and
Noah
mentioned
that
we've
got
a
list
of
people
that
we're
waiting
for
responses
for
on
the
release.
Notes.
Thank
you
to
him
for
putting
that
together.
I
we
will
start
to
nag
SIG's
for
their
themes
shortly,
but
other
than
that
we're
we're
in
pretty
good
shape.
I,
don't
think
there
really
are
too
much
in
the
way
of
coherent
themes,
the
cyclists.
So
if
we
had
to,
we
could
pretty
much.
B
H
E
H
I
B
We
need
to
find
a
way
to
make
it
compelling
because
there's
a
lot
of
good
reasons
to
upgrade,
meaning
there's
a
ton
of
bug,
fixes,
there's
some
things
moving
to
beta
and
so
forth,
but
so
so
maybe
not
themes,
but
maybe
there's
something
in
there.
That's
like
hey!
Why
should
you
upgrade,
or
let's,
let's
put
our
put
our
hats
on
our
marketing
hats
about?
Why
why?
Why
would
an
operational
organization
want
to
upgrade
and
go
through
that
the
pain
of
doing
the
upgrade
I'll.
I
Tell
you
what
I
think
I'll
tell
you
what
I
think
honestly
I
think
that
if
we
took
a
combination
of
the
preview
blog
and
maybe
a
few
more
things
that
I
discovered
going
through
doing
the
doing
what's
new
I
think
we
could
probably
come
up
with
just
a
compelling
intro
that
we
can
add
to
the
top
of
the
release.
Notes
that
would
do
that
job.
Pretty
much.
Okay,.
H
I
No
I
agree
here.
The
preview
blog
is
kind
of
a
combination
of
those
two
things.
It's
kind
of
like
a
here's,
the
highlights
of
a
few
SIG's,
grouped
by
saying
the
descriptions
of
what
it
is
so
you're,
not
you
know,
reading
PR,
so
yeah,
but
I
think
we
could
I
think
we
can
come
up
with
something
compelling
if
we
have
to
that
solves
all
of
the
problems
that
we're
not
chasing
people
down
and
we're
not
leaving
it
as
one
big
amorphous
mass
that
nobody
can
see
why
they
should
upgrade.
Let's.
B
Give
it
a
let's
give
it
a
shot
and
see
we
can
come
up
with
I
do
want
to
sakes
if
they
feel
compelled
to
write
a
theme
great
sure,
but
there's
a
certain
amount
of
diminishing
returns,
I'm
trying
to
hassle
people,
because
we
have
a
lot
of
things
that
we
have
to
accomplish
and
babysitting
a
that
may
or
may
not
have
any
true
value
is
probably
not
one
of
those
good
uses
of
our
time.
I
absolutely
agree
wholeheartedly:
okay,
so
great!
Okay!
Thank
you!