►
From YouTube: Kubernetes 1.10 release burndown meeting 20180228
Description
A
All
right
everybody
welcome.
It
is
Wednesday
February,
28
2018.
This
is
the
three
nineties
1.10
release
burndown
meeting
and
you're
in
the
Monday
Wednesday
Friday
iterations
of
the
meetings
so
means
we're
approaching
the
end
of
the
release
cycle,
but
not
quite
in
full
swing.
Yet
code
freeze
happened
yesterday
and
today
we're
just
gonna
quickly,
run
through
where
rat
and
raise
any
issues,
risks,
etc.
That
we
have
observed
thus
far
quick
note.
A
So,
yes,
code,
freeze,
happened
and
I
haven't
looked
at
this
submit
queue
recently,
I'm
sure
somebody
can
chime
in
there,
but
I
think
that
things
are
moving
forward.
I
went
through
last
night
and
I
adjusted
the
proof
for
milestone
label
and
milestone
marker
for
52,
pull,
requests
and
adjusted
a
couple
more
today
that
were
approved
and
whatnot.
Yesterday,
generally
speaking,
when
those
come
in
and
are
looking
for,
approval
I
have
go
to
the
six
first
and
there
are
a
couple
of
exceptions
that
have
come
through
as
well.
A
That
I've
kicked
back
to
the
six
to
make
sure
that
they're,
okay,
with
moving
out
that
work
forward.
So
again,
six
are
the
are
the
power
keepers
here?
Not
not
anybody
in
the
release
team,
so,
let's
see
so
that
there's
a
note
in
here
in
the
timeline
and
if
you're
looking
at
this.
After
the
fact,
it's
bit
dot,
ly
/
Kate's
110
burned
down
as
the
is
the
link
for
the
agenda,
the
pruning
aspect
is
not
something
we
need
to
worry
about
right
now.
Things
seem
like
they're
on
track
and
document
it.
B
B
A
Does
he
talk
about
user-facing
docks?
First,
do
you
want
to
hit
that
any
updates
there
isn't
or
anybody?
Actually
you
didn't
give
us
that
update
and
it
could
be
heard
anything
there.
A
C
A
Know
it
might
be
more
efficient
for
you
to
do
that
and
have
that
conversation
than
for
me,
but
I'm
happy
to
do
it.
If
it's
not
something
you
have
time
to
do.
No
I
can
do
that.
That's
fine!
Okay,
no
problem
great
thanks!
So
much
yep,
alright,
so
timeline
for
next
week,
I
really
darks
beta
marketing
stuff
is
getting
into
full
swing.
A
We
had
a
good
update
from
Tasha
on
Monday
and
also
wanted
to
call
out.
You
know.
I
mentioned
Natasha's
done
a
lot
of
work
here,
but
also
I
want
to
mention.
Katelyn
who's
done
a
ton
of
work
as
well,
so
we
are
truly
blessed
with
some
amazing
marketing
talent
and
this
release,
so
I
think
there's
a
probably
good
chance
that
Katelyn
will
step
up
as
the
marketing
lead
for
well
111
or
possibly
112.
So
that's
exciting,
I
love
getting
people
to
to
step
into
the
leadership
roles
and
signora
bug
Squasher.
Mr.
B
The
other
than
having
the
extra
24
hours
actually
really
helped
a
lot
of
the
issues
in
PRS
that
were
in
kind
of
an
indefinite
State
on
Monday
actually
got
resolved
Tuesday
morning,
and
so
we're
not
still
dealing
with
us
I,
don't
know
whether
or
not
we're
dealing
with
new
ones
yet
that
later
today,
other
than
that,
you
know,
as
I
mentioned
before,
we
have
fewer
open
issues
and
we've
had
for
past
releases.
B
The
a
lot
of
that
is
because
a
lot
of
stuff
that
was
originally
on
the
features
list
for
1.10
looks
to
be
deferred
to
1.11.
So
it's
not
necessarily
a
good
reason
to
have
few
issues
the
and
since
this
week
we
have
a
bunch
of
failing
test
issues.
As
you
know,
frankly,
we
should,
at
the
stage
so
again,
I'll
have
a
comprehensive
list
of
those.
Later
today,.
D
D
D
It
was
failing
on
a
here,
it's
dirt
past,
but
seems
absurd
home.
Add
a
fix
now.
It
starts
fading
on
l7
load,
balancing
for
folks
to
take
another
look
and
the
Stewart
has
this.
Both
the
serial
and
reading
tests
are
failing
on
demon,
sad
stuff
and
the
gaps
has
a
open
PR,
and
we
will
see
how
fast
will
behave
when,
after
that
car
is
merged.
D
I
also
find
recently
the
stability
suite
is
kind
of
flaky
and
do
we
want
feel?
How
do
we
generally?
You
know
it's
like
flaky
issues,
so
I
open
and
like
they
like
testing
flaky.
You
and
thank
you.
A
A
So,
if
that
that's
what
it
takes,
and
you
don't
get
traction
just
tell
me
who
to
go
talk
to
or
whatever
need
to
do
there.
Okay,
but
I
mean
that
they,
the
thing
just
this
is
more
of
a
philosophical
thing,
but
with
flakes
have
a
little
I'm,
not
as
concerned
where,
where
we
experience
non-deterministic
errors,
that
could
potentially
pointed
a
real
issue,
that's
where
I
will
rapidly
escalate.
So
just
keep
that
in
mind
this.
A
So
if
you
do
run
into
something
that
looks
like
it
could
be
a
true
destabilization
of
the
the
branch
in
some
way.
Those
are
the
ones
who
you
know
immediately.
Pull
the
fire
alarm
talk
to
me
and
we'll
and
we'll
get
it
prioritize.
The
flakes
are
just
more
of
an
annoyance
than
anything
at
this
point,
but
they
will
become
less
less
cool
as
the
release
marches
on.
B
E
B
B
B
F
A
A
D
A
F
A
E
A
We
certainly
can
I
feel
like
the
so
generally
speaking,
if,
if
the
sig
leaders
weigh
in
and
give
a
plus-one
and
the
email
thread,
that's
that's
ostensibly
an
approval
in
that
save
some
time
in
the
meetings.
But
if,
if
we
get
an
area
where
there's
something
contentious,
what
I
really
want
to
do
is
have
the
discussions
here
about
risk
to
the
to
the
release
and
those
are
the
ones
where
I
want
to
try
and
raise
those
up
and
and
have
that
discussion
for
sure.
Okay,.
E
A
A
Okay,
well
good
and
our
email
chain
is
working.
That's
that's
actually
really
positive!
Yeah,
it's
nice,
not
having
a
massive
list.
Okay,
cool
well
I'll,
make
sure
that
that
gets
updated
in
the
in
the
meeting
notes
as
a
formalized
approval
and
thank
you
Jordan
for
for
keeping
us
honest
there
and
getting
that
documented
yep.