►
Description
Kubernetes 1.18 Release Team Meeting Burn down for 3/2/2020
A
A
Conduct
which
essentially
boils
down
to
please
be
nice
to
each
other
at
all
times
before
we
get
into
the
meeting.
If
anyone
will
be
kind
enough
to
serve
us
and
note-taker
for
this
session,
please
put
please
put
your
name
down
in
the
notes
like
always
before,
like
always
at
the
end
of
this
meeting,
I'll
make
sure
to
go
through
the
document
again.
A
Curated
make
sure
that
all
the
information
that
anyone
might
need
to
do
their
job
is
here
in
some
way
in
one
way
or
another,
so
we
can
have
a
remote
first,
medium
for
community
pay
for
communication,
and
with
that
I'll
end,
my
public
service
announcements
and
leave
pass
it
on
to
enhancements
Kirsten.
Are
you
on.
C
C
Some
of
them
are
on
track
and
some
of
them
aren't
so
we're
pretty
much
alert
watching
all
of
the
PRS
they're
going
in
and
updating
the
tracking
sheet
as
quickly
as
we
can
we
do
have.
We
do
have
two
enhancements
that
were
removed
for
missing
the
Docs
placeholder
deadline,
one
of
them
one
of
them
basically
had
a
little
bit
of
a
problem
because
they
didn't
respond
by
the
by
the
docs
deadline.
So
we
dropped
them
and
then
they
had
said
that
they
don't
need
other
Docs,
because
they're
covered
by
you
know
another
set
of
Doc's.
C
So
we're
going
to
add
that
one
back
and
then
there's
also
like
an
interesting
question
that
we've
been
talking
about
internally
on
the
enhancements
team,
where
there
are
some
times
you
come
across
enhancements
that
don't
really
seem
to
fit
the
true
nice
crew
Nettie's
enhancements.
But
they
want
to
be
tracked,
like,
for
example,
there's
enhancement
14:32,
which
is
basically
not
in
the
repo,
and
they
also
indicated
that
they
wouldn't.
C
Be
following
all
of
the
deadlines
for
kubernetes
enhancements,
but
you
know
when
we
removed
the
when
we
remove
them
from
the
milestone
and
tracking,
because
to
us
it
didn't
necessarily
seem
like
this
was
a
proper
crew
noise
enhancement,
since
it's
out
of
repo
anyway,
they've
wanted
to
be
a
part
of
it.
So
I
think
one
of
the
questions
that
we're.
Having
is
what
do
we
do
with
these
non
kaykai
enhancements
that
want
to
be
tracked.
Do
we
still
track
them
just
because
the
person
wants
to
track
them?
Is
there
you
know
going
forward?
C
A
D
C
I
think
that's
exactly
our
question
because
on
one
hand,
if
you
want
to
be
tracked,
then
we're
kind
of
gonna
hold
you
to
all
of
the
deadlines
and
mechanics
that
a
regular
enhancement
is
held
to
you
but
like
if
you
want
to
be
tracked,
but
then
not
fully
participate
in
that.
But
it
also
makes
it
a
little
harder
for
enhancement
people
to
keep
track
of
them,
because
it's
like
then
you'll
have
all
of
these
exceptions,
which
perhaps
can
be
on
a
different
page
of
the
spreadsheet.
D
So
if
you
want
to
be
tracked-
and
you
want
to
be
part
of
the
release-
train,
meaning
you
can
have
access
to
the
blogs
and
be
part
of
the
release
notes,
then
you
have
to
go
all
in
with
the
docs
and
the
code
freeze
and
everything
that
comes
with
it.
Otherwise,
you're,
not
part
of
that
process.
I
guess
would
be
my
stance.
A
In
general,
in
general,
a
a
an
again
dissociate,
this
wasn't
happening
happening.
Wait
given
that
I'm
just
saying
this
at
this
very
moment,
but
the
that
also
does
make
sense
a
super
random
question.
If
the
core
part,
if
there
were
if
this
means
this
was
strictly
a
kubernetes
enhancement,
are
we
right
now
meeting
all
the
deadlines?
Aprs
a
called
threesome,
the
white.
C
Well,
they
said
that
their
docks
would
be
in
their
own
dogs
repo,
so
there
wouldn't
really
be
kubernetes
docks
and
then
someone
also
explicitly
said
that
they
don't
really
need
to
file
and
follow
the
timeline.
So
while
there's
a
PR
like
I,
don't
really
know
if
they're
going
to
meet
the
deadline
or
not,
the
docks
won't
be
in
the
kubernetes
repo.
E
I
think
I
think
we
should
leave
them
for
now
and
see
where
they
are
with
code
freeze,
they
I
think
have
work
going
on
out
of
tree
and
we
can
track
that
stuff
down
and
figure
it
out,
but
I
think
we
should
make
more
clarity
around
this
for
the
next
release.
We
should
definitely
add
this
to
the
retrospective
and
figure
out
a
do
we.
What
do
we
want
to
do
in
terms
of
like
the
handbook
and
explicitly
saying
how
we
want
to
handle
these,
but
also
maybe
feed
into
the
kind
of
ongoing
work?
A
A
E
778,
so
basically,
what
happened
with
770
as
Kirsten
mentioned?
Is
they
never
responded
by
the
cutoff
so
beneath
it?
I
dropped
them
from
the
release
today
and
then
they
said,
oh
wait.
This
is
covered
by
the
docks
for
603
they're
buying
the
same
feature
flag.
We
don't
need
to
have
separate
PRS
for
this.
Here's
the
link
to
the
website
dirt
to
the
pr2
k,
slash
website
so
like
then
that
pier
has
been
open
before
the
deadline,
so
we're
adding
them
back.
E
A
F
You
know
everyone
happy
muddy,
okay,
so
our
current
some
I
can
say,
yellow
but
a
little
protesters
to
go
green
this
week.
So,
let's
start
a
muscle,
plucking,
the
two
jobs
are
failing
still
oscillator
scripts
to
deal
stable.
This
is
this
is
failing
us
well
previous
group
in
the
previous
week,
and
we
don't
have
any
response
from
CLI
team
as
well.
I
ping
them
earlier
today
and
I
would
try
to
push
them
to
fit
it,
because
this
is
critical
and
this
equals
master
aha
features.
F
F
There
is
potential
fix
in
for
both
of
them
because
they
have
both
fighting
for
the
same
reason,
and
only
there
to
see
witness
2019
master
is
failing
because
of
another
six.
A
liar
are
helping
them
as
well
earlier
today,
but
no
response
I'll
try
to
push
them
as
well
build
pockets
dips.
Is
this
is
still
failing,
but
we
changed
the
priority
to
boron
soon.
I
left
the
common.
This
is
the
same.
Exactly
like
previous
week.
F
F
They
are
actually
the
same
from
prison
as
well,
but
I
can
just
that
some
more
details.
There
are
in
the
pool,
kubernetes
c2e2
see.
There
are
two
six
North
cases
that
are
that
are
similar
to
beef
leg
and
those
are
rather
investigation,
and
there
is
a
one
six-year
line
flight
that
this
is
actually
the
fix
actually
is
merged,
and
that
job
seems
that
it's
not
good
into
flame.
So
I'm
going
to
keep
wondering
and
if
the
table
is
okay,
I
would
close
this
or
about
it.
F
Cuckoo
birds
verify
another
flight,
so
subtle
diversification
and
the
cube
market
we
DC
big,
which
is
like,
should
be
fixed
one
of
the
P
ours
which
right
now
each
smells
but
I'm
going
to
keep
observing
this
job
as
well,
and
make
sure
that
it's
not
like
in
close
this
as
well
and
finally,
I
put
another
issue
down
here.
The
Miss
klegg,
like
the
desk,
which
there
are
many
many
different
test
cases
that
are,
are
free
and
we
keep
tracking
them.
You
know
this
issue.
This
is
something
the
situation
as
well.
Any
questions.
F
F
A
Sounds
that's
good
to
know
and
thank
you
for
all
the
work.
Does
anyone
have
any
more
comments,
questions
so?
Yes,
tunes
for
sky
signal
very
month,
twice
again:
Thank
You
Nico
and
a
quick
note,
because
I
just
had
this
on
the
car
on
the
comments
there,
there
is
a
link
to
the
retrospective
at
the
top
of
a
at
the
top
of
the
page.
Now,
thank
you
for
a
thank
you
for
pointing
that
out.
Yeah
next
Bach
treeoche
Bucky.
G
Hello
good
morning,
good
evening,
good
afternoon,
in
between
that
bug,
triage
is
currently
red.
We
are
drawing
down
so
I
hope
that
will
change
this
week
for
open
non-test
flakes.
We
are
down
12
to
13
for
priority
critical,
we're
remaining
steady
at
two
for
a
priority
important
soon,
weird
down.
We
are
at
thigh,
which
is
down
seven
for
open,
kkap
ours.
We
are
at
28,
which
is
down
six
priority,
critical,
urgent
PRS.
We
are
zero
and
that's
down
one
priority.
Important
soon
is
18.
G
B
Hello,
everyone
Sarita
here
overall
status
of
dog
screen.
We
had
like
three
announcement
that
didn't
help
placeholder
PRS
and
we
got
we
heard
back
from
two
and
that's
been
updated
and
track.
Like
Christy
mentioned,
the
one
that
didn't
have
the
face
of
PR
has
been
removed
from
the
milestone.
The
team
is
working
towards
the
next
milestone.
That
is
getting
all
the
dogs
ready
for
review
that
that's
it
from
the
dogs
team.
Any
questions
you.
A
It's
all
good,
hey
one,
quick
question
that
comes
to
mind:
a
strict,
not
not
super
a
release
related,
but
just
out
of
curiosity
I
saw
in
black
the
Jim
Jim
angel
from
sick
dogs
is
working
with
the
purely
with
the
release.
Engineering
people
on
the
K
rail
fast
forwarding
for
dogs.
How
plugged
in
is
a
tox
team
with
that
work.
B
A
H
I
Where
I
would
say
green
at
this
point,
we're
kind
of
in
the
same
space,
where
we're
still
waiting
for
some
updates
from
SIG's,
but
it
is
just
one
sig
that
we're
waiting
for
now
and
we
are
going
to
the
enhancements
list
to
see
which
enhancements
are
relevant
to
that
specific
sig.
So,
like
I
said,
there's
just
one
birthday
we're
trying
to
get
updates
from
and
we
will
vote
on
topics
this
week
and
once
we
do
that
we
will.
I
A
They
are
not
very
responsive,
so
in
some
cases
series
it
takes
time
to
get
here
to
get
response
in
some
other
cases,
and
we
didn't,
we
didn't
get
a
response,
and
one
of
the
one
of
the
thing
in
please
correct
me
turn
if
I'm,
if
I'm
sorry,
you
from
line
or
saying
or
telling
the
story
have
a
half
way,
but
one
of
the
a
one
of
the
I
guess
things
and
had
been
done
a
little
bit
differently
stuff
for
toast,
except
on
a
reply.
They
comic
the
communications
team.
A
It
just
starts
with
looking
at
the
enhancement
sheet
and
looking
at
looking
at
the
work
that
is
being
tracked
for
the
given
seek
so
every
single
discussion
and
issue
that
can
a
that
came
around.
That.
Could
you,
please
add
a
a
add,
a
note
on
it
on
the
retrospective.
Oh
sure,
yes,
oh
well,
please
anything
anything
that
you
think's
interesting
worthwhile
or
just
a
good
to
know
a
will
be
super
useful.
Well.
I
J
Hello,
my
name
is
Carlos
and
part
of
the
release
branch
team
and
they
start
to
for
this
week
is
we
are
doing
the
branch
fast
forward
daily,
almost
daily,
that's
one
two
days,
I
forgot,
but
then
I
did
the
next
day
and
we
have
code
freeze
scheduled
for
this
Thursday,
but
also
I.
Think
George
will
mention
again
as
well
in
the
end
of
the
meeting
and
so
far
we
are
Rick
as
well.
J
A
A
A
D
Thanks
George
hello
release,
team
emeritus
advisor
here
lucky
one
item
for
me
on
the
update.
So
there
is
the
mid
release
a
shadow
survey
I'm
closing
that
up
at
the
end
of
this
week,
which
is
March
6.
Currently
we
have
a
34
complete
34
percent
completion
rate
across
all
shadows.
If
you're
a
shadow,
we
would
love.
Love,
love
you
to
do
this
survey
and
it
means
you
will
not
have
to
do
another
meeting.
D
If
you
did
this
survey,
so
we're
trying
to
gather
feedback
on
how
useful
people
think
the
shadow
program
is-
and
this
helps
this
guide
changes
we
want
to
make
to
the
shadow
program.
So
it's
a
very
short
survey.
It
should
take
you
no
more
than
five
minutes
to
complete,
but
the
feedback
is
really
valuable
and
we
are
looking
at
it
and
we
will
take
it
into
account
for
subsequent
release
teams.
So
I
would
really
appreciate
it.
Everybody
could
get
that
up
and
running
and
the
leads
that
are
on
the
call.
D
A
A
Thank
you
so
much
lucky
and
going
back
to
my
update
so
couple
a
house
a
couple
to
a
couple
things
that
I
have
to
mention:
don't
freeze
a
we
had
that
set
up
for
this,
for
this
Thursday
so
expect
the
rest
of
the
rest
of
the
week
to
be
a
bunch
of
messages
about
the
PR
kit
about
the
day
about
the
typo.
That's
probably
gonna
be
a
huge
backup,
and
hopefully
six
get
older
peers
at
least
were
always
going
to
be
much
other
than
that.
The
docks
deadlines,
be
ours,
ready
for
review.
A
That's
going
to
be
in
a
that's,
that's
going
to
be
next
Monday
and
the
next
upcoming
milestone
is
on
next
Tuesday.
We
are
planning
to
have
a
118
beta
to
read
a
release
and
Toto
salute
really
big
event,
so
we
that
we
have
to
the
end
that
we
have
to
keep
in
mind
other
than
that,
since
we
are
getting
to
ten
last
to
last
stretch
of
the
day
of
the
release.
A
I
want
to
take
this
time
to
I
I
met
Mitch
mentioned
a
near
the
beginning
of
the
code,
but
I
want
to
be
a
what
about
sailor.
Again,
if
there
is
anything
interesting
that
you
seen
thus
far
to
a
trial
date
release
cycle,
if
there
is
anything
that
you
learned
anything,
the
guitar
was
most
funny
in
any
way
in
any
way
whatsoever.
Please
add
it
to
the
to
the
release
retrospective.
There
is
a
link
for
the
reduce
retrospective
in
the
118
readme
in
the
cigarette
list
in
the
sequence
repo.
A
A
A
Okay,
moving
on
to
the
next
topic,
a
open
discussion
and,
as
I
just
mentioned,
there's
another
link
to
the
to
the
retro.
A
really
please
drop
anything
that
you
think
might
be
worthwhile
to
share
with
future
generations
or
secretly
securities
contributors,
but
other
than
that.
Is
there
anything
that
anyone
wants
to
bring
up
for
open
discussion.
A
A
Okay,
so
can
everyone
see
my
screen,
yeah?
Okay,
sweet!
Thank
you.
Are
we
moving
on
to
the
dashboard?
Let
me
refresh
this
thing
and
let's
start
with
reviewing
progress.
So,
first
off
we
have
a
couple
peers
that
I
submitted
last
week
ensure
the
release
team
leader
organizes
the
retrospective
and
document
released
email,
please,
membership
criteria,
I
believe
there
are
a
couple,
a
couple
comments
that
I
still
had
to
go
through
good.
If
anyone
is
interested
in
reviewing,
they,
please
feel
free
to
drop
by
in
progress.
A
The
last
comment
was
by
myself
asking
people
to
pay
to
take
a
look
at
this
and
again,
please
do
the,
even
if,
even
if
you
think
that
there
is
no
benefit
whatsoever
to
a
tracking
spreadsheet,
yeah,
I
guess:
okay,
I
guess
a
comment
is
useful.
It's
useful
signal
to
see
you
area
so
might
benefit
from
this
proposal.
Hello,
hello
process,
lucky
any
updates.
A
But
so
does
off
like
it's
still
in
progress,
let's
see
next
up
tracking
okay,
so
next
one
is
track.
Enhancement
slip
across
multiple
releases
were
still
in
118,
so
we
are
in
the
process
of
acquired
data.
Next,
stop
talking
main
reason
for
inclusion
of
release
blocking
jobs,
and
this
is
still
at
work.
This
is
still
a
work
in
progress
and
I
have
a
document
open
for
it,
and
let
me
just
double
check
that
there
are
no
new
work
comments
and
indeed,
when
your
comments
so
working
produce,
add
kubernetes
really
support
period
cap.
A
A
For
the
most
part,
we
still
have
to
do
a
a
good
chunk
of
cleanup
of
these
issues
and
open
up
more
issues
and
clean
up
the
existing
ones,
hoping
to
spend
a
good
portion
of
this
week
working
on
it
ensure
that
released
in
bit
handbook
in
concern
for
adding
the
release
retrospective
to
the
release,
calendar
and
document
the
kubernetes
released
in
google
groups
membership
criteria.
These
two
issues
are
related
to
the
peers
that
I
have
open.
Ending
projects,
update
released
in
Hamburg
I
believe
their
last
issue
that
we
have
opened
is
assigned
to.
A
B
A
A
Thank
you
very
much.
Thank
you.
So
that's
that
okay,
so
update
handbook
released
in
selection,
dog
and
talk
on
synthetic
clusters.
Let's
see,
what's
here
so
of
the
release
team
selection,
one
this
one
is
assigned
to
lucky
and
the
ladies
come
in
says:
I'll
work
on
this,
so
I'll
try
to
Conley's
this
week
unless.
B
A
Else
wants
to
help
on
and
next
issue
lock
releases
online
on
synthetic
clusters.
I
believe
we
are
still
waiting
for
a
job
to
be
finished
and
actually,
let's
Adam,
remember
the
comments
and
we
have
enabled
the
CP
of
migration
system
multi
node
clusters
deploy
using
queue,
ADM,
Japanese
culture,
Viator.
A
A
A
Look
more
into
it
after
the
after
disco,
and
you
know
a
we
can
chat
more
about
more
about
this
later
and
also
if
anyone
is
interested,
if
I
knew
I
had
I.
Don't
think
I
mentioned
this
explicitly,
but
if
any
of
these
issues
are
interested
to
any
of
you
in
for
a
for
one
reason
or
another,
please
feel
free
to
drop
it
drop
by
in
review
a
joke.
Add
your
thoughts
comments
on
it
even,
for
example,
a
distinct.
A
A
Let's
see
I
just
want
to
double
check
right
now.
If
there
are
more
who
added
something.
Let's
see,
I
like
the
idea
of
having
a
tracking
issue
for
status
updates.
This
will
also
help
us
search
for
information
in
github,
rather
than
Google.
Docs.
I
still
think
that
we
need
room
for
open
discussion
and
other
topics
than
just
static
reports,
for
that
I
will
stick
to
video
call
once
a
week.
A
Shadows
leads.
If
you
have
any
preference
on
any
of
the
proposals,
I
have
it.
I
have
been
thrown
a.
We
said.
We,
please
drop
your
message,
or
at
least
an
MoU
with
the
thumbs
up
or
thumbs
out
and
information
is
a
useful
and
the
next
issue
improve
dock
release,
handbook
that
one
is
a
one
that
we
just
mentioned.
I
believe
yes,
and
the
last
one
blog
release
notes
JSON.
K
A
A
That
is
hard
to
do.
That's
got
the
backlog,
create
a
quick,
okay,
so
create
shadow
in
retrospective
a
finally,
if
anyone
is
interested
in
any
in
a
proposal
for
the
whole
selling
process,
please
take
a
look
at
this
one.
There
are
some
comments,
but
right
now
the
plan
is
to
wait
for
the
results
from
the
shadow
survey
to
see
how
we
want
to
proceed
with
that
handling
exceptions.
A
October
28th,
okay,
so
that's
gonna,
be
frozen,
still,
create
a
shadowing
template
from
handbooks
and
code.
Freeze,
okay,
so
create
a
shadow
in
template
for
our
handbooks.
What's
lame
is
common
and
holds
weight
on
the
shadow,
so
the
result
from
the
shadow
survey
testing
for
conference.
The
proposal
still
put
I
guess
we're
just
gonna.
Keep
this
one
open
for
the
time
being.
Yeah.
A
If
you
have
anything
specific
that
you
want
to
drive
around
with
seek
testing,
could
you
please
add
in
the
issue
and
and
and
and
discussing
with
people
at
this
very
moment?
The
contents
of
the
issue
are
things
that
I
and
some
other
people
I
discussed
with
discussed
with
sig
testing
in
the
past,
so
a
so
at
least
right
a
right.
Now
it
has
their
summary
of
a
summary
of
our
conversation
and
essentially
the
Congress.
A
The
conversation
was
done
at
this
very
moment
with
the
proposal
that
we
with
the
proposal
that
we,
it
wasn't
very
useful
and
the
proposal
was
just
a
complete
free-
saw
a
testing
track
which,
whichever
I
believe,
but
if
you
have
anything
anything
specific,
please
had
a
please
are
in
the
issue,
and
then
we
can
move
a
way
we
can
vote
for
a
we
can
move
forward.
Do.
F
It
actually
it's
like
right
now.
The
situation
is
that
they
are
green,
South
Korea
at
the
same
time,
because
they
they
can
do
a
part
of
or
the
freeze,
because
they
can.
They
want
to
split
specific
parts
of
their
development
and
Cora
bution
in
the
testing
from
where
they
can
just
block
her
lettuce
or
we
could
just
follow
the
freeze
or
not,
so
they
it's
like
more
complicated.
That's
where
we
thought
so.
F
A
Thank
you
so
much
next
stop
scalability
test
coming
follow-up
from
this
one,
and
that
is
actually
the
only
comment
that
I
think
that
I
can
give
at
this
moment,
and
the
topics
of
discussion
are
just
updates
on
the
fact
that
every
single
thing
that
we
run
is
on
Google
on
infrastructure.
So
we
can
I
mean
we're.
Gonna
need
to
actually
create
the
roadblock
for
moving
a
end-to-end
jobs
off
onto
CN
CF
all
projects,
so
scalability
22-inch
have
applications
feedback.
A
A
No
crying
comment
and
I'm
thinking
about
this
work.
Lucky
has
six
figured
out,
and
the
next
couple
topics
decide
on
pursuit
for
jobs,
something
this
one
we
put
on
hold
to
see
what
comes
out
of
there.
They
says
he
won't
support
a
CAC,
what's
a
project
and
there
was
one
it
shows
my
issue
or
having
access
to
well
a
to
release,
loop
things.
So
I
guess
we
are
all
done.
A
A
Going
once
twice,
ok
awesome,
so
with
that,
let's
call
it
away
everyone
a
thank
you
very
much
for
joining
a
discos,
and
thank
you
very
much
for
the
work
than
everyone
in
every
single
one
of
you
does
to
make
one
eating
happen
in
happy,
Monday,
happy,
Monday,
hope
you
all
have
a
good
rest
of
your
day.
Have.