►
From YouTube: Kubernetes 1.10 Release Burndown Meeting 20180322
Description
A
Welcome
everybody
to
the
kubernetes
1.10
released
burndown
meeting.
It
is
Thursday
March,
22nd,
2018,
I'm,
Jason,
Mars
your
host
and
release
team
leader
and
we're
going
to
kick
off
the
meeting
if
you're
viewing
this.
After
the
fact,
I
want
to
see
the
release
or
the
the
meeting
notes
on
the
agenda.
It's
available
at
bitly,
slash,
Kate's,
110,
burned
down
I'm
going
to
share
my
screen
here
and
with
any
luck,
it'll
work
and.
A
Alright
is
that
look
like
it's
shared
properly?
Don't
seem
good,
okay,
alright!
So,
let's
run
through
the
timeline,
so
I
I'm
gonna
actually
push
the
confidence
check
to
the
end
until
we
discuss
things
but
for
now
I
wanted
to
talk
about
some
of
the
things
in
flight.
So
there's
one
this
pier
here
that
I
just
was
discussing
the
release.
Channel
I
was
hoping.
Maybe
somebody
had
some
context
on
this.
A
Don't
know
where
this
came
from,
so
it's
for
one,
it's
a
terrific
candidate,
but
it's
actually
in
its
governing
to
the
110th
branch,
which
is
not
correct.
So
at
the
very
least,
these
people
are
gonna,
need
to
put
this
into
master
and
then
cherry-pick
back
into
110.
Unless
there's
something
about
this
having
to
be
some
branch
specific
commit
which
I
am
highly
opposed
to
just
on
the
merit
of
it,
so
I
guess,
I'll
figure
out
more
information,
I
send
a
private
message
to
Martian
about
this,
and
hopefully
I
can
get
some
more
clarification.
A
C
D
B
A
B
B
A
A
F
E
A
Okay,
so
just
to
put
a
bow
on
this
and
to
put
it
in
the
notes
about
what's
gonna
happen
here.
Let
me
first
copy
these
two
things
here,
so
you
can
put
these
in
notes
to
do
them.
So
those
two
no
no
paste
only.
A
F
Can
I
ask
Michelle
just
a
really
quick
question
right
now,
I
mean
it
sounds
like
this
is
really
an
edge
case
if
you've
got
any
thoughts
about
whether
we
need
something
in
the
core
Docs
or
whether
known
issues
in
the
/rel
notes.
That
would
be
helpful.
You
can
ping
me
in
slack.
We
don't
need
to
take
up
any
more
time
in
this
meeting
about.
It
sounds
good.
A
Alright,
so
moving
on
to
the
scale
regression
that
we've
been
chasing
down,
I
don't
know
if
jumps
on
this
call
or
not
that's
I'm,
gonna,
again
curse
the
fact
that
when
you're
presenting
it
makes
everything
harder,
it
does
not
look
like
it,
but
last
last
I
heard
on
this,
and
anybody
can
pipe
up.
They
have
more
info.
But
essentially
that
looks
like
the
the
it's
been
found
and
identified
and
there's
a
fix.
It
needs
to
be
in
place.
B
B
B
A
F
A
I
like
having
physical
access
to
our
people,
so
he
can.
You
know,
of
course
them
in
person.
That's
that's
good!
Okay,
so
is
there
anything
else
in
here
that
looks
particularly
problematic.
Do
we
need
to
chase
down.
B
The
large
clusters
refusing
to
come
up
that
was
unfortunate,
that
was
Shyam
and
so
for
the
fix
got
merged.
I
have
no
idea
what
the
results
were,
the
so
and
then
the
others
are
sort
of
unverified
things.
I
just
got
word
from
scheduling
on
the
Tex
preemption
one,
and
they
say
that
is
not
a
blocker
and
that
I
haven't
had
a
chance
to
investigate
the
other
two
with
their
respective
six.
Yet,
okay.
A
B
B
G
A
Yeah
I
know
that
it's
just
yeah,
if
we,
if
we
there's
some
reasonable
reason,
why
it's
not
why
I
timing
out
I'm
fine
with
that,
but
if
it
indicates
that
there's
some
underlying
instability,
that's
causing
it
to
do
that,
then
I
want
to
definitely
want
to
investigate
but
agree.
So,
okay,
so
just
to
just
to
put
a
bow
on
this
Josh,
so
we're
gonna,
try
and
figure
out.
We've
got
something
in
flight
for
the
host
path.
B
B
A
A
Which
looks
like
a
yes
from
all
the
information
I
have
thus
far
we've
identified
the
problem.
So
if
we're
able
to
to
do
whatever
it
takes
to
get
those
PRS
in
place
to
fix
it,
then
the
question
is:
can
we
get
those
done
and
approved
and
enough
visibility
on
those
today
and
tomorrow,
in
order
to
make
the
release
on
Monday?
Well,
I
guess
we'll
have
Monday
to
technically
to
let
things
soak,
because
we
don't
usually
release
until
p.m.
yeah.
B
A
All
right,
okay,
so
before
you,
the
confidence
check.
I
want
to
announce
the
team
that
Josh
burkas
has
kindly
offered,
as
tribute
sacrificial
tribute
to
the
the
111
release
demon
as
lead
and
we're
still
going
to
be
taking
other
people
who
might
be
interested
in
and
if
there's
contention
around
it,
the
multiple
just
vote
or
to
have
some
discussion
around
it,
there's
also,
obviously
an
opening
for
whoever
is
going
to
be
the
shadow
for
that
release
to
help
Josh
out.
A
A
Ok,
so
last
thing
in
this
current
the
cycle
here
is:
let's
get
a
confidence
check
from
the
folks
in
the
virtual
room
here
I.
How
confident?
Let
me,
let
me
put
it
this
way.
Does
anybody
feel
like
there's
a
likelihood
that
we
are
not
going
to
hit
Monday
like
this
Monday
feel
completely
totally
out
of
question
to
anybody
either.
A
C
A
A
C
A
H
No
I
mean
I,
don't
think
it's
a
blocker,
you
know.
Ideally,
we
do
need
to
get
a
draft
to
two
media
to
start
writing
their
stories
and
I
do
need
to
let
some
of
our
some
of
the
companies
in
our
little
sphere
here
know
that
there
has
been
changes.
You
know,
for
example,
I
had
a
company
reached
out
to
Jason
I
yesterday,
who
thought
could
what
was
still
in
the
release
and
so
I
just
need
to
give
an
FYI,
so
people
for
planning
vlogs
on
Monday?
H
What
features
are
going
to
be
in
there
and
are
going
to
be
promoted?
So
you
know
I'm
fine,
having
reviews
and
changes
made
as
long
as
I
have
something
that
were
comfortable
with
just
letting
people
know
like
these
are
the
features
and-
and
this
is
what
you
should
write
your
stories
around.
This
is
what
you
should
do
your
blocks
around,
and
then
we
can
make
finalization
to
the
blog.
Even
as
early
as
Monday
morning
before
we
go.
A
A
D
E
A
A
A
H
A
C
A
A
H
And
then
in
turn,
open,
no
hypnosis
I
was
just
going
to
say
in
terms
of
the
media
for
their
stories
and
any
many
companies
that
are
putting
out
blog
post
on
Monday,
I,
normally
I
would
just
say
you
know,
go
ahead
and
and
that
I
would
just
give
them
the
time
of
like
5:00
p.m.
to
post
yeah
anything
5:00
p.m.
Pacific
time,
and
then
even
if
it
shifts
a
little
early.
A
A
C
A
H
H
H
A
H
A
A
A
A
G
F
F
F
Worst
case
scenario,
I
sit
down
with
Andrew
tomorrow
and
decipher
my
merge,
mysteries
I
think
I've
got
it
cleared
up,
but
this
is
just
me
being
still
kind
of
you
know
when
I
get
to
get
yeah,
so
yeah
I
think
we're
pretty
good
shape.
I
just
I
want
to
do
this.
This
one
I
want
to
do
in
this
meeting.
I
did
it
in
the
slack
Channel
yesterday,
because
you
referred
to
this
yesterday
in
this
meeting
Jase.
So
the
release
note
doc,
coordination
that
Nick
and
I
did
was
around
at
PVC
PV,
downgrade
issue.
F
That
is
now
out
of
the
docks
documented
only
in
release
notes
as
saying
okay,
if
you
want
to
downgrade
to
1.9,
go
to
1.9
got
six.
We
are
all
good
with
this
I'm,
just
speaking
or
forever
hold
your
peace,
because
I
sent
a
fair
amount
of
time
on
that
PR
yesterday
afternoon,
and
then
Jordan
comes
in
and
says:
no,
we
don't
need
it.
So
if
I
need
to
revive
it,
it
needs
to
happen
today.
F
A
F
A
A
F
F
A
A
H
A
Right
and
then
release
notes,
update
from
Nick
in
chat
was
here's
my
update
running
behind,
not
editing,
but
we'll
have
it
all
done
today
expect
markdown
version
tomorrow
morning.
Anybody
who
doesn't
respond
to
comments
by
then
will
have
to
live
with
our
interpretation
of
their
release
notes
we
will
run
TLDR
by
the
SIG's
in
slack,
so
there
we
go
and
I
will
paste
that
in
the
meeting
notes.
F
A
Fantastic
and
we're
also
the
earliest
we've
ever
identified
a
release
late
too
so
this
is.
These
are
good.
These
are
pieces
that
are
critical
to
success
that
are
starting
to
move
forward
in
the
process.
So
this
is
good.
Thank
you,
everybody.
Okay,
anybody
have
announcements.
Questions
concerns
that
they
want
to
run
through
before
you
adjourn.