►
From YouTube: Kubernetes 1.10 release burndown meeting 20180302
Description
A
Welcome
everybody:
it
is
Friday
March,
2nd
2018.
This
is
the
kubernetes
1.10
release
burned
down.
Meeting
I,
am
your
host
Jason
singer,
Jamar's
aka,
snowy
landscape
photo
and
I
am
happy
to
go
over
the
meeting
agenda
and
minutes
with
everybody
here
today,
which
you
can
see
after
the
fact
that
bitly
slash,
Cates
110
burned
down
without
further
ado.
Let's
just
quickly
cut
to
the
timeline.
This
week
we
did.
The
beta
docs
PRS
are
due
for
review
today,
we're
in
the
middle
of
code.
Freeze,
we
are
accepting
exception
reviews.
A
We
have
done
three
of
three
so
far.
The
third
one
will
have
been
approved
today
timeline
next
week,
yet
another
beta,
Doc's
PRS
should
be
finalized
and
release
notes
draft
we
should
be
reviewing
and
refining
marketing
activities
are
swinging
in
full
motion,
getting
the
blog
reviewed
and
ready
to
get
out
the
door
and
making
sure
that
anything
that
we
think
is
in
the
release.
As
far
as
a
features
perspective
is
actually
in
there
or
not
and
validating
all
that
metrics
review,
there's
22
open
issues
in
the
milestone.
A
A
A
B
Okay,
so
network
has
fixed
a
test
panic
in
England
in
one
of
their
networking
tasks,
which
brought
both
ingress
and
slow
sweet
back
to
green,
so
they're
still
one
sick,
sick,
apps
bug
demo
set
which
come
that
cost,
both
the
gck
cereal
sweets
and
the
master
other
great
jobs
to
fail
there
two
fixes
one
is
still
open,
but
God
lgt
and
the
other
one
has
merged
this
morning.
I'm
going
to
follow
up
on
these
jobs
today,
hopefully
they
will
get
better
result.
B
Force
the
skip
scalability
suite
has
some
flakes
doing
recent
bronze
weight
hack
charged
last
night
and
seems
guy
found
good
conclusions
since
fixed
Irish
should
send
out
a
fix,
surely
and
last
finales
qadian
cubed
emails.
Sweet
seems
that
some
issue
was
wrong
after
success
in
pro
ben
has
some
fix
to
publish
a
latest
beta
beaut,
so
qadian
can
switch
to
just
fetch
the
latest
BW
the
rather
than
rely
on
the
riot
or
success
a
via
we
was
that
should
also
be
fixed
today.
I
will
follow
up
on
that
and
hopefully
next
Monday.
A
A
Fantastic,
so
cool.
Thank
you.
C
And
apologies
for
having
been
away
for
so
long,
not
just
from
meetings
but
I
have
not
been
attending
their
release.
Talks
as
I
optimally
would
have
liked
to
do
so.
I'm
getting
folks
back
on
track
and
plenty
of
PRS
are
going
to
miss
today's
deadline,
but
I
am
talking
to
people.
A
few
folks
have
actually
deemed
me
of
their
own
accord
today.
So
some
people
are
noticing
the
deadline
and
I
think
we're
gonna
be
okay.
C
C
I
mean
I'm
working
I
I
was
initially
more
optimistic
than
I
should
have
been
about
the
current
state
of
merged
Docs,
be
ours
against
one
at
ten
I
think
it
was
us.
People
I
understand
how
folks
get
confused
about
the
branching
strategy
for
the
docks.
It's
not
the
same.
We
know
this,
but
you
know
we
do
have
some
in,
and
it's
evident
looking
at
the
issues
in
the
future
tracking
spreadsheet
that
some
at
least
some
of
them
that
are
currently
flagged
as
needing
ducks.
C
A
C
D
Getting
off
of
mute
so
looking
at
my
list,
I
need
Nick,
you're,
Caleb,
Jason
Jennifer,
just
to
give
the
vlog
that
relief
loss
a
little
more
just
to
make
sure
that
we
are
communicating
the
features
correctly
and
that
we
have
all
of
them
in
there
and
if
any
of
them
need
to
be
removed,
you
know
please
do
so
and
then
also
if
you
can
give
the
key
messages
from
media.
A
look
I
just
put
together
at
QA
that
the
media
will
want
for
their
stories
and
I.
D
Think
that
the
responses
that
place
should
come
from
the
fume.
So
we
please
give
that
a
look.
If
you
don't
have
time
today,
then
Monday
or
Tuesday
next
week
would
be
great.
Looks
like
we're
all
good
with
the
five
vlog
series.
So
Caitlyn
is
moving
forward
with
that.
So
no
calls
like
no
action
there
and
then
I
sent
an
email
around
everybody,
with
the
release
blog
and
the
key
messages
for
media
with
timing
for
media
stories
recommendations.
A
I'm
asking
people
to
do
a
visible
plus
one
on
that
email
thread
that'll
at
least
let
you
know
who's
verified
and
gone
through
it,
and
okay
next
week
is
the
open
source
leadership
summit,
so
we're
gonna,
be
we're
gonna,
be
a
little
short-handed
I'm
gonna
be
at
that
I
know.
A
lot
of
other
people
are
as
well
II
who
are
Aparna
myself
another.
So
next
week
is
going
to
be
a
little
tricky
in
while
we're
actually
talking
about
that
real
quick.
A
E
D
D
A
D
C
A
E
F
Yeah,
frankly,
the
the
issue
that
we're
having
as
we're
going
through
this
is
sort
of
correlating
the
time
line
versus
the
branching
and
realizing
that
we're
not
entirely
sure
of
the
list
that
we're
getting,
which
ones
should
be
the
the
official
lists.
Now
you
just
mentioned
what
was
it
two
hundred
and
thirty-eight
issues
that
should
be
listed
here
and
I've
got
some
that
range
from
80
issues
to
500
issues
and
I'm,
not
sure
which
ones
of
these
I
need
to
pull
together
and
which
tags
I
need
to
be
pulling
out.
F
A
A
This
summit
thing
next
week
is
hard
timing.
Are
you
available
to
maybe
schedule?
The
kids
gives
an
hour
there's
three
of
us
early
next
week,
maybe
Monday
or
Tuesday,
and
the
evening
I.
E
A
C
Would
you
mind,
including
me
in
that
Jase
it's
Jennifer
just
because
you
know
I
have
some
historic
interest
in
the
answers
to
these
questions.
Yes,.