►
Description
A
A
B
A
Yeah
I
don't
know,
maybe
I'm
celebrating
the
fact
that
Seattle
was
supposed
to
get
yet
more
snow
today,
but
it's
actually
just
really
bright
and
sunny
out
there,
and
nobody
knows
what
to
do
with
it
and
the
grocery
stores
are
ransacked
yet
again.
No,
it's
fine,
that's
whatever,
but
yeah,
apparently
Portland
in
California
are
gonna
have
a
fun
time
today,
through
Wednesday.
Let's
see
how
it'll
just
get
Sun,
it's
great.
A
A
So
I'd
like
to
welcome
everybody
to
the
one
for
kubernetes
114
release
team
meeting
this
is
week.
Eight
today
is
Monday
February
25th
I
am
your
host
Aaron
of
cig
beard
and
you
are
all
being
publicly
recorded
and
so,
of
course,
will
be
on
your
best
behavior
to
adhere
to
the
kubernetes
code
of
conduct
which
boils
down
to
please
don't
be
a
jerk
as
soon
as
the
recording
has
been
processed
I'll
upload
this
to
you
youtube.
So
you
can
all
see
your
smiling
faces.
A
I
thought
the
pattern
I
did
last
week,
kind
of
worked
really
well
so
I'd.
Rather
let
everybody
else
go
first
and
kind
of
clean
up
stuff.
At
the
end,
the
one
thing
I
will
say
at
the
top
is
for
those
of
you
who
missed
my
community
meeting
update
on
Thursday
I'm
so
excited
because
it's
the
start
of
burndown,
which
means
we
get
to
start
having
more
meetings.
So
I
get
to
see
you
all
more
often.
A
So,
if
you
are
on
the
kubernetes
release
team
mailing
list
or
your
the
kubernetes
cig,
release
mailing
list,
I
think
I,
just
added
it
to
the
community
calendar
as
well.
You
should
now
see
that
there
are
additional
30
minute
meetings
scheduled
for
Wednesday
and
Friday,
using
the
same
zoom
URI
that
you
are
at
right
now
so
same
room,
and
we
do
have
a
book
for
up
to
an
hour
if
we
have
to,
but
generally
I
found
that
burndown
meetings
seem
to
be
a
little
more
short
and
tactically
focused.
E
Yeah
so
right
now
we
have
34
enhancements
that
are
slated
for
114,
that's
for
less
than
last
week,
just
four
more
enhancements
getting
either
deferred
or
were
determined
that
they
didn't
actually
need
to
be
tracked.
I
think
two
of
those
specifically
for
those
who
are
curious
that
were
determined
they
didn't
need
to
be
tracked,
were
AWS
out
of
tree
related,
so
those
were
removed.
E
33
of
these
enhancements
are
slated
with
a
cup
there's
still
one
outstanding.
It
was
due
to
being
an
approved
exception,
but
we're
making
sure
that
they
will
have
a
cup
which
brings
me
to
the
next
bullet
point
of
our
enhancements.
15
are
at
risk
due
to
missing
testing
plans
from
their
cups.
This
is
something
that
we
want
all
cups
tab
just
because
it
helps
us
know
if
they're
actually
ready.
So
anything,
that's
in
the
spreadsheet,
that's
marked
is
at
risk
right
now.
A
Since
you
had
mentioned
out
of
tree
enhancements,
we
can
talk
about
this
natasha
Caitlyn
when
we
get
to
your
section,
but
I
did
appreciate
that
Nishi
from
sig
AWS
made
sure
to
to
create
caps
and
create
tracking
issues
and
whatnot.
But
I'm
of
the
opinion
that
when
it
comes
to
the
release
team
tracking
things
for
burned
down,
we
should
only
be
tracking
stuff
that
lands
and
kubernetes
kubernetes.
But
we
probably
still
want
to
help
out
people
who
are
doing
things.
A
The
right
way
like
working
on
your
stuff
out
of
tree
is
what
we
as
a
community
and
as
a
project,
would
like
to
encourage
because
it
allows
people
to
release
on
their
own
time
and
on
their
own
schedule.
So,
for
whatever
reason,
cig
AWS
would
still
like
to
tie
to
the
publicity
cycle
of
114
and
I
I.
Think
I
can
understand
that
I'd
like
to
be
clear
that
there's
probably
no
technical
reason.
They
couldn't
just
release
their
things
right
now
and
go
be
loud
on
whatever
channels
best
suit
them.
G
F
Yeah,
so
there's
there's
definitely
a
couple
of
ways
that
we
could
do
that
and
I
think
we
could
I
think
it
goes
back
to
that
key
message
and
document
that's
outside
of
the
blog,
where
we
have
those
four
questions
that
reporters
are
going
to
ask
each
time
and
one
of
them
is
how
does
one
point?
Thirteen
and
one
point
fourteen
tie
to
each
other,
and
what
does
this
mean?
What
for
one
point,
fifteen
and
I
know
during
our
brains
from
discussion
we
had
slated
kind
of
part
of
GWS.
F
Discussion
may
be
relevant
there,
so
I
feel,
like
we've,
already
kind
of
started,
that
discussion
I'm
independently
from
them,
which
is
wonderful
and
I,
think
we
could
put
more
messaging
and
they
are
from
the
AWS
SIG's
about
that
I
know
this
will
be
definitely
interesting
to
reporters
and
we
could
get
them.
You
know
kind
of
that
bump
up
coverage,
but
they
wanted
to
in
terms
of
a
blog
post,
separate
I,
think
that's
a
great
idea
where
you
don't
have
to
be
tied
to
the
five-day
series,
so
it
doesn't
have
to
come
help
after
the
release.
F
We
could
always
put
it
out
before
the
release
and
then
we
could
talk
about
it.
You
know
when
we're
doing
the
interviews
with
it
and
have
their
messaging
in
that
key
message
document
which
just
sent
to
all
the
reporters
and
that
if
they
have
further
questions
about
the
EWS,
we
could
set
up
separate
meetings
with
that
sig.
So
we
can
definitely
do
some
publicity
for
them
around
it.
We
can
you
know
post
blog
on
Twitter.
A
Okay,
that
sounds
like
a
good
compromise
for
now.
It's
it's,
not
something
I
want
a
future
trip
on
too
hard.
It's
just
the
sort
of
thing
where
I
do
want
to
incentivize
that
good
behavior
of
giving
us
as
a
release
team,
less
stuff
to
track,
and
in
you,
the
cloud
providers
or
content
producers
way
to
produce
your
content
on
your
own
I.
Just
recognized
that
we
have
such
an
awesome
hype
machine
here
that
people
still
want
to
get
plugged
into
it,
however,
is
most
appropriate
for
them
is.
H
A
F
Caitlin
Bernard
for
the
kubernetes,
blog
and
I
can
send
you
kind
of
the
criteria
for
that
and
the
evaluation.
And
then
we
have
a
blog
calendar
and
we
slated
them
there
and
then
from
there.
We
promote
that
blog
on
social,
so
any
I
mean
anybody
can
submit
a
blog
as
long
as
its
original
content
and
it
it
follows
a
criteria,
so
the
SIG's
could
definitely
be
submitting
blogs,
as,
as
things
are
finished
outside
of
the
release
cycle,
and
we
actually
encourage
that
so
I
mean.
H
I
just
think
it
might
be
worthwhile
if
there
is
a
way
for
some
of
these
out
of
tree
enhancements.
If
they
want
to
take
advantage
of
the
release
machine,
it
seems
like
there's
more
than
enough
ways
for
them
to
do
it
without,
involving
you
know
your
yourself
or
other
people
who
are
busy
with
doing
release
related
things.
Yeah.
F
F
You
know,
I,
think,
that's
a
that's
a
really
good
way.
Another
good
time
as
well
is
at
coop
con.
We
have
the
keynotes
once
you
know,
to
dedicated
to
all
CNCs
projects
and
updates
on
Sancerre
projects,
and
so
we
go
out
to
all
the
maintainer
and
we're
just
hey.
What's
going
on
with
your
project,
can
you
provide
us
updates
for
the
slide,
so
that's
another
way
that
we
could
get
some
work,
that's
being
done
outside
of
the
releases
updated
to
that.
You
know
eight
thousand
plus
audience.
A
Okay,
I
think
as
Claire,
perhaps
as
you
and
I
and
others
interact
with
people
who
we
counter
more
things
that
they
turn
out
to
be
out
of
treat.
It
sounds
like
to
me
the
behavior
we
want
to
incentivize.
Is
it
we'd
love
for
you
to
write
a
blog
post
whenever
your
feature
is
ready
to
go
so
if
you're,
a
cloud
provider
and
you're
hooking
up
some
awesome
new
cloud
provider
feature
to
kubernetes,
and
you
can
do
that
today.
A
Why
not
talk
about
it
today
and
then
we
can
also
make
sure
during
large
moments
like
the
next
kubernetes
release
or
a
coupon
or
something
we
can
go
back
and
look
at
blog
posts
and
kind
of
be.
You
know
include
like
hey
by
the
way,
if
you
only
hate
this
blog,
when
the
new
kubernetes
release
comes
out,
you
may
have
missed
the
following
things.
That
also
happened:
yep,
okay,.
A
Just
a
personal
story
on
work
working
through
the
enhancements
stuff
I
haven't
had
time
to
go
through
most
of
them
with
this
level
of
detail,
but
I
took
a
deep
dive
on
an
enhancement
about
node
leases.
Let
me
try
and
find
the
spreadsheet
go
fast,
but
my
personal
experience
was
I
went
to
read
it
to
figure
out.
Okay,
so
like
why?
Why
is
this
node
least
thing
being
called
beta?
Was
it
was
it
called
alpha
before
like?
A
Did
it
actually
go
out
the
door
as
alpha
can
I
go,
find
a
documentation
or
a
piece
of
information
that
tells
me
that
and
I
couldn't
by
reading
the
cap?
Okay,
so
then
the
test
plan
they
talked
vaguely
about
like
a
description
of
oh
the
word,
lease
was
in
the
test,
so
I
figured
like,
oh,
maybe,
if
I
go
like
grab
the
code
base
and
look
for
tests
that
have
the
word
lease
in
them.
Maybe
that'll
tell
me
if
tests
have
been
written
but
I
still
don't
really
know
like
okay.
A
How
do
I
go
find
where
the
tests
are
actually
running
so
I
had
to
ask
a
question
about
that,
and
I
got
back
information
that,
oh
by
the
way
like?
Actually
this
is
a
feature
that's
handled
by
a
future
flag.
So
when
we
turn
the
feature
Lag
on
it's
automatically
on
for
all
the
tests,
okay,
great
so
I.
Guess
that
means
that
if
I'm
CI
signal
and
I
want
to
understand
how
this
release
this
particular
feature
works,
I
should
be
going
and
looking
at
all
the
releases
blocking
tests
and
I
think.
A
A
A
So
when
Claire
talks
about
us
getting
a
little
noisier
about
enhancements,
that
was
sort
of
my
story
of
trying
to
do
that
for
her
one
of
them,
I
have
managed
to
get
a
follow
on
PR
as
a
result
of
that,
but
that's
the
level
of
questioning
you
are
empowered
to
ask.
If
you
look
at
this
and
don't
really
understand
what
the
cap
is
saying
for
your
role
feel
free
to
ask
questions.
A
E
I'll
say
I
did
the
opposite
approach
and
rather
than
deep
dive
into
one
I
did
all
of
them
at
a
really
high
level
and
the
testing
plans
for
a
lot
of
them
felt
to
me
on,
like
the
lighter
side
for
those
that
even
had
them.
So
yes,
anyone
who
has
follow-up
questions
or
if
things
don't
make
sense
and
you
need
help
getting
through
to
people,
feel
free
to
ping
me
or
let
me
know
if
it's
insufficient
feel
free
to
like
flag
it
on
the
spreadsheet,
as
well
as
that
risk.
G
Yep,
hello,
good
so
compared
to
last
week
we're
looking
at
significantly
more
turbulence.
I
would
say
the
good.
The
good
part
is
that
we
would
have
had
good
response
in
terms
of
open
issues,
so
the
failures
that
we
see
at
the
moment,
or
at
least
relatively
new-
we
don't
have
a
lot
of
ongoing
stuff
in
terms
of
numbers-
were
looking
at
through
filling
jobs
at
the
moment
in
master
blocking
five
in
release
master
upgrades
and
for
failing
jobs
in
the
1:14
blocking
dashboard,
some
of
them
are
appearing
across
dashboards,
so
it's
at
least.
G
G
The
other
thing
on
our
heads
is
going
back
to
going
back
to
enhancements
and
looking
at
test
buns
I
mentioned
last
week
that
we
went.
Can
we
had
a
first
run
through
a
couple
of
weeks
ago
and
we're
not
quite
defined
yet
or
were
described
as
like
to
be
decided
so
part
of
what
we're
gonna
do
this
week
is
go
back
and
figure
out.
You
know
given
given
what's
described
here
as
a
test
one
for
this
feature.
Are
we
confident
enough
that
we
could
say
yes,
this?
G
This
is
very
much
something
that
I'd
like
to
focus
on,
especially
is
willing
to
up
to
in
the
state.
But,
as
I
said,
priorities
for
this
week
was
to
clear
out
test
grades
and
to
get
comfortable
get
to
a
comfortable
state
with
testing
plans
for
enhancements
any
questions
or
opinions
around
any
better.
A
This
is
the
point
at
which
I
would
be
escalating
and
trying
to
go
chase
down
the
sink
and
I
would
expect
CI
signal
to
ask
the
release
team
to
increase
visibility
on
this
sort
of
thing.
Similarly,
I
go.
Take
a
look
at
the
release,
114
bored,
so
this
is
this-
is
now
fast-forward
it
sort
of
on
a
daily
basis,
which
actually
gives
us
something
really
cool
from
a
flight
perspective.
A
You
see
how
there's
that,
like
large
black
rectangle
up
there
as
I
hover
flips
between
like
one
black
rectangle
to
another,
this
is
basically
how
this
was.
The
kubernetes
kubernetes
released,
114
branch
sitting
at
the
same
commits
over
the
weekend
before
Honda's
fast
forwarded
it,
and
so
all
of
these
different
tests
that
are
all
failing
in
different
ways
are
all
failing
in
different
ways
against
the
exact
same
commits.
So
this
is
probably
a
hint
to
us
that
these
particular
tests
are
flaky.
A
The
release
branch
is
really
useful
for
this
sort
of
differentiation
between.
Is
it
a
flake
or
is
it
an
actual
failure
that
was
introduced
as
a
result
of
some
commit?
I
keep
scrolling
over
to
the
right
here.
You
know
all
right,
so
this
was
sort
of
when
the
board
was
created,
and
then
this
was
when
we
first
caught
the
very
first
beta.
So
you
can
see
we
have
some
data
about
flakiness.
A
It
looks
way
worse
on
the
cereal
board,
like
that's
a
whole
lot
of
red.
So
when
I
see
things
like
this
I
expect
that
she'd
be
able
to
get
a
look
for
issues
with
the
v1
14
milestone
that
have
kind
failing
tests
attached
to
them.
When
I
see
a
board
like
this
I
expect
that
I
should
be
able
to
get
a
look
for
issues
in
the
v1
14
milestone
that
have
kind
flake
attached
to
them.
A
G
So
the
Google
Doc
and
the
project
board
are
two
tools
that
we
experimented
with
mainly
to
be
able
to
coordinate
amongst
ourselves
and
who's.
Following
on
what
because
opening
bishop
for
a
failing
test
in
sort
of
the
step,
the
first
step
to
getting
it
resolved
at
the
time
it
you
know
it
has
followup
with
the
Sagan
slack
or
and
calls
and
whatnot,
so
that
helped
us
with
keeping
track
of
posting
lots
and
what
the
status
is
for
each
failure.
We
haven't
really
gone
ahead
with
the
project
for
it.
G
It
wasn't
very,
very
comfortable
so
for
us
to
do
the
things
that
we
wanted
to
do.
The
straight
sheep
was
a
bit
funkier,
but
indian
just
works
better
in
terms
of
having
a
snapshot
of
where
we're
at
as
a
team
filtering
going
and
getting
issues
for
KK
and
filtering
on
kind,
failing
tests
and
kind
of
like
and
milestones,
though
we
haven't
been
putting
them
until
now.
As.
C
G
A
The
fact
that
some
of
these
things
have
been
sitting
in
red
for
forever
you-
you
absolutely
have
the
authority
privilege
capability
to
escalate
and
and
get
us
to
go,
go
be
loud
and
chase
down
a
stick.
This
is
also
the
sort
of
thing
I
feel
like
the
issue.
Triage
team
can
help
you
out
with,
because
these
are
particularly
hot-button
issues.
G
Yeah
I,
don't
think
we
have
done
that.
We
have
had
up
levels
relations
in
the
last
few
weeks.
It's
tricky
with
the
jobs
I
guess
that
the
top
level
jobs
is
all
of
the
time.
The
reason
why
they
are
red
is
for
a
test
that
launched
a
different
sink
so
whether
while
the
job
itself
is
red
for
a
long
time,
the
individual
tests
that
caused
it
to
fail
at
each
run
are
different.
It
just
makes
things
a
little
blurry
er.
G
G
G
A
I
Your
name,
that's
good!
Thank
you!
Okay,
yeah
I'm,
just
the
ambassador,
so
nico
left
a
couple
of
notes.
He
started
to
grab
metrics
from
issue
sample
cast
that
are
opened
without
any
label
a
kind
level
to
stick
label
and
he
started
to
train
us
about
what
to
do
next,
because
it
looks
like
it's
gonna
be
hot
time
for
bug
triage
from
now.
I
A
Okay,
so
a
similar
comment,
/
opinion
for
the
triage
team
I
now
feel
like
there
should
be
significantly
more
issues
in
the
114
milestone,
because
we
are
now
at
burned
down.
I
would
rather
sort
of
err
on
the
side
of
having
too
much
in
the
114,
milestone
and
kicking
it
out.
As
we
discover
it's
not
pertinent
to
this
release,
rather
than
issues
sort
of
piecemeal,
sneaking
their
way
into
the
milestone
as
burndown
progresses
like
new
issues
that
we
uncover
through
the
course
of
debugging.
A
A
A
You
can
also
think
you
can
also
adjust
the
query,
so
it
looks
for
like
needs
priority
or
needs
kind,
and
even
like
literally
just
taking
a
best
guess
at
priority
is
a
start
and
then,
as
we
progress
through
burndown,
we'll
start
to
refine
those
priorities
and
figure
out
what
the
really
important
stuff
is
and
what
we
should
really
be.
Focusing
on
now
release
team.
A
This
is
just
my
perspective
as
somebody
who
starts
to
get
really
paranoid
as
we
enter
burn
down,
I'm
totally
happy
or
like
you're,
all
welcome
to
stand
up
and
say,
like
I'm
being
too
paranoid,
here's
what
we
should
do
instead
I'm
just
throwing
out
there
things
that
I've
seen
in
the
past
and
how
I
personally
have
operated
in
the
past.
But
there
are
29
of
you
so
I'm,
just
one
person
with
one
opinion.
But
what
are
the
other
28
of
you
think.
J
J
A
K
K
M
Everybody
first
off
I
want
to
apologize,
have
been
a
little
out-of-band.
Lately,
I've
been
traveling
more
than
I've,
been
on
the
ground
the
past
two
weeks.
So
it's
good
now
that
things
are
settling
down.
I'm
gonna
be
pretty
much
crunch
time
from
here
on
out.
We
have
our
placeholder
deadline
for
at
least
an
open
PR,
which
this
means
is.
If
there's
something
that
requires
Docs,
we
just
want
a
placeholder
could
be
a
blank
PR
saying:
hey
here's
where
our
Docs
exist.
M
Here's
where
we're
going
to
put
them,
preferably
it'd,
be
the
full
Docs
or
at
least
partial
Docs.
But
you
know,
placeholder
PR
would
be
acceptable
as
well.
So
I'm
gonna
be
working
with
my
shadows
to
make
sure
that
every
single
enhancement,
that's
in
scope,
has
a
placeholder
doc
if
it
needs
it
and
that's
gonna,
be
our
primary
focus
for
the
next.
M
Maybe
we
start
adding
in
the
shadows
for
that
enhancements
pressure
or
the
kubernetes
release
team
group
that
were
keying
off
of
as
part
of
the
release
cycle
that
we
kick
off
because,
right
now,
what
were
happening
or
having
happen
is
the
shadows
are
going
to
these
enhancements,
checking
on
them
submitting
comments,
but
they
aren't
able
to
update
the
enhancements
spreadsheet.
So
I
can't
get
metrics
to
report
back.
Here's
exactly
where
we
are
today
without
doubling
efforts.
I
guess
so
not
the
end
of
the
world,
but
that's
kind
of
where
we're
at
today.
I
think.
H
Hey
Jim
I,
just
added
a
release:
team
onboarding
document
to
the
cig,
release
repo.
We
should
for
sure
get
you
the
access
you
need,
but
can
we
perhaps
document
that
people
with
this
role
need
this
access
on
there?
Just
so
we
can
all.
You
know
just
document
all
of
the
access
for
all
of
the
roles
and
shadows
and
what-have-you
yeah.
A
Thank
you
yeah
in
in
general,
every
release
team
related
artifact
is
gated
by
that
group
and
if
you're
a
member
of
the
release
team
leader,
shadow
or
whatever
you
should
be
in
that
group,
it
used
to
be
way
more
complicated
than
that
and
I
have
tried
to
simplify
it
down
to
that
the
cycle.
So
that
may
be
why
we've
had
some
bumps
along
the
way,
so
I
apologize
for
that
I
see
one
outstanding
invite
to
that
group
right
now,
but
I'll
ping
you
about
offline,
make
sure
that
things
get
moving
for
you
awesome.
Thank
you.
B
So
I'm
gonna
share
my
screen
because
we
have
a
couple
things
to
talk
about
and
Aaron.
Please,
like
time
box
me
so
I,
don't
pulley
you
and
talk
for
20
minutes,
because
I
might,
with
this
desktop
to
thanks
I
guess.
Oh
no
I
wish
I
had
your
breath
of
being
able
to
talk
for
that
long.
Normally,
I
am
I
tend
to
leave
a
lot
out
you're.
The
exact
opposite.
I
appreciate
that
point
is
tangibly
right
now,
release
notes.
B
All
we're
really
working
on
is
updating
the
draft
weekly
and
then
we're
going
to
start
gathering
the
external
dependencies.
We
also
as
a
group
met
and
there's
a
reason
why
I'm
sharing
as
a
group,
we
were
talking
about
different
ways.
We
might
be
able
to
change
the
release,
notes
to
be
a
little
bit
more
functional
for
end
users
right
now.
If
you
look
at
release
notes
for
an
end
user,
it's
kind
of
confusing-
and
please
someone
tell
me
otherwise,
because
I
would
love
to
hear
other
opinions
right
now.
B
We
are
very
much
you
know,
kind
of
an
echo
chamber,
but
let's,
let's
take
a
look
at
113,
changelog,
urgent,
upgrade
notes
and
security
content.
That
totally
makes
sense,
known
issues
make
sense.
Deprecations
is
useful.
These
are
all
things
that
we
as
the
release
notes
team
will
have
to
pull
out
manually
and
that's
fine.
B
If
you've
really
read
a
lot
of
these
major
themes,
it
isn't
what's
going
in
to
a
release
its.
What
that
cig
may
have
done
over
the
course
of
that
release
cycle,
so
essentially
it's
them
giving
their
quarterly
community
update
in
our
release,
notes:
sig
big
data
during
the
113
release
cycles,
sig
big
data
focused
on
community
engagements
that
has
nothing
to
with
1:13
lets
I'm,
not
just
gonna
like
take
a
jab
at
that
sick
I'll,
take
a
jab
at
siggy.
Why
migration
to
the
newest
version
of
angular
is
still
under
active
development.
B
This
has
nothing
to
do
with
113.
This
is
literally
giving
an
update
for
SIG's.
So
why
are
we
collecting
themes
when
also
as
a
release
notes
team
collecting
these
themes
is
like
pulling
teeth
from
SIG's,
apparently
for
the
last
few
release
cycles,
we
have
had
to
hound
them
to
give
us
content
when
realistically
they're
rehashing
the
release,
notes
anyways
so
make
some
popcorn
I
would
love
to
hear
some
opinions.
I.
H
Would
love
I
mean
if
we
think
that
the
major
themes
aren't
really
adding
value
now
that
we're
tracking
enhancements
a
little
more
thoroughly?
One
thing
we
could
consider
doing
is
getting
rid
of
major
themes
and
just
having
kind
of
the
top
section
where
we
talk
about
things
that
are
actually
required
or
security
fixes
and
then
just
enumerate
the
enhancements
that
we
know
are
going
into
the
release
and
have
been
tracked
and
what-have-you
and
then
just
do
away
with
the
section.
I
love
that
yeah.
F
I
agree-
and
this
is
Natasha
I-
think
if
they
want
to
talk
about
major
themes
and
things
that
they've
been
working
on
again,
the
kubernetes
blog
is
a
really
great
spot.
We
were
I
just
talked
to
Kaitlyn
a
little
bit
during
this
call.
We
were
hot
and
heavy
on
blogs
and
now
we've
kind
of
slowed
down,
so
we
need
blogs
and
again
we
promote
this
on
social.
A
Ranted
about
this
at
length
for
the
one-port
113
retrospective
I,
don't
know
if
they're
still
in
there,
but
there
was
something
about
sig
IBM
cloud
in
the
release
notes
and
about
how
their
proprietary-
let's
see,
let's
find
IBM
cloud,
look
cool
yeah.
They
get
talked
about
how
they
released
something
in
chaos.
They
they
announced
a
new
version
of
Huber
Nettie's
in
their
kubernetes
service
that
is
not
allowed
in
a
file
called
change,
login
kubernetes
kubernetes.
That
has
nothing
to
do
with
the
code
in
kubernetes
kubernetes.
It.
B
A
A
What
was
the
most
important
thing,
and
so
they
used
their
brain
like
a
machine
learning
algorithm
to
kind
of
cluster
things
together
and
have
the
major
themes
come
out
of
that,
and
then
we
eventually
decided
that
was
too
much
work
for
one
single
person
to
do,
and
so
we
started
federating
or
mapping
all
of
that
out
to
the
stakes
and
asked
hey.
Could
you
please
decide
amongst
the
PRS
that
you
know
that
you
submitted,
which
ones
you
think,
are
most
important,
and
so
that
came
back
and
then
eventually
that
kind
of
turned
into
hey
six?
A
A
So
I
really
think
if
you
want
to
talk
about
this
in
the
technical
sense,
there's
a
map
and
then
there's
a
reduce,
and
we,
if
we
are
missing
the
reduced
step
and
I,
think
that
there
really
needs
to
be
like
a
single
or
a
very
select
few
people
who
contribute
their
editorial
voice
to
what
actually
are
the
important
major
themes
of
this
release
and
in
some
way,
that's
kind
of
the
process
that
Natasha
tried
to
kick
off.
As
we
started
talking
about.
B
The
blog
post,
great
and
yeah,
and
that
that
was
actually
like
I
feel
like
that
process
should
be
intertwined
with
this,
if
you're
going
to
have
up
to
not
necessarily
exactly
but
up
to
five
different
blog
posts.
Highlighting
things
in
this
release,
I
mean
you're
already
collecting
the
themes
and
you're
blogging
about
those
themes
yeah.
A
B
This
goes
back
to
thinking
about
end
users,
art
and,
actually,
let
me
pull
this
up.
I
will
read
this
out
loud
release
notes
give
our
users
a
heads
up
about
what
is
coming
when
they
install
or
upgrade
to
a
particular
release
of
kubernetes.
They
are
not
primarily
contributors.
Do
they
need
to
know
what
a
cig
is?
No.
A
M
Know,
speaking
from
a
consumer
of
kubernetes
and
consumer
of
the
release
notes
when
they're
coming
out,
you
know
I
really
do
like
keeping
up
with
what
all
the
other
SIG's
are
doing
by
definitely
just
point.
This
is
not
a
release
or
a
you
know,
component
of
the
release.
I
wonder
if
there's
a
compromise
here
where
all
the
SIG's
can
provide
all
this
information,
the
team
released
notes
or
maybe
in
collaboration
with
Doc's,
could
come
up
with
the
overlying.
M
The
underlying
themes
of
what's
really
truly
important,
but
then
also
maybe
as
part
of
cig
Doc's
or
the
release
notes
team.
They
also
create
the
blog
post
of
here's,
the
overall
themes
of
all
the
SIG's,
and
then
they
have
the
SIG's
review
of
them
and
the
reason
I
say
that
is
because
it's
unreasonable
to
think
every
single
sig
is
gonna
write,
a
single
blog
post
or
collaborate
with
each
other
I
see
the
sig
release
being
the
forcing
function
to
have
quarterly
updates
of
the
state
of
all
SIG's.
M
B
M
M
That's
a
great
point:
I
guess
what
I'm
looking
or
suggesting
is
formalizing
a
way
that
that
blog
is
assembled.
You
know
maybe
diskant
rebec's
and
maybe
that's
part
of
sig
release.
You
know
I,
see
kind
of
a
blurry
line
between
sig
ducts.
The
release,
notes
and
contributes
for
something
like
this
happy
to
help
out
happy
to
have
the
discussion.
I
would
hate
to
say:
let's
scrap
it,
just
get
the
core.
You
know:
here's
this
gonna
break
and
then
113
or
114.
Here's
just
gonna
be
fixed.
Here's.
What
changed!
M
B
B
Thinking
about
again,
this
is
kind
of
an
unwieldy
document
and
I
don't
know
if
everyone
actually
cares
about
every
Ingle
thing
in
here.
Wouldn't
it
be
nice
if
there
was
a
little
website
that
took
the
output
of
someone's
awesome
awesome,
go
util
that
generates
release,
notes
and
also
has
an
output
to
JSON.
Thank
you
Mike
and
then
lets
you
just
filter.
Whatever
you
want
to
see.
B
Already
you
know
going
off
of
github
labels,
we
can
see
everything
that
changed
with
cube
cuddle
and
now
this
was
just
a
weekend.
Project
and
I
still
have
a
lot
of
other
things,
I
want
to
add
to
it,
but
it
is
actually
showing
a
little
bit
of
promise,
and
this
whole
thing
on
the
left
is
completely
auto-generated
from
all
the
categories
that
Mike's
utility
puts
into
JSON.
I.
Think
that
is
a
minute
come
out.
Yeah.
A
That
looks
really
neat
I.
Think
there's
there's
got
to
be
some
kind
of
compromise
between
a
changelog,
that's
literally
just
the
pull
request
title
for
every
pull,
request
and
themes.
Maybe
this
helps
us
explore
again
there.
Okay,
so
I'm
a
totally
unrelated
note:
let's
go
over
to
comms
and
hear
from
Natasha.
F
F
B
F
A
So,
in
terms
of
the
place
to
coordinate,
do
you
have
links
available
to
the
Google
Docs
I'm,
trying
to
dig
through
the
release
notes?
I
can
see
the
the
release
marketing
plan
I
found
that
but
I
didn't
find
the
one
where
we
had
sort
of
the
release,
themes
and
stuff
that
we
could
maybe
brainstorm
around.
Yes,.
F
Definitely
so
all
all
put
those
in
the
meeting
notes
right
now
and
I'll
also
put
in
the
key
messages
document
the
one
that
we're
going
to
need
to
fill
out
for
media
interviews
as
well,
all
I'll
link
all
that
in
there
and
then
just
to
beat
a
dead
horse
if
there
is
something
that
is
not
going
to
make
it
into
this
release,
but
will
be
ready
before
the
next
release.
A
blog
post
on
kubernetes
at
I/o
would
be
greatly
appreciated.
F
A
N
If
anybody
of
you
ever
feels
that
we
should
wait
with
a
fall
fast
forward
to
get
some
more
signal,
ping
me
totally
fine,
no
problem
regarding
the
caps
for
packaging
package
creation
and
package
releases
where's
sake
release,
namely
me
mostly
and
C.
Cluster
lifecycle
is
involved.
It
was
decided
to
not
bring
them
in
for
114.
We
didn't
get
to
a
consensus
on
what
what
it
actually
should
be.
N
However,
it's
being
worked
on
and
should
come
in
with
the
next
release,
then
so
we
were
continuously
working
on
that
and
hopefully
have
something
then
to
pull
in
early,
hopefully
early
for
the
115
release.
What
else
tomorrow
there
is
another
cut.
We
are
cutting
beta
1
tomorrow
with
one
of
my
shadows
and
well
yeah.
You
see
a
couple
of
metrics
for
the
b20
any
questions.
A
A
N
C
O
Question
from
me,
Lou,
Hamer,
Erin.
So
do
these
kind
of
use
the
cloud
provider
resources
like
okay
cubic
units
anywhere
you
used
to
do
no
okay,
this
logo.
It
basically
creates
a
cursor
inside
the
correct.
So
it's
not
one
for
one
replacement
right
because
the
earlier
given
it
is
anywhere
jobs
used
to
use
the
entry
providers
to
do
volumes
and
stuff.
C
O
A
O
C
O
A
My
question
is:
do
the
exist?
I
thought
that
the
existing
pile
of
bash
that
stands
up
the
majority
of
our
clusters
for
release
jobs
does
in
fact
set
the
cloud
provider,
so
the
functionality
is
being
exercised
there.
What
dropping
this
particular
communities
anywhere
job
would
do
is,
in
the
matrix
of
like
a
cluster,
stood
up
with
cuvee
DM.
That
also
happens
to
use
the
GCE
cluster
provider
right.
That's
what
we
would
be
dropping
correct.
C
Mr.
Cobra,
the
server
is
special,
but
the
problem
here
is
that
we
are
not
testing
GC.
We
are
testing
the
deployer
and
you
know
we
already
have
coverage
with
using
cube
up
to
bring
up
coasters
in
the
GC
infrastructure.
So
what
happens?
Is
the
big
kubernetes
anywhere?
We
are
testing
the
communities
anywhere
deployer
and
not
the
core
provider
I.