►
From YouTube: Kubernetes 1.10 Release Burndown Meeting 20180323
Description
A
Welcome
everybody:
this
is
the
kubernetes
1.10
release
team
meeting.
It
is
Friday
March,
23rd
2018,
and
with
luck
this
will
be
the
penultimate
meeting
of
the
release
team
for
1.10
and
without
further
ado
I'm
going
to
go
ahead
and
share
my
screen
and
we'll
walk
through
timeline
and
go
through
the
meeting
minutes.
A
Today,
timeline:
let's
go
through
the
risk
assessment,
this
one
popped
up
and
I'm,
not
exactly
sure
where
this
came
from
or
why,
but
it
looks
like
a
bump
and
heap
stir
see
if
any
changes
have
happened
on
this.
No
no
context
does
anybody
know
anything
about
this
because
there's
no
cig,
it's
a
version
bump
and
there
doesn't
seem
to
be
any
context
whatsoever.
B
A
So
the
the
thing
is,
though,
that
we
don't
bump
versions
on
patch
releases,
because
technically
a
a
bump
and
a
version
is
a
feature
not
a
bug
fix
unless
the
unless
the
bump
is
to
specifically
address
known
issues,
I
mean
there
are
some
issues
associated
with
this,
but
it's
mostly
just
performance
improvements
and
stuff
like
that.
So
I'm
I'm
really
not
feeling
super
comfortable
with
this,
especially
since
the
release
is
going
to
go
out
on
Monday.
A
The
people
who
are
associated
with
this
PR
are
apparently
in
Europe
and
Asia.
So
there's
a
gap
there
I
can
follow
it.
This
weekend
and
I
might
ask
for
special
dispensation
from
the
release
team
in
the
release
channel
over
the
weekend,
but
I'm
I'm
feeling
pretty
pretty
sketch
about
this
particular
change.
I.
A
Yeah,
it's
I
mean
it's
not
gonna
merge
because
it's
a
cherry
pick.
So
the
only
way
this
would
merge
is
if,
if
Caleb
approves
it
and
merges
it
wait
so.
A
A
A
C
A
A
D
Yes,
okay
anyway,
so
I
believe
to
our
first
flying.
So
she
can't
comment
on
it,
but
we
were
working
on
making
sure
all
of
this
was
is
documented
in
the
release
notes,
as
I
told
her
yesterday,
I
up
until
yesterday.
I
was
really
good
in
cynic,
so
today
and
Monday
are
well,
and
the
weekend
are
my
days
to
make
sure
that
the
last
well
I
might
as
well
get
my
update
now.
D
A
A
E
E
A
B
A
F
One
quick
question
say
any
person
who
who
we
know
we
can
like
work
with
to
figure
out
why
it's
not
properly
come
to
do.
We
have
an
owner
for
the
job
at
all.
E
Looks
like
between
six
and
so
ban
has
fix
our
the
queue,
a
demeaning
job
for
number
inch
of
brilliant.
So
so,
for
example,
the
cube
admin
110
job
is
working.
G
F
A
Alright,
well
we'll
trust
that,
based
on
the
signal
we
have
the
the
history
and
where
we're
at
and
the
release
cycle,
that
this
is
not
a
blocker
that
it's
just
something
that
needs
to
be
resolved.
And
maybe
we
can
put
this
in
the
retro
for
for
next
time,
because
111
this
will
come
up
again
guaranteed.
E
E
A
A
A
E
Isn't
it
the
gray
team
need
he?
So
this
does
not
reach
any
likes,
green
or
red
signals
right.
It's
just
like
performance
data.
Oh
oh.
C
A
E
I'd
like
to
invite
signals
committee
into
Monday's,
burned,
meeting
and
asked
them
to
sign
off
on
this.
Okay.
A
E
H
A
Okay,
this
is
the
one
we
were
just
talking
about,
which
we
also
agreed
is
we're
gonna,
pull
out
of
milestones
that
correct.
E
A
Scalability
we've
got
a
bead
on
that
and
that's
this
accumulator
good.
Okay,
that
all
looks
good
fantastic,
oh
sweet
relief,
open
PRS!
These
are
all
the
they're
in
progress.
I
pinks
the
perverse
on
two
of
the
three
because
there
weren't
getting
approved
so
hopefully
those
will
happen
and,
as
we
saw
earlier
this
one,
the
pod
schedule
book
is
missing,
passing
tests
so
hopefully,
once
those
are
in
place,
that'll
that'll
go
through
and
merge
any
any
idea
about.
If
there's
flakes
happening
in
the
the
submit
queue
right
now
said
that
might
inhibit
that
from
merging
I.
E
A
A
B
A
B
A
I
So
I
am
just
waiting
for
confirmation
from
Brian
on
that.
One
of
the
edits
that
he
requested
in
the
blog
release
has
been
clarified
to
his
satisfaction
and
then
there's
a
couple
things
that
we're
filling
out
like
links
to
release,
notes
and
making
sure
that
the
wording
for
the
future
blogs
are
consistent,
but
other
than
that.
In
terms
of
that
actual,
like
intro
paragraph
and
the
meat
of
the
futures,
everyone
works
on
those
the
last
several
days
and
we
are
in
a
phenomenal
place
for
Monday
we're
really
happy
there.
I
I
Blog
draft,
as
well
as
the
media
FAQ
out
to
14
other
publications,
most
of
them
have
indicated
that
they
will
write
based
off
of
what
we
sent
them
and
they'll
follow
up
with
any
questions
that
they
have,
which
is
wonderful,
because
the
writing
off
of
our
announcement
and
I've
gotten.
Some
requests
from
some
of
the
companies
like
Red
Hat,
core
OS
and
VMware
and
Google
just
double
checking
what
features
did
make
it
into
the
release,
what
the
release
date
and
time
are
going
to
be
because
they
want
to
schedule
their
blogs
with
us
before
us.
I
So
right
now,
I'm,
very,
very
happy
and
where
we
are
scheduling
the
webinar
we
I
mean
we
have
one
more
person
scheduled
for
the
blog
series.
So
we
in
terms
of
marketing
like
we
are
in
the
homestretch
and
next
week.
Hopefully
we
can
just
watch
on
all
the
great
coverage
trickling.
A
It's
fantastic
boy:
it's
been
a
rollercoaster.
Thank
you
so
much
for
your
incredible
work
on
this.
It
has
taken
a
lot
of
diligence
and
follow-up
to
make
sure
that
this
was
complete.
You
know,
I
talked
to
talked
to
Brian
grant.
Yesterday
a
little
bit
as
I
was
asking
to
review
the
blog
one
last
time,
and
he
said
you
know,
we've
said
that
we
wanted
to
do
a
stabilization
release
for
awhile
and
it
sort
of
had
this
sort
of
accidentally
happened
when
ten
is
essentially
I
mean.
G
A
A
Stabilization
in
the
sense
that
moving
moving
things
to
betas
is
really
super
important,
so
in
a
sense
I
mean
those
all.
Those
moves
to
beta
are
also
a
kind
of
stabilization.
I
mean
and
I'm
not
GA
features
per
se,
but
just
the
track
is
there
progressing
forward,
which
is
good
sure
right,
yep,
you
know,
are
you
in
some
sort
of
undisclosed,
location?
A
A
A
D
Just
she
just
slacked
me
an
old
on
their
game:
okay,
yeah.
We
just
I
need
to
I.
Just
I
need
to
confirm
the
release,
notes
the
ultimate
release
notes,
URL
I
had
I
had
sent
her
the
so
anybody
here
can
probably
answer
this
question.
I'm
ahead
sent
her
this
message
and
she
had
said
yeah.
She
thought
so,
but
I
just
dropped
it
in
the
chat.
But
if
anybody
can
look
at
that
and
go
yeah
because
she
just
sent
me
a
note
that
says
she
thinks
we
may
have
changed
it
from
one
nine.
A
That
that
does
not
that's
correct
as
far
as
I
know,
yeah
I
mean
I.
Think
that's
right.
D
J
D
J
J
And
yeah
and
we'll
need
to
make
sure
that
nago
is
looking
at
there
rather
than
in
the
features,
but
that's
that's
impulses.
Robot.
Another
change.
Okay,
I
was.
A
C
J
C
A
J
I
was
I
was
I,
was
just
well
so
I,
pinged,
Tim,
all
Clara
back
channels
here,
stuff,
pretty
anything
bad
about
the
PR
he
meets
to
approve
and
oh
did
get
some
more
context
on
that
heap
stir
bub.
It
is
from
Sega
instrumentation,
but
those
folks
are
in
Warsaw
as
you
yeah,
so
it
it
doesn't
sound
critical
for
this
release,
although
they
just
there
are
some
bug
fixes
there
I
told
them
to
follow
up
on
the
in
the
issue.
Okay,.
A
J
A
And
if
it
is
I
mean
this
is
one
of
those
things
were,
and
this
is
going
to
be
up
to
you
as
branch
manager
for
for
this
period,
if,
if
this
is
something
that
you
feel
that
can
go
into
the
branch
and
not
destabilize
and
throw
us
off
and
I
will,
in
this
case,
defer
to
your
judgment.
So
if
you,
if
you
are
able
to
do
the
due
diligence
around
that
decision,
that
would
be
greatly
helpful
sounds
good.
Thanks.
Cap,
alright
I
think
that's
the
end
of
our
regularly
scheduled
topics.
H
Just
wanted
to
say
thanks
to
everybody:
I
won't
be
here
Monday
or
Tuesday,
because
I'll
be
all
speech
in
a
class,
but
for
my
reception
bone
group,
the
release
team.
This
has
been
a
incredibly
fun
slightly
crazy.
More
than
slightly
crazy,
endeavor
and
I
mean
I,
don't
know.
If
you
all
know
this
was
actually
my
first
contribution
of
the
project.
So
this
was
a
blast
and
I
just
want
to
thank
everybody
and.
D
C
A
A
Alright
team
I
could
not
be
more
proud
and
honored
to
work
with
all
of
you.
This
has
been
a
thrilling
experience
and
Monday.
We're
gonna
put
this
thing
out
in
the
world
after
night.
What
seems
like
a
million
years
of
effort,
but
really
three
months
of
concerted
strategic
effort
to
get
this
happening
truly
appreciate.
All
of
your
help
and
again,
thank
you.
Thank
you.
Thank
you.
Can't
wait
so
Monday
we'll
have
our
final
release
team
meeting,
hopefully
and
then
Thursday
the
following
Thursday
next
week.
A
The
second
45
minutes
of
the
the
community
meeting
will
be
the
retrospective
for
the
release.
So
please
make
sure
that
the
really
retro
doc
has
anything
you
want
to
add
in
there
and
we'll
discuss
it
and
linked
and
identify
how
Josh
burkas
can
make
111
even
more
awesome.
So,
alright,
everybody
thank
you.