►
From YouTube: Kubernetes 1.12 Release Team Meeting 20180807
Description
A
A
A
B
A
We've
got
Kenny
as
well:
okay,
well,
I'm
gonna,
go
ahead
and
get
started.
We'll
probably
have
a
relatively
short
meeting.
Today
we
had
a
short
meeting
yesterday
that
fits
with
where
we
are
in
the
cycle.
So
a
couple
of
updates.
Last
week
we
hit
feature
freeze
and
amazingly,
we
are
up
to
well
unless
it's
changed
again
today,
we
are
up
to
66
features
that
have
been
captured
by
the
feature
definition
process.
That's
a
big
number.
A
I'm
slightly
skeptical,
looking
at
some
of
them,
whether
all
of
them
are
gonna
get
through,
and
this
is
this
is
actually
normal.
We
get
a
big
chunk
of
things
that
come
in
and
some
of
them
fall
away
and
that
there's
kind
of
a
set
of
things
that
bounce
from
release
to
release
and
eventually
things
come
to
completion.
But
the
were
is
a
community.
We're
ambitious
I
think
that's
a
good
thing,
we're
trying
to
achieve
a
lot
and
we'll
we'll
see
which
of
these
come
to
fruition,
but
something
else
that
came
up
in
the
call.
A
Yesterday
we
had
Aaron
Creek
and
Berger
on
and
he
was
asking
if
we
looked
at
that
relative
to
prior
releases
and
I
had
a
gun
and
look
specifically
at
dev
stats,
but
anecdotally
felt
like
it
was
high,
but
something
that
he
called
out
was
looking
at
dev
stats
that
this
quarter
has
probably
been
historically
an
active
one.
So,
depending
on
where
we
are
in
the
calendar
year,
people
have
different
things
going
on
between
whether
it's
work
in
life
product
releases
at
work.
A
Things
like
that
or
holidays
conferences
stuff,
like
that
somehow
this
quarter
seems
to
be
one
where
people
are
actively
productive,
so
we'll
see,
we
may
actually
have
a
lot
that
happens
in
this
quarter.
Looking
at
that
list
of
features,
there's
a
number
that
look
slightly
worrying
to
me
just
in
terms
of
like
ok,
if
this
happens,
this
is
a
fairly
big
deal,
so
that
could
bring
some
risk
to
us
later
in
the
cycle,
but
again
we'll
kind
of
kind
of
see,
I'd
encourage
folks
even
beyond.
A
Obviously,
just
the
the
features
lead
in
shadows,
we're
looking
at
the
features
and
I
am
as
well
at
this
point,
but
I'd
encourage
other
folks
to
glance
over
that
spreadsheet
kind
of
look
at
at
least
the
names
of
the
features
and
SIG's
just
to
have
them
in
your
head
a
bit
if
and
when
things
come
up
later
in
the
cycle
and
if
you've
got
time
to
kind
of
glance
over
maybe
a
little
bit
more
of
the
feature.
Is
the
cycle
progresses?
One
of
the
things
that
will
really
happen
is
as
a
team.
A
The
way
we
manage
risk
is
kind
of
collectively
worrying
and
wondering
out
loud.
So
if,
if
there's
a
particular
feature
foo
and
for
whatever
reason
it
hasn't
come
up,
but
you've
noticed
something
about
foo
lately,
that's
exactly
what
we
want
you
to
bring
up
in
the
meeting
to
say:
hey
I'm
wondering
about
this:
we
haven't
talked
about
it,
but
I
saw
a
little
something
on
it
this
week.
A
Yesterday
we
talked
about
what
else
called
the
blog
post
in
Prior
releases
around
this
time
after
feature.
Freeze
the
communications
team
started
working
up
a
blog
post
to
describe
what
features
might
be
coming,
and
this
was
actually
a
Miss
on
my
part.
It
had
come
up
last
release
that
we
we
weren't
gonna,
do
this
going
forward,
but
it
didn't
get
removed
from
the
schedule.
A
So
we
sort
of
do
a
copy/paste
of
the
prior
schedule
and
we
don't
always
do
edits
of
the
old
schedule
live
as
we
remove
things
so
that
one
hadn't
gotten
explicitly
removed
I
carried
it
forward.
So
we're
not
gonna
do
that
formally.
But
then
there
was
some
discussion
about
whether
individuals
amongst
us
might
want
to
sort
of
informally
on
whatever
platforms
we
have
start
talking
about.
A
A
What's
actually
going
to
be
done
yet
so
then
the
communications
team
has
to
sort
of
backtrack
on
things
and
if
there's
press
out
there,
who
is
kind
of
incorrectly
latched
on
to
things
that
they
believe
are
conclusively
happening
and
and
kind
of
advertising,
those
or
messaging
those.
It
leads
to
confusion.
A
A
And
that
was
the
the
general
message
yesterday
that
are
not
gave
us
dick,
were
we've
got
a
pretty
small
issue
count
and
relatively
quiet
increase
singly
on
CI
signal
as
well,
compared
to
a
week
and
a
half
two
weeks
ago,
CI
signals
cleaned
up
quite
a
bit
on
master
blocking.
We
still
have
some
upgrade
tests
that
are
an
issue
just
glancing
at
our
attendance
suite.
We
don't
have
to
buy
coverage.
So
really
that's
that's
all.
There
is
to
say
probably
that
master
blocking
has
stabilized.
Yesterday.
A
A
B
A
A
Okay,
so
that
hits
the
main
three
areas
features
bugs
and
CI
and
a
bit
about
documentation,
communications
as
well.
There
were
a
couple
of
kind
of
miscellanea
that
came
up
yesterday
so
last
week
in
the
sick
release
meeting
we
had
a
discussion
about
turning
off
the
milestone
Munder
and
what
the
milestone
vendor
is.
A
So,
in
this
case,
1.12
and
at
the
same
time,
they
haven't
maybe
been
updated
recently
or
they
don't
have
certain
labels
and
the
the
frequency
or
the
specific
labels
kind
of
varies
or
varied
slightly
during
the
cycle
right
at
first,
you
could
just
say
we're
aiming
to
have
something
and
release
one,
not
twelve,
and-
and
maybe
that's
okay,
because
it's
early
in
the
cycle.
But
then,
as
we
progress
through
feature
freeze,
a
sig
should
have
looked
at
it.
A
It
should
be,
and
and
also
so
feature,
there's
kind
of
an
overlap
of
features
and
issues
here
and
potentially
PRS,
but
they're
they're
not
quite
treated
the
same.
So
we
get
this
ambiguity.
What
what
are
required
and
and
how
much
nagging
do
we
do
and
what
we
decided
in
the
sig
release
discussion,
and
this
had
been
discussed
on
and
off
in
previous
release.
Retrospectives.
A
It
gave
a
lot
better
results.
So
last
week
the
milestone
mantra
was
turned
off
on
Friday
and
it's
kind
of
funny
because
since
Aaron
had
attended,
the
meeting
I
was
gonna.
Ask
him
like
hey,
did
the
mouse
time
under
get
turned
off
and
I
hadn't
even
noticed,
because
I
don't
see
the
emails?
Probably
the
same
reason.
Nobody
else
sees
the
emails,
so
we're
all
curious
to
see
how
this
goes.
It's
a
risk
that
maybe
the
bot
was
actually
helping
something
and
we
have
issues
or
things
that
languished
right.
A
I
mean
we,
we
don't
know
for
sure,
so
I'd
encourage
folks
to
keep
an
eye
on
things
and
if
you
feel
like
somehow
we're
we're
that
you
get
this
sense,
somehow
that
we're
kind
of
losing
control
or
we're
not
noticing
things
that
we
keep
getting
surprises
speak
up,
share
that
that
worry
or
anxiety
and
and
we'll
revisit
this.
This
is
a
effectively
an
experiment
for
the
next
month
or
so,
and
especially
as
we
get
closer
to
the
release,
if
it
seems
like
somehow
we've
we're
realizing
with
hindsight
that
we
dropped
the
ball.
A
We'll
want
to
look
at
this
again,
and
it
may
be
that
automation
is
helpful
here,
but
we
need
to
change
the
way
we
do
automation.
So
we've
swung
from
really
aggressive
nagging
automation
to
none
so
we'll
re-evaluate
how
we
do
on
that.
The
other
thing
that
Aaron
mentioned
is
that
the
1.8
test
automation
has
been
turned
down
so
or
turned
off.
The
community
supports
three
prior
releases
and
part
of
that
is
having
test
automation
to
notice.
A
If
things
have
broken
there
and
one
not
eight,
has
passed
its
point
of
support,
and
this
has
happened
informally
in
the
past.
So
I
think
we
talked
about
this
last
week
that
we
needed
to
formalize
this
and
so
he's
put
out
a
PR
I'm,
not
sure
this
morning,
if
it's
merged
but
put
out
a
PR
to
update
the
schedule
to
have
a
formal
point
about
a
month
in
that's
turned
down
three
releases
agos
test
automation,
so
that
saves
the
project.
A
So
with
that
we
were
we.
Similarly
to
this
we're
15
minutes
past
we
had
a
pretty
quick
run-through
of
things
yesterday
and
then
we
had
kind
of
maybe
10
or
15
minutes
of
general
discussion
around
these
these
same
points,
but
so
I'll
I'll
open
it
up
to
y'all
anything
that
you'd
like
to
comment
on
any
questions.
Any
observations
for
the
week.
A
All
right,
so
the
other
thing
is:
do
we
keep
having
this
Tuesday
meeting
and
my
vote
would
be
yes
and
I'm
curious?
What
you
all
think
I
feel
like
we're
getting
two
sets
of
people
on
the
two
meetings
and
that
the
times
were
more
convenient
for
four
people
in
a
disjoint
way,
and
it's
fairly
easy
for
me
to
do
the
two.
And
what
do
you
all
think.
B
A
A
We
had
originally
kind
of
said
this
would
be
an
experiment.
We
do
it
for
a
couple
of
weeks,
so
this
was
the
last
meeting
on
the
calendar
formally,
but
I'm
gonna
go
ahead
and
extend
it
just
through
the
rest
of
the
the
112th
cycle,
I'm,
finding
it
useful
and
I
like
that,
we're
getting
more
activity
so
alright.
A
Well,
if
nobody
has
anything
else,
I
think
I'll
end
it
very
early
today,
I
would
say
our
our
next
couple
of
meetings
are
likely
to
be
modestly
short
as
well
before
things
really
start
to
ramp
up
in
September,
keep
an
eye
out
for
for
activity
on
github
and
issues
and
discussion,
and
things
and
familiarize
yourself
a
bit
with
the
features
and
we'll
we'll
see.
Where
are
they
all
head
over
the
next
month?