►
Description
A
So
welcome
everybody
to
the
kubernetes
114
release
team
weekly
meeting
today
is
Monday
February
4th
I.
Am
your
host
Aaron
tricking
Berger,
welcoming
you
to
this
wonderful,
publicly
recorded
meeting
in
which
we
all
adhere
to
the
kubernetes
code
of
conduct,
which
boils
down
to
please
don't
be
a
jerk
and
remember
that
everything
you
say
here
will
be
posted
to
YouTube
later
for
all
to
enjoy
or
mock.
You
know
take
your
pick,
so
we
are
at
week
five
week.
A
Five
is
the
only
week
in
the
originally
planned
schedule
that
didn't
have
a
thing
scheduled
like
there
was
no
milestone.
There
was
no
deadline,
there
was
no
nothing
and
then
enhancements,
fries
came
and
went
and
everybody
was
like
wait
what's
a
cap,
so
we
now
have
today.
I
guess
is
kind
of
a
deadline
for
people
to
get
their
caps
written,
get
their
caps
merged
and
then
anything
that
had
an
enhancement
tracking
issue
but
didn't
have
a
cap
will
be
reevaluated
today
for
inclusion
into
the
114
milestone.
A
So
great
everybody,
everybody
did
a
thing
with
caps
I,
just
as
an
experiment.
Last
week
last
Saturday
I
created
a
github
bot
account
solely
for
it
to
watch
the
enhancements
repo
I
set
it
up
to
have
it
do
email
notifications
and
send
them
to
an
email
address,
and
in
that
week,
between
last
Saturday
and
the
Saturday
that
just
happened.
It
got
over
twelve
hundred
and
ninety
emails,
so
people
were
clearly
doing
stuff.
A
The
question
now
is
remember:
we
asked
everybody
to
have
caps
associated
with
their
enhancements
so
that
we
could
use
them.
Can
we
use
them?
What
I
had
asked
people
to
do
is
to
put
sort
of
a
test
plan
and
an
upgrade
downgrade
plan
in
there,
as
well
as
some
kind
of
checklist
in
the
graduation
criteria
area
that
we,
the
release
team,
could
consume
as
sort
of
a
go/no-go
checklist
for
whether
or
not
an
enhancement
is
okay
to
land
in
this
release?
A
I'm?
Okay,
if
this
checklist
is
a
little
squishy
or
vague
right
now,
because
everybody's
still
busy
hacking
away
in
coding
but
I
would
like
for
us
to
be
in
I,
would
like
for
that
checklist
to
be
a
little
more
solidified
and
usable
by
us.
The
release
team,
as
we
approach
code
freeze,
the
situation
I
want
to
avoid,
is
people
feeling
like
goal
posts
are
moving
on
them
as
we
get
to
good
code
freeze.
A
So
it's
important
that
we
take
these
next
couple
of
weeks
to
evaluate
whether
from
a
CI
signal
perspective,
can
you
understand
if
the
tests
are
actually
being
run
and
if
they're
actually
passing
from
an
enhancement
perspective?
Does
it
look
like
this
enhancement
is
actually
complete
and
everything
for
it
has
landed
from
a
Doc's
perspective?
Do
we
feel
like
we
have
a
grasp
on
the
appropriate
level
of
documentation
that
needs
to
land,
for
this
particular
enhancement,
from
a
release
notes
perspective?
A
Is
that
showing
up
in
the
release
notes
draft
in
a
way
that's
explainable
from
a
comms
perspective?
Are
we
going
to
be
talking
about
this?
So
every
member
of
the
release
team
has
something
that
they
can
get
out
of
these
caps
and
I
look
forward
to
us
actually
going
through
and
using
them
to
make
this
a
more
stable
release.
A
A
So
I
know
that
Honus
has
talked
about
this
and
it
kept
and
tried
to
get
some
folks
to
talk
about
it
in
a
sink
release.
Release
team
meeting
I
know
that
sig
cluster
lifecycle
is
very,
very
interested
in
this
from
the
cuvette
DM
sub
project
perspective
and
I
would
like
to
see
those
groups
of
people
sort
of
collaborate
to
make
sure
that
we,
the
release
team,
are
kept
informed
of
how
the
bits
are
getting
cut
and
what
the
schedule
and
plan
for
that
is.
A
If
one
of
the
things
I
should
be
doing
up
front
is
telling
you
my
vision
or
what
I'm
paranoid
about
one
of
the
things
I'm
paranoid
about.
Is
that
we're?
Suddenly
we
find
ourselves
cutting
a
brand
new
release,
a
brand
new
way
that
we've
never
tried
before
at
the
very
last
day?
That's
not
where
I
want
to
be
so.
I
would
like
for
us
to
understand
how
much
of
this
new
way
of
doing
things
we're
going
to
have
in
place
prior
to
code
freeze
and
whether
or
not
that's
efficient.
A
Finally,
my
karpea
has
an
issue
out
in
the
synchronous,
repo
about
scheduling,
a
more
european
and
friendly
meeting
for
the
release
team.
Historically,
we've
had
one
in
a
more
of
a
u.s.
friendly
time
zone
and
one
in
the
european
friendly
time
zone.
Now
that
we
have
all
of
the
shadows
in
the
release
team,
we
can
sort
of
see
the
breakdown
of
where
everybody's
at
it
seems
like.
We
have
roughly
30
people
in
u.s.
A
time
zones
and
roughly
16
people
in
European
time
zones,
so
we're
going
to
try
and
find
the
way
for
the
release
team
to
be
effective
by
starting
to
spread
the
load
across
time
zones.
So
look
for
Mike
to
put
out
doodle
to
figure
out
what
time
works
best
for
everybody,
and
our
goal
would
be
to
have
this
decided
upon
by
the
end
of
this
week,
such
that
we
can
announce
when
a
European
friendly
meeting
is
happening
next
week,
as
I
mentioned.
A
I
believe
the
two
upcoming
milestones
for
us
to
be
aware
of
would
be
that
end
of
day
today.
Claire's
going
to
go
through
is
the
enhancements
lead
and
make
sure
that
anything
that
didn't
have
a
cap,
but
does
now
and
had
an
enhancement
tracking
issue
gets
folded
back
in
and
then
next
week,
Tuesday
February
12th
Honus
will
be
cutting
the
next
middle
to
V
114
alpha
dot.
Three,
that's
all
that
I
have
I'm
super
excited
to
hear
from
everybody
else.
B
Hey
everyone,
so
after
enhancement
phrase,
we
had
a
bit
of
a
trim
down
in
our
metric,
so
we
are
now
at
25
enhancements
that
are
being
tracked
again.
26
of
those
were
deferred
because
of
missing
or
incomplete
cups.
If
a
cup
is
merged
by
EOD
today,
they'll
get
added
back
to
the
milestone
so
expect
that
number
to
increase
of
those
29
enhancements,
Niner,
alpha
Niner,
beta
and
11,
are
stable.
A
Just
from
your
perspective,
as
as
the
enhancements,
lead
and
I
think,
some
of
your
shadows
are
on
the
call
I'm
curious.
If
you
know
one
went
spending
a
couple
minutes
just
talking
about
how
the
experience
has
gone
for
you,
what
what
worked?
Well?
What
did
you
notice
a
lot
of?
What
did
you
wish?
You
had
seen
more
of.
B
Sure,
I
from
my
experience
than
I'll
pass
it
over
to
any
of
my
shadows,
who
are
on
I
think
retrospectively.
We
probably
could
have
done
more
to
really
iterate
that
caps
were
mandatory
during
the
cycle,
but
I
think
with
all
releases.
When
you
try
to
do
new
process,
there
are
some
pickups
and
we
iterated
really
fast
and
we're
able
to
say,
okay,
we'll
give
an
extension
just
for
cups.
I,
think
things
that
also
have
gone
really
well
have
been
generally
folks
are
very
responsive
to
the
issue.
B
C
Yeah
I
don't
have
too
much
more
to
add
other
than
what
Claire
said.
I
think
you
know
a
few
surprises
for
folks
as
to
what
it
means.
I
think
still,
the
state
that
they
need
to
be
in
is
a
little
bit
fluid
in
getting
to
implementable
and
what
exactly
that
means
and
who
exactly?
That
means
something
to
is
still
a
little
fluid
going
from.
C
You
know,
provisional
to
implementable,
so
just
getting
the
states
I
think
it's
folks
are
still
getting
used
to
it
in
the
community,
but,
as
Clair
had
mentioned,
given
that
people
around
ready
to
help
out
when
we
were
shepherding
them
into
this
process,
I
think
was
a
good
outcome,
so
I
think
for
next
time.
Certainly
there'll
be
a
lot
more
folks
with
a
lot
more
skin
in
the
game,
and
we
will
get
the
kept
process
better
as
well
as
a
result
of
this
hoping
to
take
some
of
the
learnings
back
to
sig
p.m.
C
D
A
Excellent
thanks
to
all
of
you
that
was
me
trying
to
prime
the
pump
a
little
bit
for
the
fact
that
we
do
have
a
retrospective
at
the
end
of
all
of
our
releases
and
I
figured.
It
was
a
good
chance
to
just
talk
about
that.
Well,
it
was
fresh
in
your
minds.
I
pasted
a
link
to
the
retro
doc
in
chat
I'll
link
to
that
retro
doc
is
also
available
at
the
top
of
the
meeting
minutes
and
the
link
in
his
Cates
114
retro.
A
So,
as
you
see
stuff
stuff
that
works
well
stuff
that
doesn't
work
well
things
that
you'd
like
to
suggest
as
improvements
going
forward,
that's
definitely
a
place
to
put
them
so
that
we
as
a
community,
can
talk
about
them
at
the
end
of
this
release
cycle.
So
thank
you
all
for
your
input.
I
just
tried
to
briefly
summarize
that
in
there
and
yes
to
Luckys
point
I'm
trying
to
suggest
that
caps
are
capsules,
a
process
are
a
thing
that
are
owned
by
sig
p.m.
A
A
E
E
There
are
currently
a
couple
jobs,
a
failing,
I,
think
I
think
there's
a
there's,
a
there's,
a
PR
open
from
from
six
storage
there's
there
was
a
problem
on
their
end
and
there
are
currently
working
on
fixing
it
now
and
then
the
other
and
then
the
other
big
change,
especially
since,
especially
since
May
mode
for
most
of
their
jobs.
Since
this
weekend
there
are
five
filling
jobs
on
master,
a
master
of
grade,
a
a
lot
of
a
lot
of
them.
E
They
need
a
little
bit
more
hands-on
and
debugging
from
a
from
RN
to
be
able
to
a
provide
a
little
bit
more
feedback
on
a
one
might
actually
have
gone
wrong.
Some
of
them.
We
tracked
him
down
to
watch
a
to
commit
on
test
him
from
a
another.
A
another
issue
which
is
which
I
link
the
73
775
seems
to
be
affecting
mostly
sick,
clustered
life
cycle,
a
some
of
the
upgrade
tests
they
have
and
also
a
we
pray.
A
F
I
am
I
am
back
to
your
strand
of
in
this
cycle.
This
is
my
first
time
going
up
update
but
hoping
this
is
going
to
go
well
so
far
we
have
some
metrics
about
the
number
of
open
'dearest.
It
is
51
open
and
then
close
it
also
36,
open
and
51
close
it
also.
We
can
fix
it.
Those
two
links,
so
you
can
use
them
to
check
out.
How
is
it
going
so
far?
Also
we
have
a
bug
tracking
and
fixes
the
link
for
that.
F
Now
you
have
a
Google
document
with
all
the
issues
so
far
and
a
new
page
is
added
and
it's
called
reset
across
the
dishes.
It
is
what
is
closed
within
the
last
10
days.
We
will
try
to
get
that
updated
and
to
see
how
is
it
going
on
so
far
also
we
are
quality
top
talking
and
planning
to
switch
to
air
table
instead
of
Google
Docs.
F
We
will
try
to
do
that
ad
cycle
and
to
see
can
we
form
some
team
or
group
to
work
a
debt
and
we
will
try
to
cap
to
keep
everyone
updated
as
of
the
progress,
so
we
are
hoping
that
this
is
going
to
do
well
and
to
do
the
job.
I
hope
I
have
not
forgotten
anything,
but
if
there
are
any
questions,
let
me
know
or
let
us
know
in
the
seek
race
web
channel.
A
First
sort
of
like
to
an
issue
in
chat:
that's
called
investigate,
automation
to
facilitate
tracking
spreadsheets.
It
sounds
like
that
is.
Maybe
what
you
are
talking
about.
I
would
appreciate
some
more
insight
on
your
plans
as
you
have
them.
That
seems
like
maybe
the
right
issue
to
track
that
if
you
are
tracking
this
work,
someplace
else,
let
me
know
yes.
F
A
A
F
G
Hey
so
the
number
of
peers
we
merge
this
week
was
around
137,
which
is
a
big
uptick
from
the
last
two
weeks
where
it
was
around
80
in
the
last
two
weeks.
This
is
a
pretty
big
uptick.
The
next
upcoming
milestone
for
testing
friends,
that
110
jobs
will
be
removed
this
week
and
114
jobs
will
be
added
the
weakness
after
that
regarding
proud.
G
We
move
the
full
cover
at
easy
to
a
cops,
a
double-a
job,
to
an
optional
job,
which
means
that
you
can
give
a
test
communities
to
get
to
run
the
job
owner
here,
but
it
would
not
be
blocking
by
default
and
the
since
we
migrated
this
to
being
optional.
Now
we
will
remove
all
the
old
statuses
that
were
on
old
tears
and
they
should
now
be
all
three
and
that's
it
from
us.
G
A
H
Everybody,
this
will
be
a
real,
quick
update,
just
kind
of
waiting
for
all
the
kept
stuff
to
shake
out.
So
you
see
exactly
we're
looking
at
four
as
far
as
enhancements
and
then
talking
about
dividing
that
workload
so
kind
of
in
a
holding
pattern
right
now
and
keep
engaging
with
the
team
as
well
as
working
on
the
release.
Playbook
and
that's
pretty
much.
It.
I
I
I
A
Okay,
yeah
I,
just
like
looking
at
the
draft
it.
It
feels
really
sick,
centric
right
now,
I'm
gonna,
wonder
if,
as
we
get
closer
to
the
release
day,
I'm
gonna
start
wondering
from
the
perspective
of
an
end
user.
Do
these
make
sense
to
me,
or
is
this
a
question
of
like
we
have
these
all
broken
down
by
sake
right
now,
because
it's
easy
to
automate
from
the
production
perspective,
and
this
is
me
just
riffing
and
making
stuff
up
with
it.
A
What
I
feel
like
I
have
seen
historically
in
the
past,
is
that
there's
some
confusion
over
what
release
notes
are
so
I?
Think
I
still
have
this
item
on
my
plate
from
the
113
retro.
The
release
notes
are
not
supposed
to
be
a
dumping
ground
for
everything.
A
sig
did
they're
supposed
to
be.
What
are
the
changes
that
landed
in
kubernetes,
kubernetes
and
then
possibly
as
a
user
I
feel
like
the
release.
Notes
should
be
like
what
are
the
things
that
are
interesting
to
me.
A
Not
what
did
each
of
the
36
land
in
kubernetes
kubernetes,
which
is
why
we,
we
often
have
them
broken
down
or
in
the
past
I
know.
When
I
worked
on
release
notes,
they
were
broken
down
into
like
here's,
the
action
required
before
you
upgrade
your
cluster.
We
did
try
and
sort
of
bring
up
at
a
top
level,
the
the
new
features
or
the
the
big
features,
and
that
was
going
to
sort
of
overlap
with
the
the
like
top
five
features.
A
We
would
have
comms
sort
of
broadcast
in
you
know
a
series
of
blog
posts,
and
things
like
that.
So
just
as
we
start
to
think
about
what
the
theme
of
this
release
is,
what
the
shape
of
it
feels
like
when
I
look
at
this
release,
its
nose
release,
notes
trapped
right
now,
it's
difficult
for
me
personally
to
to
get
a
sense
of
what
that
is.
Yeah.
I
J
J
Basically,
this
meeting
is
for
the
release,
lead
hint
enhancement,
lead,
release,
release,
notes,
lead
any
of
their
shadows
and
anybody
else
that
wants
to
join.
But
what
we
do
is
we
go
through
the
25
different
enhancements
and
we
look
at
the
layout
of
the
blog.
So
are
we
starting
to
see
patterns?
Are
there
certain
ones
on
here
that
are
ones
that
are
going
to
be
major
for
the
community?
J
The
cig
leads
on
those
and
who
do
we
need
to
contact
to
kind
of
put
on
point
to
help
write
those
blogs
for
the
kubernetes
website,
and
so
this
kind
of
really
from
becomes
perspective
is
a
big
planning
meeting
for
us
and
then
from
there
we'll
start
to
riff
on
materials
and
get
ahead
of
fit
versus.
You
know
the
week
right
before
the
release
goes
out,
we're
trying
to
do
the
released
long.
So
if
you
have
not
responded
to
that,
doodle
I
sent
it
over
email.
J
A
Thank
You
Natasha
I
mean
yeah
from
from
my
perspective,
I
have
no
idea
what
any
of
the
enhancements
are
right
now,
because
my
enhancements
team
has
been
doing
such
an
awesome
job
like
shepherding
all
of
them.
If
that
hasn't
had
to
be
of
worry
for
me,
but
my
goal
is
to
start
reading
through
those
this
week
to
get
a
better
sense
of
the
shape.
Okay,.
A
A
Okay,
so
I
will
work
to
sync
with
that
offline.
As
far
as
I
know,
cutting
the
alpha
build
was
no
less
controversial
than
cutting
the
previous
alpha
build.
The
same
issues
happened,
but
they
weren't
showstoppers
or
crazy
blockers.
That
was
just
kind
of
business
as
usual
hands
up.
Who
here
has
actually
used
the
alpha
build
of
kubernetes?
Oh
man,
oh
wow,
okay,
mr.
kind
over
there
nicely
done
all
right.
That
was
more
more
for
my
own
curiosity.
Thank
you
for
that.
A
A
Okay,
great,
like
I
personally,
have
a
sense
of
not
entirely
knowing
what's
going
on,
but
stuff
is
definitely
happening,
and
so
I
really
appreciate
everybody's
effort
in
pushing
stuff
forward,
so
I
think
the
best
way
for
me
to
figure
out
what
is
happening
is
to
go
start
doing
a
bunch
of
reading,
rather
than
holding
everybody
hostage
here
to
chat
about
stuff.
But
if,
in
the
future
we
find
that
chatting
about
stuff
is
a
better
way
for
everybody
to
stay.
Informed
I'm
super
open
to
that
too.