►
Description
A
Hi
everybody
welcome
to
this
week's
edition
of
the
kubernetes
114
release
team
meeting
today
is
Monday
February
18th
I.
Am
your
release,
lead
Aaron
of
cig
beard
and
you
are
all
being
publicly
recorded
and
will
hopefully
be
adhering
to
the
kubernetes
code
of
conduct,
which
basically
boils
down
to
please
don't
be
a
jerk.
This
meeting
will
be
posted
to
YouTube
later
so
you
can
all
look
at
your
smiling
faces.
I
thought
I
would
try
something
a
little
bit
different
this
week
and
see
if
this
works
going
forward.
A
I
know
I,
am
your
release
lead,
but
I
would
really
rather
hear
from
everybody
else.
First
and
then
I
can
clean
up
whatever
we
decide.
We
need
to
kick
to
the
parking
lot
at
the
end,
so
I'll
just
say
up
front
that,
according
to
our
schedule
this
week,
the
only
big
thing
on
our
radar
is
the
release.
114
branch
and
cutting
a
beta
off
of
that
so
I'm
sure
Hannes
will
have
a
lot
to
talk
about
and
then
next
week
we
will
start
to
kick
up
the
frequency
of
these
meetings
to
Monday
Wednesday
Friday.
A
B
A
So
Claire
I
believe
we
met,
along
with
some
other
folks
on
the
team,
with
Natasha
to
talk
about
sort
of
the
themes
for
the
release
and
blog
posts,
and
part
of
this
was
going
to
involve
us
asking
the
different
say,
needs
sort
of
what
they
thought.
Their
important
themes
for
this
release
were:
what
can
you
share
with
us
about
that
sure,
so.
B
Talking
with
the
communications
team,
they're
looking
to
focus
on,
we
know
for
sure
Windows,
and
then
we
have
a
few
other
areas
of
interest,
though
we
are
still
reaching
out
to
some
cig
leads.
I
was
in
the
midst
of
an
off-site
last
week,
so
a
little
behind
on
that,
but
Windows
for
sure.
We
know
and
then
were
exploring
a
few
other
potential
themes.
A
I
think
another
question
I
had
I
also
was
a
little
bit
out
of
the
loop
last
week
was,
if
you've
had
a
chance
to
look
through
caps
and
get
a
sense
for
whether
or
not
they
are
suitable
and
usable.
You
know
whether
or
not
we
feel
like
yeah
that
graduation
criteria
really
does
have
a
checklist
that
we
can
understand
and
yeah
there's
definitely
a
test
plant
there
did
you
have
a
chance
to
take
a
look
at
any
of
that
on
your
end,
Claire?
Yes,.
B
So
I
started
doing
that
and
made
it
through
a
handful
of
cups
and
I've
been
putting
notes
on
that
in
the
existing
spreadsheet
for
enhancements
under
the
notes
section.
So
I
have
just
something
where
it's
like
my
name
and
then
I'll
say
notes
on
the
cup
and
give
one
to
two-sentence
summary
of
what
I'm
seeing
within
that
cup.
So
I
haven't
finished
all
of
them.
Yet.
B
A
Okay,
that's
good
to
know
that
I
personally
am
feeling
like
we
really
want
to
have
a
much
better
sense
of
whether
or
not
they
are
usable
or
not
and
possibly
use
that
as
forcing
criteria
when
we
get
to
burn
down
well
I'm
at
it,
I'm
sorry
I
kind
of
blazed
right
on
through
to
enhancements
on
top.
Could
somebody
please
volunteer
to
be
a
note-taker
I'm,
not
really
good,
at
doing
the
active
listening
and
talking
and
typing
thing
at
the
same
time?
Well,
taking
it
something!
That's
already
for
money.
A
E
Hi
everyone,
so
we
ended
last
week
in
a
pretty
good
state.
We
in
fact
started
this
week
on
a
almost
clean,
almost
green
test,
great,
which
is
great.
There
have
been
not
for
long.
Fortunately,
I.
We
are
seeing
some
failures
s
for
the
last,
like
a
couple
of
hours.
From
what
I
see,
some
of
them
seem
like
timeouts,
and
things
like
that,
so
I
want
to
watch
them,
maybe
for
another
run
and
see
how
persistent
they
are.
E
So
that's
on
failed
runs
speaking
of
flakes.
This
is
something
that
we
will
be
looking
in
a
little
bit
more
detail
over
the
last
couple
of
weeks
and
at
least
until
code
freeze,
the
intention
there
is
to
get
as
clear
a
signal
as
possible
once
we
enter
as
we
approach
as
we
approach
the
approaches
with
the
release
date.
E
A
A
So
a
part
of
a
part
of
my
personal
sense
on
the
test
plan
front
is
that
if
you,
a
CI
signal
are
unable
to
actually
determine
whether
or
not
a
given
enhancement
is
working
correctly.
We
should
not
shift
that
enhancement,
so
I
feel
when
I
talk
about
using
caps
as
forcing
functions.
I
think
part
of
what
I'm
suggesting
is
that
you
have
the
authority
to
say
if
there
isn't
actually
a
test
plan
for
your
enhancement
that
I
or
my
shadows
as
CI
signal
cannot
read.
I,
don't
think
this
enhancement
belongs
in
this
release.
E
That's
interesting,
I,
wonder
so:
I'm,
not
clear
I,
wonder
if
some
enhancements
have
the
intention
of
adding
a
testing
plan
soon,
but
I
think
it's
a
really
good
shout
out,
and
maybe
that's
something
for
us
to
pick
up
and
go
back
to
do
folks
that
have
submitted
enhancements
and
try
for
a
bit
more
of
a
definition.
Great.
A
So
my
recommendation
would
be
for
you
and
your
enhancements
to
sort
of
identify
those
those
issues
or
those
caps
that
don't
have
a
test
plan
that
you
can
understand
and
ask
them
to
get
to
a
test
plan.
You
can
understand
because
we
will
be
taking
a
much
much
closer.
Look
at
that
as
we
begin
burndown
next
week,
because
if
we
can't
tell
whether
or
not
a
given
feature
is
working,
it
doesn't
seem
to
make
sense
to
really
lock
it
in
into
code.
E
A
They
have
it
under
their
own
test
plan.
That's
that's
great
I
still
feel
like
they
should
be
able
to
enumerate
that,
so
you
should
be
able
underst.
You
should
I
for
me
personally,
where
I
in
that
role,
I
would
ask
for
like
where's
the
test
grade,
dashboard
that
I
can
look
at
or
what
are
the
specific
tests
names
or
what's
the
regex
that
I
can
use
to
make
sure
this
is
in
the
this
is
green.
E
A
E
A
F
A
Had
I
had
launched
some
kind
of
email
thread
last
week,
but
I
haven't
had
the
chance
to
catch
up
on
everything.
So
I
wasn't
clear
to
me
where
we
stood
on
all
of
that
I
personally
love
to
see
all
green,
so
that's
great
I
just
in
it
would
be
even
better
to
see
coverage
on
more
than
just
the
GCE
cloud
provider,
although
I
guess
technically,
we
do
have
QA
diem
has
a
slightly
different
way
of
standing
up
clusters.
So
there
is
that.
D
D
G
G
B
F
A
A
H
H
A
H
H
I
H
J
We
have
a
we're
investigating
usage
of
spyglass
or
issue
tracking
so
as
a
part
of
our
automation
efforts
we're
kind
of
looking
into
how
all
of
this
might
be
automated
in
some
sort
of
meaningful
way.
This
is
kind
of
looking
into
the
fact
that
we
are
not
sure
exactly
where
we
should
be
placing
stuff,
although
we
we
understand
that
we're
kind
of
moving
towards
a
spyglass
from
Juba,
nadir
and
I'm,
not
honestly
sure
about
that
of
that
framework.
Just
yet
as
well.
J
H
A
Right
I
mean
I,
expect
like
a
bunch
of
the
114
jobs
would
fail
if
there
was
no
114
branch
to
pull
from,
but
you
could
at
least
still
verify
like
that.
All
of
the
old
jobs
were
removed,
all
the
old
dashboards
were
removed
and
all
of
the
new
dashboards
were
created
and
that
they
looked
about
right
just
that
they
wouldn't
pass
I
believe
in
times
past
we
have
had
a
bit
of
a
period
where
the
the
jobs
were
created
before
the
branch
was.
But
it's
like
it's
totally
fine.
Whatever
ordering
we
choose.
Ok,.
G
Hi
everybody
I'm
Bonnie
I'm
here
to
talk
about
dogs
Jimmy's,
not
available
because
he
has
a
conflict
with
their
head
another
meeting,
but
what
we
have
done
so
far.
We
have
created
a
branch
for
dogs
which
is
one
dev
114
and
created
a
placeholder
that
have
been
linked
on
the
docks
that
will
be
merged
during
the
release.
So
we
have
assign
each
other
announcement
that
will
be.
We
are.
A
A
K
Notes
absolutely
this
week
we're
meeting
to
try
and
figure
out
if
we
should
change
the
changelog
format.
I
had
the
dumb
idea
of.
Maybe
we
should
make
a
website
that
tracks
all
of
our
release,
notes
throughout
all
the
different
versions,
so
we
could
actually
be
able
to
filter
based
on
releases,
be
able
to
see
what
changed
between
111
and
114
and
say
you
only
want
to
be
able
to.
You
only
want
to
see
what
storage
stuff
changed.
So
we're
gonna
talk
about
that
that
it
that
is
pie-in-the-sky
idea.
K
That's
not
going
to
block
us
from
doing
anything
else.
Also,
this
week
we're
gonna
start
working
on
updating
the
external
dependencies
and
I
just
like
an
hour
ago
pushed
the
draft
for
release
notes
for
this
week.
That's
where
things
are
right.
Now
things
are
gonna,
start
ramping
up
this
week
and
next
week
for
us,
okay,.
A
So
same
question
to
you:
the
release,
notes
representative
from
a
comms
perspective.
What
what
do
you
feel
like
you
got
out
of
last
week's
meeting,
or
what
did
release
notes
get
out
of
last
week's
meeting
with
comms
on
sort
of
trying
to
decide
what
the
important
enhancements
and
release
note
or
release
themes
would
be
for
114.
K
That's
kind
of
tough,
because
Lindsey
was
at
the
first
half
and
I
was
at
the
second
half,
because
I
had
an
appointment
halfway
through
and
she
had
an
appointment
halfway
through.
So
together
we
got
kind
of
a
full
perspective.
What
we
got
out
of
it
was
what
are
the
pet
like?
What
are
the
patterns
based
on
all
the
different
release?
Notes
looking
at
it
from
a
release,
note
perspective,
you
actually
pointed
it
out
pretty
well,
there
was
an
abundance
of
different
changes
for
storage
that
are
going
into
1.14.
A
C
C
As
you
said,
I,
don't
think
it
matters
too
much
except
the
chops
will
fail.
Probably
if
there
is
no
branch
there.
Yet
so
I
will
try
to
align
with
the
testing
in
for
a
team.
The
least
I
will
do
is
like,
of
course,
let
them
know
as
soon
as
I've
cut,
but
I
will
try
to
figure
out.
Maybe
today,
what
like?
What
is?
What
is
the
more
appropriate
way
to
do
it
regards
to
ordering,
and
if
that
is
figured
out,
I
will
update
the
document.
The
role
handbook.
C
In
regards
to
cutting
the
thing
itself,
I
don't
expect
any
issues,
but
well
maybe
now
I
changed
it,
but
we
will
find
out.
I
will
do
the
cut
tomorrow,
my
noon,
which
is
early
morning
time,
so
that
should
give
us
a
bit
of
like
overhead
overlap
with
with
us
folks,
yeah
I.
Guess
that's
pretty
much
it
regarding
the
cut
any
questions
about
that.
A
C
I
will
try
to
figure
that
out
and
in
the
role
handbook,
but
honestly
I
cannot
remember
how
often
we
did
it
in
the
last
release
as
soon
as
like
at
the
end,
at
the
end
of
the
release
cycle,
we
did
it
daily
I'm
happy
to
align
there
on
on,
like
which,
time
of
the
day
we
do
it
last
releases.
We
always
did
it
end
of
the
day.
I
think
Pacific
time.
That
would,
of
course,
be
not
too
good
for
me,
but
I
can
do
it.
C
I
don't
know,
for
example,
whatever
I
can
do
it
yeah
we
will
figure
out
a
time
which
is
suitable
for
everybody.
The
thing
is,
we
will,
especially
towards
the
end
of
the
release,
probably
be
a
bit
careful
about
when
and
if
we,
if
we
do
the
branch
fast
forward,
so
that
we
don't
get
into
a
situation
where
we
need
to
cherry-pick
some
things
in
case
we
got
some
bad
commits
in
to
master,
but
I
think
that's
that's
that's
more
relevant
for
later.
C
A
So
one
thought
I
had
is
maybe
there's
somebody
in
the
Pacific.
It
looks
like
your
shadows
are
all
in
the
Pacific
time
zone.
Maybe
we
could
look
to
ensure
that
one
or
more
of
them
would
be
capable
of.
You
know
pushing
the
button
so
to
speak,
so
that,
if
you're
not
available-
and
we
find
that
we
do
need
to
make
it
happen,
we
could
have
it
happen
on
a
time
zone
that
lines
up
with
where
another
large
chunk
of
contributors
are
yeah.
C
The
problem
here
is
that
my
shadows
don't
have
the
appropriate
access
or
permissions
to
certain
things.
I
talked
about
this
with
Caleb
and
we
are
not
really
sure
if
we
want
to
give
all
the
shadows,
all
the
permissions,
so
at
least
for
now
it
seems
that
this
will
be
so
basically
only
the
release
branch
lead
and
the
batch
patch
management
team
will
have
the
appropriate
rights.
C
C
A
But
while
I
recognize
the
way
that
branch
thinking
works
is
not
actually
just
a
get
push
or
I
get
fast
forward,
there's
a
little
bit
more
to
it
than
that.
It
does
feel
as
though
that
is
a
significantly
reduced
permission
set.
That
applies
just
to
a
gift
repository,
as
opposed
to
all
of
the
different
places
that
we
store
bits
once
they're
cut,
yeah.
H
C
C
C
Anyway,
I
guess
I
link
to
the
document.
If
anybody
has
some
input
on
what
needs
to
be
there
until
it,
it
would
get
it
can
get
peered
in
as
provisional
I
would
say.
That's
a
good
place
to
add
comments
in
this
Google
document
and
I
will
keep
you
up
to
date
on
what
the
status
is
regarding
this
cap.
The
other
side
of
the
coin
is
how
to
add
this
package
publishing
and
so
on
into
the
release
process.
C
What
people
think
is
needed
to
get
it
merged
as
provisional,
like
the
bare
minimum
to
get
it
merged
and
then
I
feel
we
can
hash
out
details
and
further
PRS,
and
also
still
a
bit
unclear
to
me
is
who
should
be
reviewers
and
approve
us
to
this
cap.
I
feel
the
owning
sake
should
be
sig
release
as
it's.
A
A
So
that's
a
start,
but
perhaps
you
know
your
Caleb's
or
your
Tim
peppers
or
something
like
that.
But
we
can.
We
can
handle
that
offline
I've
I've
been
like
watching
all
this
stuff
from
a
distance
for
the
past
couple
of
weeks.
I
do
intend
to
make
a
genuine
effort
of
reading
through
both
of
these
caps
to
understand
when,
where
and
how
they're
going
to
land.
C
A
James
I,
don't
know
if
you
have
any
interest
in
these
or
if
you
have
any
suggestions
for
people
from
the
Cates
infra
working
group
who
might
be
applicable
here
since
I
believe
eventually,
though
I
haven't
read
this
like
at
some
point,
will
want
to
talk
about
this
in
the
context
of
how
does
it
run
on
CN
CF,
owned
infrastructure,
not
Google
and
infrastructure?
All.
C
A
A
A
Okay,
so
thank
you.
Everybody
for
showing
up
I.
Think
I
gave
a
couple
suggestions
for
some
things
for
people
to
do,
as
always,
you
more
or
less
have
my
full
authority
to
say
no,
whenever
you
say
no
to
stuff
and
if
you
get
pushed
back
and
you
need
escalation,
I
can
be
the
person
you
escalate
to
and
if
I'm
not
available,
Mike
and
then
most
likely
will
be
and
I
think
that's
all
I
have
all
right:
cool,
happy,
Monday.
Everybody.