►
From YouTube: Kubernetes 1.12 Release Team Meeting 20180806
Description
A
B
All
right,
we're
to
past
I
am
going
to
go
ahead
and
start
things
up.
Just
a
reminder.
I
have
been
remiss
to
mention
this
at
the
beginning
of
previous
meetings,
but
this
meeting
is
recorded
and
we
do
post
it
to
YouTube,
so
the
broader
communities
community
can
see
and
understand
what
we're
doing
so.
Just
keep
that
in
mind
that
don't
expect
to
have
any
issues
on
this
call,
given
the
the
set
of
people
who
attend,
but
just
to
make
it
explicit.
B
These
are
public
meetings
so
kind
of
the
the
typical
standing
agenda
for
where
we
are
right
now,
just
gonna
go
over
features
a
bit
bugs
and
CI
signals.
So
our
features
lead
is
indicated
earlier
this
morning
that
he
is
unable
to
attend,
but
had
sent
a
note
in
the
slack
channel
and
sig
release
mentioning
that
there
are
as
many
as
66
features.
Now
we
had
three
that
are
going
to
be
exceptions
that
came
through
last
week,
which
is
not
completely
unexpected.
B
The
there's
always
a
few
things
that
trickle
in
so
there's
some
some
work
there
to
go
through
and
scan
things
and
and
potentially
one
also
that
was
additionally,
something
that
might
be
at
at
risk.
So
we
need
to
tighten
that
up
a
little
bit
this
week
and
I'm,
hoping
then
at
next
week's
meeting
that
we
have
maybe
Stevan
able
to
give
a
little
bit
of
an
overview
of
that
list,
and
summarize
it
a
bit
for
us
so
do
any
of
the
features
lead
shadows
have
anything
that
they
would
like
to
mention.
There.
B
Lots
of
pinging
and
poking
so,
okay,
then
the
next
thing
that
I
want
to
talk
about
and
I
just
know
that
Caitlin
joined
usually
around
this
point.
B
C
D
C
So
we
basically
putting
out
all
of
those
features
that
essentially
became
what
the
media
was
using
for
the
articles
and
stuff
that
they
put
out
alongside
the
release
that
then
not
all
of
those
features
made
it
into
the
actual
release
itself.
So
we
actually
found
that
we
were
kind
of
having
to
backtrack
and
correct
some
of
this
messaging
with
the
updated
features.
So
it
ended
up
causing
more
work
for
us
I
think
then
it
ended
up
being
worth.
C
D
E
One
thing
that
we
talked
about
in
the
past
is
our
sort
of
unofficial.
One
I
mean
the
problem
with
the
previous
one
was
that
it
was
quote
official,
so
we
had
talked
about
doing
this
sort
of
unofficial
one
so
that
it
kind
of
gives
the
community
a
little
bit
of
air
cover.
Should
things
not
land
and
that's
something
that
I
was
actually
thinking
about
writing
anyway.
So
if
we
can
figure
out
where
to
where
we
might
want
to
publish
it
within
the
community,
we
can
certainly
do
that.
E
C
E
E
B
Wrong
with
you
just
putting
a
link
to
that
on
gate
of
at
a
minimum
and
I
think
Josh
burkas
is
likely
to
pick
it
up
for
his
last
week
in
kubernetes
and
I
would
probably
echo
it
and
my
semi-weekly
update
on
the
release.
Even
if
it's
not
on
the
official
Kate's
blog,
then
it
just.
It
gives
a
little
bit
of
visibility
in
a
lightweight
way.
I
think
this
is
I,
get
the
sensitivity
and
how
the
the
media
may
latch
on
to
things.
B
Thinking
like
this
is,
this
is
what's
coming,
but
part
of
this
I
feel
like
is
for
the
community
to
give
them
a
sense
of
themes
and
not
everybody's
gonna
go
look
at
the
feature
spreadsheet,
but
if
somebody
happens
to
read
a
blog
post
and
say,
oh
wait
that
feature
kind
of
overlaps
with
something
I'm
working
on
I
should
go
talk
to
these
other
developers.
That
cross
communication
is
actually
important
in
the
developer
community
yeah.
E
C
B
G
Yeah,
okay,
so,
as
far
as
far
as
to
see
a
guessing
game
is
concerned,
I
would
say
so
does
master
blocking
is
mostly
stabilizing.
There
is
one
more
open
one.
More
failure
bring
that
the
Dare
are
of
few
failures
on
master
upgrade
the
the
puberty,
an
issue
that
was
there
it.
It
is
finally
gone
three,
so
that's
good
than
or
equal
to
the
so
myself.
G
G
B
H
F
D
D
D
A
D
D
I'd
love,
to
know
how
this
compares
to
where
we
were
at
this
time
last
release
cycle
and
I,
don't
actually
know
how
to
how
for
how
we
can
better
keep
track
of
our
stuff
in
order
to
quickly
make
these
sorts
of
assessments.
I
often
hear
questions
in
the
form
of
at
this
point
in
the
release.
Does
any
remember
anybody
remember
like
how
many
open
issues
we
had
or
how
many
bugs
we
had
or
whatever
and
like
that's,
not
something
you
can
actually
quickly
craft.
A
github
issue
query
to
find
out.
B
The
way
I've
been
trying
to
get
a
sense
of
that
historical
stuff
is
going
and
looking
at
places
where
we
had
recorded
those
point
in
time
so
like
in
the
in
the
1.11
release,
meeting
google,
docs
notes
and
those
sorts
of
things,
because
usually
we
end
up
with
a
little
bit
of
something
there
so
like
looking
back
April
23rd,
there
were
45,
so
that
would
have
been
around
under
still
check.
B
I
think
that
was
a
round
feature
freeze,
but
I
feel,
like
the
the
number
anecdotally
feels
higher
to
me,
but
it
also
feels
like
we
had
more,
that
just
sort
of
kind
of
carried
over
like
we're
sort
of
kind
of
in
this
range
of
twenty
to
thirty.
They
carry
over
from
release
to
the
release
and
then
either
a
subset
of
those
get
created
or
get
get
done
or
carry
on
to
the
next
one.
So
there's
this
sort
of
this
chunk,
that's
sort
of
just
on
the
front
edge
of
that
wave.
That
just
keeps
totally.
D
Paradoxically,
even
though,
like
July
seems
to
be
the
month
of
summer
vacation
for
everybody
at
least
that
I
seem
to
interact
with
like
it's
actually,
q3
has
been
the
most
productive
quarter
for
the
past
two
years,
three
years
according
to
dem
stats,
so
that
actually,
like,
maybe
it
being
higher,
seems,
okay
still
seems
wild
to
me
that,
like
so
much
higher
than
what
we
actually
released
last
time
but
I'm
curious
to
see
what
we
actually
release.
Yeah.
B
That's
the
big
question,
I
think
as
the
the
list
of
stuff
kind
of
ratcheted
up
in
the
last
two
weeks,
I
started,
causing
me
a
little
bit
of
worry
like
is
this
gonna
be
a
super
active
release,
but
then
also
so
much
of
it
felt
like
it
was
the
kind
of
carry
forward
stuff
I'm
a
little
skeptical
at
this
point.
How
much
of
that
list
of
now
66
things
is
gonna,
actually
get
done
right.
D
B
D
Well,
we
did.
It
happened
on
Friday,
so
I
don't
know
if
it
actually
hits
if
it
happened
in
time
they
get
Friday
morning's
notifications,
but
I
was
tempted
to
not
tell
you
and
just
see
what
happens
in
some
sort
of
experiment,
but
now
I've
told
you
so
I've
ruined
that,
and
if
anybody
you
know
I'm
looking,
especially
in
the
direction
of
CI
signal
and
issue
gosh,
if
you're
finding
life
is
more
complicated.
Let's
chat.
D
That's
part
of
the
reason
I
keep
showing
up
to
this
meeting
and
also
just
to
close
the
loop,
since
this
was
a
decision
that
was
made
during
the
sacral
East
meeting,
which
happens
separately
from
the
release
team
meeting,
but
it
seemed
like
it
had
a
lot
of
impact
to
this
release
team.
So
anyway,
any
questions,
let's
chat
about
it
on
cig
release
and.
B
B
Well,
this
has
been
a
relatively
quick
meeting,
I
kind
of
makes
sense,
I
guess,
given
that
we're
almost
smack
dab
in
the
middle
of
the
release
cycle.
Looking
up
at
my
calendar,
we,
we
have
basically
four
weeks
now
until
code
freeze,
and
this
will
be
a
period
where
we
are
kind
of
collectively
looking
at
those
features
going
by
in
terms
of
implementation,
pr's,
bug
issues
and
zi
signal
and
starting
to
formulate
more
concretely,
our
sense
of
risk
and
complexity
in
the
release.
B
Do
we
have
sixty-six
features
that
are
large
and
actively
under
development
and
major
test
destabilization,
or
do
a
good
chunk
of
those
fall
away
and
it
becomes
simpler.
So
I
guess
my
my
main
thing
that
I
would
say
going
forward
for
the
next
couple
of
weeks
is
to
really
try
and
keep
a
proactive
eye
on
these
things
and
get
an
early
warning.
I
See
anything
at
present
we're
still
tracking
everything
in
the
air
table
as
far
as
what's
going
on,
we
have
a
few
weeks,
I.
Think
three,
if
I
remember
correctly,
until
Docs
PRS
need
to
be
at
least
open,
so
right
now
I'm
just
managing
the
branch
in
the
website,
repo
keeping
it
up
with
master
because
we're
doing
a
lot
of
refactoring
with
the
Hugo
migration
and
internationalization
that's
going
on
in
preparation
for
a
coupon,
China
and
obviously
Goodman.
It's
a
global
effort
now.
I
So
so
that's
mostly
what's
going
on
as
we're
just
kind
of
keeping
things
over
there
and
keeping
our
eye
on
inbound
pull
requests
that
aren't
associated
with
features,
but
it
could
probably
use
documentation.
I,
welcome,
anyone's
feedback,
I'll
pop
the
link
in
the
chat
again
on
what
you
think
could
be
improved
about
it.
I
know
we
talked
about
potentially
using
this
for
more
than
just
documentation,
but
even
if
you
notice
here,
you're
like
hey,
this
actually
does
not
need
Docs
or
does
need
arts
than
that.
That
would
be
awesome.
B
All
right
anything
else
that
anybody
wants
to
bring
up
today-
oh
I,
guess
I
did
I
just
noticed,
Doug,
Mike
hacker
and
joined
I
didn't
mention,
because
this
happened
after
last
week's
meetings.
We
actually
cut
a
release
me.
He
alpha
one
release,
so
alpha
zero
gets
created,
sort
of
automatically
in
the
prior
cycle
due
to
reasons
but
Doug
was
able
to
cut
a
release.
We
had
some
a
few
issues
that
came
up.
B
The
the
documentation
in
the
process
are
both
evolving
quite
a
bit
right
now,
so
we
had
instead
of
the
maybe
sort
of
hour
to
two
hours
to
make
a
release.
We
we
were
dabbling
and
stumbling
our
way
through
it
for
about
two
days
and
out
popped
release
on
late
on
Wednesday,
if
I
recall,
correctly
and
I
think
based
on
that,
we
have
the
process
kind
of
better
documented
I
hope.
B
So
Caleb's
got
a
bunch
of
work
that
has
happened.
That
he's
helped
drive
behind
the
scenes
at
Google
to
update
the
process
there
and
the
some
of
the
other
Google
folks.
So
it
seems
like
it
actually
works.
We
were
able
dug,
as
somebody
new
and
non
completely
non
Google
was
able
to
make
a
release.
So
that's
a
really
positive
change
in
terms
of
bringing
stuff
a
little
more
out
from
behind
the
Google
wall
and
fully
into
the
community.
J
Yeah
I
think
it
went
pretty
smooth
of
me
me
an
issue.
Funnily
enough
was
the
email,
so
I
don't
know
about
anyone
else
here,
but
I
haven't
used
a
local
MTA
to
send
mail
for
years,
I'm
going
to
try
to
do
it
manually
and
then
even
think
about
a
copy
and
paste
of
the
generated,
HTML
and,
of
course,
came
through,
as
is
the
first
time
so
I
hopped
up
my
email
game
for
next
time.
D
I
had
one
more
tiny,
tiny
thing
since
I
think
this
was
also
discussed
at
the
last
sake.
Release
meeting,
but
not
here,
I,
want
to
add
a
quick
milestone
to
this
release.
Schedule
where
the
testing
for
a
role
formerly
deprecates
and
removes
all
of
the
release
branches
for
oh
good
grief,
I
should
have
the
number
locked
and
loaded
here,
I
want
to
say:
1/8,
yes,
I,
believe
technically,
1/8
is
more
than
three
releases
back
right
now,
and
so
we
don't
really
need
to
have
ongoing
CI
support
for
it.
D
You're
still
capable
of
cutting
a
release
off
the
branch
for
security
purposes,
but
we're
gonna
shift
everything
forward
and
lockstep
and
I'm
proposing
to
make
this
just
a
part
of
the
standard
release,
schedule
and
set
of
responsibilities
for
testing
first
and
look
for
a
PR
to
the
schedule
later.
I.
Don't
think
anybody
here
really
cares,
but
just
ahead.
I.
B
Think
it
died,
I
would
say
I
care
because
I
really
like
that
that
it's
not
just
let's
turn
this
off,
but
let's
put
it
in
the
schedule,
because
we
copy-paste
sort
of
the
schedule
each
time
forward
that
that
becomes
a
regular
reminder
to
the
release,
lead
and
test
them.
For
folks
to
that,
this
is
something
we
do
explicitly
at
a
certain
time
and
then
for
the
rest
of
the
community
or
downstream
derivatives,
the
distros
and
vendors.
To
know
that
that's
the
point
at
which
it
goes
away.
B
Alright,
anybody
anything
else
shall
we
call
it
a
day
and
oh
I'll
mention
that
I,
so
we
will
be
having
the
meeting
tomorrow
morning
early
Pacific
time,
which
is
a
little
bit
earlier
for
European
folks
and
a
better
time
for
China.
So
far,
that
seems
to
have
been
working,
we've
been
having
constructive
conversation
and
pulling
in
a
slightly
disjoint
set
of
people
more
of
the
the
shadows
as
well.