►
Description
A
A
So
I
dropped
a
link
to
the
meeting
minutes
in
in
chat,
and
since
we
are
recording
right
now,
I'm
gonna
go
ahead
and
remind
everybody
that
you
are
on
a
publicly
recorded
meeting
for
sorry.
Let
me
start
over
hi.
This
is
the
114
kubernetes
release
team
meeting
for
V
114.
This
is
week.
Two
today
is
Monday
January
14th,
because
this
meeting
is
being
publicly
recorded
and
posted,
we're
all
going
to
hold
ourselves
to
the
kubernetes
code
of
conduct,
which
roughly
boils
down
to
please
don't
be
a
jerk.
This
will
be
posted
to
YouTube
later.
So.
A
A
What
I
had
proposed
last
week
was
that
we
use
a
template
that
I
can
just
copy
paste
and
y'all
can
fill
out
and
part
of
that
template
would
include,
like
metrics,
that
you
feel
best
represent
the
state
of
the
world
from
you
roles
perspectives.
So
we
can
sort
of
keep
track
of
things
moving
up
or
things
moving
down.
Whichever
direction
is
most
appropriate
for
your
role
on
a
week-by-week
basis,
so
I
had
put
in
some
things
that
were
my
suggestion.
A
A
A
A
Let's
take
a
look
at
the
meeting
minutes
except,
etc.
The
schedule
roughly
oils
down
to
this.
So
we
began
the
release
week.
One
was
last
week
week:
four
is
going
to
be
enhancements.
Freeze
week,
nine
is
going
to
be
code
freeze
and
week.
Twelve
is
when
we're
going
to
release
kubernetes
140
the
two
things
that
we're
going
to
do
differently.
This
release
that
we
know
of
right
now
is
that
there
will
be
no
code
slush
and
that
all
proposed
enhancements
for
this
release
must
have
an
Associated
cap
I'll.
A
Let
Claire
speak
to
more
of
this,
but
we're
trying
to
go
around
to
syncs
this
week.
As
we
start
collecting
enhancement,
work
and
give
sakes
a
heads
up
about
this.
It.
The
discussion,
let's
say
architecture
was
not
a
quick,
concise
meet
a
discussion
that
came
to
closure,
but
instead
remind
us
reminded
us
all
that
this
is
sort
of
going
to
be
an
iterative
and
ongoing
process
as
we
look
to
sort
of
refine
the
formalism
of
enhancements
and
what
criteria
be
used
for
things
living
in
the
release.
A
more
detailed
timeline
is
listed
here.
A
A
So
another
big
milestone,
I'm,
seeing
now
as
I
look
at
this
is
that
we,
you
need
to
cut
an
alpha
of
114
this
week
and
I
had
it
listed
as
Tuesday,
since
that's
roughly
speaking,
but
the
most
useful
day
for
any
of
these
milestones.
So
I'd
love
to
talk
about
that
when
we
get
get
to
the
branch
manager
section,
because
I'm
I
actually
don't
really
know
what
credentials
and
criteria
need
to
be
set
up
in
order
to
make
that
happen,
enhancements
freeze
is
the
big
thing.
A
That's
on
my
mind,
any
of
the
big
release
transitions
I
did
as
links,
so
you
can
go
down
below
and
see
like
what
enhancements.
Freeze
means
what
burn
down
means,
what
code
freeze
means
and
what
code
thaw
means
and
I
tried
to
document
processes
that
might
be
of
interest
to
people
who
are
consuming
for
release
as
a
whole.
I
might
be
wrong
on
these
processes.
If
this
is
something
that
involves
your
role
again,
please
feel
free
to
update
it.
A
A
A
Have
it
linked
in
the
meeting
notes,
I
plan
on
going
through
and
purging
membership
of
this
Google
group,
so
that
it
only
lines
up
with
the
114
release
team
members,
the
patch
release
team
and
the
cig
release
leads,
and
that
way
we
can
use
this
Google
Group
as
the
one
single
place
for
Ackles
for
who
should
have.
You
know,
write
or
admin
access
to
certain
documents.
It's
a
lot
easier
than
having
to
track
people
individually
as
I
went
through
and
created
things
for
than
114
release.
A
I
found
that
there
just
there
were
random
names
all
over
the
place.
It's
also
going
to
be
more
convenient
to
use
this
for
scheduling,
release
team
meetings
rather
than
using
the
burndown
meeting
group.
The
burndown
meeting
group
has
like
a
hundred
and
fifty
something
people
on
it.
It's
nuts,
we
don't
need
that
many
people
getting
invites
for
this
weekly
meeting.
Just
yet
and
then
the
second
thing
is
Stephen
said:
Kate's
114
contacts
is
the
short
link
to
that
spreadsheet.
A
B
B
B
Yeah
so
I
have
so
once
I
have
everyone's
contacts,
then
I'll
actually
be
able
to
use
the
kubernetes
release
team
group
to
give
you
access
to
another
spreadsheet
that
will
include
links
and
contact
information
for
people
filled
out
survey
from
there.
Then
you
can
reach
out
to
your
perspective,
shadows
and
go
from
there.
A
Cool
yeah
I
totally
leave
discretion
of
shadow
selection
up
to
each
and
every
person.
He
needs
to
select
shadows
I'm
here
as
an
escalation
point
of
last
resort.
If
you
need
help
or
have
questions
other
than
that,
I,
don't
know
that
I
have
a
lot
of
additional
things
to
say,
I
might
think
of
some
topics
as
we
go
along,
in
which
case
I'll
add
them
to
the
bottom
of
this
week's
agenda.
A
Where
I
have
an
open
discussion
topic
item,
the
last
thing
I
will
say,
is
I,
went
through
and
created
copies
of
all
of
the
previous
releases
tracking
artifacts
of
things
like
the
enhancements
tracking
sheet
or
the
CI
signal
report
with
bug,
triage
tracking
sheet
I,
just
copied
them
and
I
didn't
change
the
content
at
all.
Please
also
don't
take
this
as
a
mandate
that
you
follow
the
previous
format
in
any
way,
shape
or
form.
A
A
E
So
there's
not
too
much
happening.
There
are
a
few
failing
start
slaking
jobs
on
master.
Some
of
them
have
been
a
bit
on
and
off
during
holiday,
so
I'll
just
follow
up
on
these
other
things
a
little
bit
too
enthusiastic
and
send
out
questions
to
folks
that
volunteered
to
shadow
CI
signal
before
the
question
at
result.
Luckily,
there
was
quite
a
bit
of
overlap,
but
I
just
had
to
go
back
to
them
and
ask
them
to
fill
in
the
questionnaire
and
then
in
case
that's
interesting.
E
A
Oh,
thank
you
very
much.
Yeah
and
I
appreciate
you
capturing
all
of
that.
Maria
you
and
I
can
think
up.
Offline
I
know,
I
bring
up
the
bunch
and
I
still
haven't
found
the
Google
Doc,
where
you
could
take
copious.
That's
on
that
I
did
try
to
gather
up
everything
that
seemed
to
talk
about
deep,
linking
kubernetes
tests
and
I
mentioned
it
as
an
example
of
a
good
use
of
a
project
work
during
the
community
meeting,
which
inspired
a
number
of
other
people
to
start
project
towards
yay
project.
A
A
One
one
random
thought
I
had
on
on
this
roll
is,
it
kind
of
seems
like
it's
not
really
about
just
triaging
bugs
anymore.
If,
when
I
went
through
and
read
the
description
of
the
roll,
it
sounded
an
awful
lot
like
it
was
more
like
shepherding
issues
and
PRS
in
in
general.
I,
don't
know
if
anybody
else
has
a
lot
from
it.
Yeah.
B
So
we
had
a
we
had
a
discussion,
I
think
in
112
about
considering
adding
an
issue
in
PR
triaged
person
and
then
decided
that
it
could
kind
of
be
serviced
by
the
it
could
be.
The
issue
issue
you
PR
bug,
triage
person,
so
I
think
we
just
kept
in
a
spoke
triage,
but
that's
kind
of
essentially
what
the
role
means.
Maybe
we
should
clarify.
A
A
So
if
you
are
a
community
member
who
may
not
necessarily
have
time
to
dedicate
to
the
release
team
or
for
whatever
reason
you
don't
show
up
as
a
shadow,
it
is
totally
a
okay
to
help
out
by
figuring
out
why
certain
PRS
or
issues
are
blocked
escalate.
Accordingly,
as
far
as
the
milestone
being
consistently
assigned
to
issues
in
PRS
I
think
there's
an
open
discussion
on
what
the
most
appropriate
etiquette
is.
I
personally
and
I
really
wish
I
could
point
you
to
a
document,
but
I
don't
have
any
links.
A
Offhand
I
know
that
we
really
don't
affectively
care
about
the
milestone
too
much
until
it
comes
to
burn
down,
which
is
going
to
be
a
week
before
code
freeze
because,
as
the
name
implies,
we
want
to
like
start
with
a
backlog
of
work
and
then
burn
it
down
right.
So
that
said,
I
think
it's
useful
from
an
issue
perspective
to
be
able
to
use
the
milestone
to
kind
of
predict
how
much
work
is
coming
at
us.
Maybe
it's
less
useful
for
it
to
be
applied
to
feed
ours.
A
B
A
Cool
I
have
an
outstanding
PR,
which
I
think
updates
the
testing
for
book
tournament.
The
concept
of
code
slush
and
I
also
had
a
PR
out
the
community,
because
code
slush
was
mentioned
there
to
enter
Craig's
question
about.
Why
not
use
a
project
board
for
keps
instead
of
a
query,
I'm
kind
of
going
to
defer
to
how
my
nan
Smith's
lead
Claire
would
like
to
best
track
things
in
an
ongoing
manner,
but
I
will
say
that
project
boards
currently
aren't
automatically
populated.
So
the
query
is
something
that
I
can
like.
I
can
run.
A
B
C
A
A
F
C
Everybody
I'm
Jim
angel,
the
Ducks
lead
for
114,
so
this
should
be
a
pretty
quick
update,
still
just
waiting
to
confirm
the
shadows,
get
access
to
the
survey
and
get
everything
lined
up
there.
There
is
the
dev
114
branch
open
already
for
a
PRS
to
be
submitted
to
that's
one
thing:
I
did
notice,
Erin
on
the
release,
notes
or
that
initial
release
team
documented
had
a
little
snippet
about
the
docs.
We
previously
called
the
branch
release,
whatever
the
version
was
now.
C
We
change
it
to
dev,
so
I'll
submit
a
PR
later
to
fix
that
in
those
notes,
and
also
in
the
the
handbook
for
docs,
which
I've
been
working
with
us
even
on
over
the
past
couple
days
here
as
far
as
useful
metrics
I
think
we
can
track
once
we
know
what
the
enhancements
are.
The
capsule
we're
looking
at
looking
at,
which
ones
need
ducts
and
then
whether
or
not
those
Doc's
are
present
I
think
tracking.
C
A
Okay,
I
agree,
and
one
thing
I
noticed
after
I
put
the
draft
of
the
release.
Schedule
out
was
I,
don't
think
I
actually
have
a
Docs
finalized
call
out
literally
schedule.
Let
me
see
okay
I
know.
If
not
I
can
happily
add
that.
Okay,
the
the
thinking
was
just
suggest
that
code
freeze
means
freeze
for
everything,
Docs
PRS
and
tests,
the
idea
being
in
the
past.
We've
talked
about
like
get
an
initial
PR
open
by
some
date.
That's
later
than
code,
freeze
I'd
rather
have
an
initial
PR
open
that
represents
stocks
by
countries.
A
G
H
Hello,
everybody
yeah
release
branch
management.
I
can
try
to
cut
the
first
Oliver
to
the
alpha-1
tomorrow
my
morning,
if
I
don't
expect
any
issues,
but
if
I
run
into
issues
like
not
having
access
to
certain
things,
I
can
then
I
guess
poke
people,
but
I,
guess
I!
Guess
it's
gonna
be
fine.
I
already
cut
stuff
in
the
last
release.
H
D
A
Okay
and
and
your
plan
sounds
great
to
me-
I'm
a
sync
with
you
offline
about
whether
we
want
to
give
you
an
issue
or
something
just
to
track
to
log
like
what
did
you
do?
What
are
the
things
you
noticed
that
weren't
quite
working
for
you?
How
did
that
deviate
from
the
playbook
as
written
and
stuff
like
that.
H
A
A
So
I
see
something
here
about
Dave
having
a
conflict
at
this
time
with
respect
to
release
notes,
if
that's
the
case,
I
really
appreciate
a
chat
about
this
in
slack,
so
we
can
figure
out
the
right
way
to
get
really
ensure
that
release
notes
has
a
voice
here
at
this
meeting,
I
believe
starting
next
week.
Historically,
release
notes
has
created
some
sort
of
draft
or
artifact.
A
B
So
so
we
were
also
having
the
discussion
about
whether
this
should
even
be
the
time
for
the
release
meeting.
So
I'm
not
sure
if
we
discuss
that,
like
with
the
team
itself
and
I,
don't
like
I,
don't
personally
have
a
preference,
but
if
it's
a
time
that
is
not
amenable
for
the
entire
team
or
some
people
who
are
in
other
time
zones,
maybe
it's
anyway.
It's
good
to
look
at
assessing
changing
that.
A
A
H
A
Okay,
that
sounds
ideal
to
me.
I
think
the
best
way
to
track
this
would
be
to
open
an
issue
milestone
it
open
an
issue
in
the
cig
release,
repo
milestone,
it
is
114,
so
we
know
it's
something.
This
release
team
is
keeping
track
of,
and
then
we
can
discuss
the
plan
to
send
out
a
doodle
once
all
shadow
searches
all
take.
B
A
A
Well
so
another
thing
to
notice
is
this:
took
about
30
minutes,
which
is
awesome.
30
minutes
is
usually
the
cadence
I
would
expect
from
a
release.
That's
running
smoothly,
where
everybody
generally
knows
their
thing.
It
probably
will
balloon
up
to
an
hour
here
or
there,
but
this
is
roughly
what
I
hope
that
burned
out
meetings
look
like
and
if
nobody
has
anything
else,
we
can
have
30
minutes
of
our
lives
back.