►
From YouTube: Kubernetes 1.10 release burndown meeting
Description
A
All
right
everybody
welcome,
it
is
Monday
February
26
2018
today
is
the
first
day
of
code
freeze
for
the
110
release
cycle.
So
this
is
a
pretty
epic
part
of
the
process
here,
where
we're
starting
to
focus
on
release,
fidelity
and
get
a
good
understanding
about
what
the
release
branch
holds
and
so
at
6
p.m.
today,
Pacific
time
we
will
be
turning
on
the
switches
in
the
but
there's
actually
a
switch
in
the
Majer
that
sets
to
code
freeze.
A
So
we'll
do
that
probably
need
some
help
from
some
Googlers
to
make
that
happen,
because
the
Majer
has
to
be
I
believe
the
mantra
has
to
be
restarted,
so
yeah
so
I
will
be
getting
smoke,
looks
like
from
Kohl's.
So
that's
me.
Thank
you.
So
much
cold
really
appreciate
it.
So
yeah
today's
a
great
day,
let's
go
ahead
and
get
right
into
the
meeting
minutes
if
you're
watching
this
video
after
the
fact
and
when
I
follow
along
with
the
actual
minutes
that
we
take
they're
available
at
bit,
Dali
slash,
kits
110,
burned
down.
A
B
So
tide
is
a
little
different
than
Monte
github
tide
is
just
for
the
emerg
automation,
where
github
the
only
thing
that
we're
really
using
for
well
I
guess
for
the
the
milestone
stuff.
There's
a
milestone,
Lunger,
that's
specific
to
that,
and
then
we're
also
using
this
to
make.
You
still
will
switch
over
to
tide
in
the
next
couple
months.
Hopefully,
but
the
milestone
stuff
may
still
be
done
by
munchkin
hope
for
the
next
few
months,
at
least.
A
Great
things
so
another
another
thing
that
we're
gonna
be
looking
at
is
stuff
in
the
release:
branch
that
is
missing
tests
or
things
that
might
in
worst
case
need
to
be
reverted.
I
will
reiterate
that
that
is
a
last-ditch
option
that
we
do
not
want
to
be
reverting
things
in
the
release
branch,
unless
it's
absolutely
100%
necessary,
much
preferred
to
shore
up
things
tests,
whatever
we
need
to
do
to
make
that
work,
so
we'll
be
keeping
a
close
eye
on
that.
A
Mr.
miles,
we'll
be
cutting
a
beta
this
week,
I
believe
and
if
he
says
otherwise,
then
we'll
go
with
that.
But
as
far
as
I
know,
we'll
be
cutting
a
beta
and
docks
PR
deadline
is,
is
this
week,
so
this
is
where
basically,
we
want
to
have
PR
Zen
for
most
the
the
docks,
but
they
they
may
have
some
missing
pieces
or
or
they
may
not
be
fully
ready
for
public
consumption.
A
But
the
idea
is
simply
that
we
want
to
capture
the
major
pieces
of
functionality
there
and
major
themes
and
also
whoever
is
putting
in
the
PR,
for
the
docks
is
going
to
be
the
main
contact.
So
that
will
be
the
person
that
Nick
and
others
haunt
as
the
docks
do
or
do
not
meet
the
various
deadlines,
just
as
a
reiterate
er
to
anybody
working
on
docks
and
collection
of
that
stuff.
A
I,
am
your
servant
put
me
to
use
if
you
need
me
to
go
to
meetings,
to
talk
to
people
to
hit
people
up
on
slack
I
did
this
and
1-8
I
did
a
lot
of
of
talking
to
people
about
documents
and
I'm
happy
to
do
it
again,
if
need
be.
So
nobody
in
this
release
team
should
suffer
in
silence
if
your
job
is
becoming
onerous
and
you
cannot
manage
all
the
things
you
need
to
do
for
it.
A
Please
pull
me
into
it
or
pull
somebody
else
from
the
release
team
to
help
you
out,
because
the
heroics
are
not
encouraged.
Heroics
are
not
cool
the
we
need
people
to
make
this
sustainable,
because
this
is
a
marathon
and
it's
basically
a
release
after
release.
We
need
to
find
ways
in
places
to
make
it
better.
So
that's
my
public
service
announcement
about
no
heroism
so
moving
along
next
week.
We're
going
to
be
looking
at
another
beta
and
that's
ducks
should
be
pretty
well
in
the
homestretch
next
week.
Just
to
put
things
in
perspective.
A
As
far
as
the
release
timeline
goes,
we
are
in
week
9
right
now,
and
there's
only
really
three
weeks
left.
So
this
is.
This
is
really
the
end
into
the
the
race
here
that
we're
pushing
for
so
that's
pretty
much
it
for
the
timeline
I
put
yellow
for
the
timeline,
because
I
feel
like
there's
a
classic
amount
of
unknowns
still
lingering
on
the
periphery
that
hopefully,
Josh
and
others
will
be
able
to
sort
out.
A
A
C
C
A
My
my
memory
does
not
serve
me
quickly.
I
guess
I
was
traumatized
from
1.8,
so
it
seemed
seemed
less
less
than
at
that
point.
So,
okay!
Well,
that's
good.
I
am
noting
that
it
does,
and
this
is
something
we've
talked
about
is
it
seems
like
there's
a
lot
less
activity
in
the
milestone
this
time
around
by
a
lot.
Yes,.
D
A
It's
interesting
so
thanks
to
Josh's
cheery
assessment,
I'm
saying
that
crepe
we're
not
looking
so
bad
right
now,
which
is
fantastic,
but
we
will
need
to
focus
on
getting
those
PRS
attended
to.
But
if
the
folks
who
are
responsible
so
Oh
Josh,
you
and
I
will
talk
about
that
and
all
I'll
gladly
help
and
talk
to
those
folks.
So
we.
C
C
E
I'm,
looking
through
the
master
blocking
dashboard
every
day
and
trying
to
like
mark
the
red
test
as
an
issue
and
keep
checking
with
them.
A
Great,
thank
you
so
much
for
doing
this,
and
and
and
also
keeping
those
issues
up-to-date,
alright,
so
moving
along
so
Josh.
Do
you
want
to
go
ahead
and
run
through
your
stuff?
I
mean
we'd
sort
of
you've
broken
this
down
the
bug.
Leaderboard
that
you
keep
it.
It
didn't
look
last
time,
I
check
to
be
updated
for
today.
So
if
you
want
to
just
give
a
quick
rundown
on
that,
that'd
be
helpful.
Yeah.
C
C
After
this
meeting,
basically
we're
actually
down
a
little
bit
on
issues
than
we
were
last
week,
so
new
issues
been
open,
but
more
issues
have
been
closed
or
taken
out
of
the
milestone.
The
so
stuffs
getting
closed
as
you'd
expect
from
the
stage
of
the
release.
The
new
issues
are
basically
bugs
the
sort
of
newly
declared
bugs
the
when
I
have
the
leaderboard
you'll
have
more
of
an
idea
of
a
sig
breakdown.
C
C
A
Great,
thank
you
so
much,
maybe
just
post
in
the
slack
channel.
When
you've
got
the
leader
board,
we
can
take
a
look.
Let's
go
ahead
and
run
through.
You
know,
there's
a
couple
interesting
things
this
time
around
I've
noticed
that
one
is
that
we
haven't
had
any
exception.
Requests
yet
and
I'm.
Anticipating
will
have
some
exception,
requests
to
go
into
the
release
branch,
but
interesting
that
there
is
seems
to
be
feature
volume.
Just
generally
speaking,
is
much
slower
and
less
aggressive
in
this
release.
A
So
it's
going
to
be
interesting
to
see
how
that
shakes
out
in
terms
of
release
branch
health.
A
E
Sure
you
see
so
most
it's
a
lot
of
noise
from
the
past,
because
optim-r
failing
the
reaching
API
server,
there's
they
opened
by
Magna
nice,
so
hopefully
that
will
at
least
make
it
past
API
access,
accessibility,
check
and
get
give
us
better
signals.
E
E
We
might
need
to
take
a
look
at
this
and
because
me,
after
the
code
freeze,
we
will
like
need
signal
from
the
pre
jobs.
F
A
A
B
A
A
A
A
D
For
marketing
there's
three
main
things
on
our
list
that
I'm
hoping
to
wrap
up
or
get
into
a
solid
review
by
Friday.
The
first
is
the
blog
announcement,
of
course,
so
this
is
already
pre
drafted
and
now
Jase
we're
just
looking
to
you
and
you
are
and
to
really
go
through
and
just
make
sure
that
the
features
that
we've
highlighted
now
that
we're
in
freeze
are
correct
and
that.
D
Is
communicated
correctly
and
the
way
that
we
want
to
to
talk
about
the
trollese,
and
then
you
know,
hopefully
to
finalize
that
offense
the
following
week.
The
second
one
is
I
just
wanted.
We
just
want
to
solidify
the
five
blogs
for
the
five
blog
series
that
will
be
going
out
after
the
release.
We've
made
some
suggestions
but
I'm
trying
to
make
sure
that
everyone's
an
agreement
of
that
then
the
last
one
is
just
kind
of
a
small
Q,
a
sound
byte
document.
D
D
A
Cool,
thank
you
so
much
Natasha.
This
is
really
great
I.
You
know
the
seen
the
evolution
of
marketing
being
an
integrated
part
of
the
release
team
is
really
exciting.
This
is
truly
so
much
better
and
you've
you've
been
extremely
diligent
about
keeping
the
the
schedule
tight
and
and
getting
these
things
and
meeting
your
deadlines.
It's
very,
very
appreciated.
Thank
you.
So
much
great.
C
G
I
can't
talk
to
the
docs
in
general,
but
I
can
talk
to
the
release
notes,
so
no
I
managed
to
get
the
auto-generated
version
working,
which
is
awesome
so
now
we
can
do
it
ourselves
instead
of
having
a
bunt
of
Anthony
all
the
time.
The
other
thing
is,
we
already
have
the
base
the
base
of
what's
new
in
the
preview
blog,
which
we're
going
back
and
forth
on
where
that's
going
to
go,
probably
being
the
kubernetes
flog,
so
we
have
the
the
basics.
The
other
thing
is
in
that
process.
G
By
the
way
we
discovered
a
few
things
that
are
on
the
release,
spreadsheet,
that
we're
marked,
as
you
know,
with
particular
statuses
that
it
turns
out,
are
not
actually
accurate,
so
might
be
a
good
thing
to
kind
of
confirm
that
release
spreadsheet
as
well
so
yeah.
So
that's
that's
where
we
are
so
probably
Pinnock,
yeah.
H
H
D
H
G
A
G
Oh,
no,
absolutely
you
know
the
the
first
kind
of
release
notes
will
let
everybody
know
about
that.
Contesta,
yes
and
I'll.
Send
you
the
and
I'll
tell
you
what
I'm,
just
gonna
post
here,
the
give
me
a
minute
to
pull
it
up
and
I'll
post
the
link
to
the
Google
Doc
or
the
this
is
a
preview
blog.
This
is
not
the
official
release.
Blog
keep
in
mind.
Yes,
that's
a
separate
animal.
Okay!
A
I'll
I'll
link
it
in
the
the
meeting
notes
and
so
we've
got
it
all
right.
Thank
you.
So
much
again,
your
work
here
is
tremendously
appreciated
and
I
know
there's
a
lot
to
it.
So.
A
Absolutely
all
right
so
announcements,
one
is
that
we
are
commencing
with
Monday
through
our
Monday
Wednesday
Friday
meetings
this
week,
because
I
want
to
be
really
careful
of
everybody's
time.
I
may
cancel
these
depending
on.
If
we
really
need
them
or
not,
I
just
want
to
have
them
available.
If,
if
we
need
them
so
I
think
there's
a
very
high
likelihood
that
Wednesday's
meeting
will
be
canceled.