►
From YouTube: Kubernetes 1.12 Release Team Meeting 20180904
B
B
A
C
A
A
A
A
Yeah
I
I
went
ahead
and
let
my
slack
notifications
come
through
just
because
I
need
to
be
watching
this
stuff
right
now
and
I
were
surprised
by
that
it
was
was
also
the
message
was
I,
don't
know,
the
the
wording
was
interesting
between
the
lines,
just
sort
of
felt
a
little
cavalier
like
process
yeah,
so
we'll
see,
I
mean
this
I,
don't
even
know
the
scope
of
it.
How
how
big
or
small
it
may
or
may
not
be
so
we'll
see
yeah
it.
A
This
is
interesting
timing
because
today
is
the
day
that
we
will
start
code
freeze
and
feature
freeze
was
six
weeks
ago.
So
it's
always
interesting
to
see
like
try
to
try
to
over
communicate
things,
and
this
process
is
pretty
established
and
the
I
don't
know
you
can
only
do
so
much,
there's
always
gonna
be
mrs.
I,
guess
just
Clancy.
You
know
we
don't
have
any
tests
and
for
folks
so
and
I
think
most
of
the
meeting
today
is
not
overlapped
with
Friday.
So
on
Friday
we
discussed
the
coming
code.
Freeze
and
Cole
from
tests.
A
Infra
had
been
doing
some
experimentation
and
so
basically
we're
gonna
shift
over
to
using
tide
and
the
past
there's
been
a
variety
of
different
things
involved
with
enforcing
and
reminding
about
code,
slash
code
freeze
and
merge
requirements.
We
had
the
the
github
merger,
there's
the
submit
queue,
there's
tied
and
there's
potentially
a
few
other
things
in
there
as
well
around
the
automation
and
things
are
consolidating
in
the
direction
of
tide,
but
not
quite
completely
there
so
he's
gonna.
The
expectation
is
based
on
Friday
discussion.
Is
that
we'll
turn
things
on
today
using
the
submit
queue?
A
That
will
give
a
slight
change
in
what
users
perceive
during
code
freeze,
so
things
won't
be
just
completely
consistent
for
them,
but
I
also
feel
like
if
we're
that
that's
better,
because
right
now
we're
making
some
changes
to
code
to
implement
this
new
thing
and
the
development
there
is
happening
right
now.
I
would
rather
see
it
get
deployed,
as
opposed
to
say,
okay.
We
think
this
is
ready
and
set
it
on
a
shelf
for
three
months
and
then
come
back
to
it.
A
So
you'll
probably
see
some
stuff
coming
later
this
week
around
that
do
we
have,
we
know
to
have
anybody
from
CI
signal
here.
So
I
was
actually
I.
I
was
thinking,
CI
signal
was
looking
pretty
great,
but
strangely
not
today,
I
guess
I,
don't
know
if
any
has
looked
at
tests
created
without
anybody
from
CI
signal
on
there's
not
so
much
to
talk
about
on
that
and
I
will
be
spending
my
day,
I
think
trying
to
understand
what
happened,
because
we
were
looking
a
lot
better.
D
A
Touch
base
with
Gwen,
also
yeah
later
today,
it's
this
6:00
a.m.
and
on
the
west
coast,
things
are
just
getting
started,
suspect.
Tomorrow's
release
meeting
will
be
very
interesting
because
I'll
have
had
a
day
back
to
go.
Look
at
all
of
these
things
that
have
changed
and
start
hounding
people
and
get
more
attention.
A
B
A
Imagine
for
there
there
there
was
all
sorts
of
stuff
going
on
between
company
internal
and
various
public
meetings
and
I
think
I
get
the
impression
in
San
Francisco,
just
like
the
whole
Bay
Area,
not
that
he's
there,
but
everybody
just
disappears
for
Burning
Man
last
week,
maybe
and
then
you
throw
in
a
long
weekend
as
well.
It
feels
like
nobody
was
around
this
last
week.
All
right
he
did.
He
had
posted
the
draft
on
hack,
Indy
I,
haven't
gone
and
looked
to
see
if
anybody's
added
anything
there.
A
A
E
F
E
E
C
E
A
E
C
A
A
Is
today
so
I'm
gonna
work
with
Doug
during
the
day
to
see,
if
he's
got
permission,
issues
that
are
different
and
then
we'll
figure
out
what
we
can
do,
because
it's
gonna
take
somebody
at
Google
to
to
change
things
if
necessary.
So
Doug
had
been
on
pto
through
the
end
of
last
week
and
is
back
today
so
I'll
check
in
with
him
to
see,
because
since
he'd
been
out,
I
hadn't
had
the
ability
to
see
if
he's
having
these
permission
issues.
A
Also
so
I'll
have
him
look
at
that,
and
then
we
should
have
the
Googlers
around
today
to
be
able
to
figure
out,
what's
necessary
to
change
and
fix.
So
I
really
appreciate
you
having
tracked
on
and
opened
the
issue
and
following
on
it
and
it's
I,
think
just
because
of
timing.
It
ended
up
not
getting
eyeballs
on
it
super
promptly.
But
today,
since
the
the
beta
will
be
today,
we'll
we'll
just
force
through
it
and
figure
it
out.
F
A
A
So
for
everybody
else,
I'll
drop
a
link
to
this.
We
have
a
issue
about
a
build
problem.
A
A
Alright,
well,
we
have
three
weeks
from
today
three
weeks
to
go:
we've
got
two
beta
releases
and
RC
release
between
now
and
then,
hopefully,
we'll
be
getting
all
of
our
doc
merges
in
in
this
next
period.
As
code
velocity
slows
down
and
people
are
able
to
shift
over
to
a
little
more
focus
on
tests
and
Doc's,
and
hopefully
then
also
we
get
our
CI
signal
straight
and
it's
gonna
be
fun,
especially
looking
at
this
grid.
Today,
alright,
well
I
appreciate
you
all
joining
for
for
the
short
meeting
and
I'll.
A
A
shadows
for
most
of
the
folks
on
the
call
today,
if
you,
if
you
have
the
ability
to
join
some
of
the
other
meetings
over
the
next
couple
of
weeks,
I
think
you'll
see
a
lot
of
discussion
and
talk
going
on
and
and
hopefully
you've
had
some
chats
with
your
your
leads
about
succession,
whether
they're
wanting
to
move
on
hand
the
reins
over
whether
you're
wanting
to
move
up
and
also
it
you're
interested
in
continuing
to
participate
in
the
release,
lead
laterally.