►
Description
Kubernetes 1.18 Release Team Burn Down Meeting for 20200309
A
So
good
morning,
good
evening
and
good
afternoon,
everyone
welcome
to
yet
another
meeting
for
the
kubernetes.
A
released
him
from
1:18
I
will
be
your
host
today
for
a
my
name
is
Jorge
Lacan
before
we
get
started.
Like
always,
I
have
to
mention
that
we
have
a
code
of
conduct
which
essentially
boils
down
to
please
be
nice
and
kind
to
each
other
at
all
times,
as
we
progress
into
this
meeting,
if
there
is
anyone
interesting,
they
ain't
been
the
official
note-taker.
A
B
B
So
this
is
a
bug
fix
it's
not
directly
related
to
any
of
the
feature
work.
They
were
doing
to
promote
this
to
stable.
However,
the
bug
fix
PR
has
been
open
for
a
little
bit
and
it
seems
like
all
the
code
changes
that
were
requested
happened
before
code
freeze,
but
we
weren't
tracking
this
because
they
didn't
disclose
it
to
us
and
it
wasn't
included
in
there
like
umbrella
tracking
issue,
so
they're
asking
for
an
exception
now
to
merge
this
bug
fix
in.
B
So
we
should
discuss
that
I
think
we're
still
at
I'm.
Sorry
I
didn't
update.
The
total
number
can't
do
math
that
quickly.
The
number
is
basically
the
same
number
of
enhancements
that
we
had
Friday
with
one
exception.
We
had
a
cap
that
was
merged
before
enhancements
freeze,
but
there
was
no
issue
filed
for
it.
So
one
of
the
requirements
for
merging
caps
supposed
to
be
that
there
is
an
issue
for
it
in
the
communities
enhancements
repo,
that's
what
we
use
to
track
enhancements
for
the
releases.
B
This
one
didn't
have
it,
and
specifically
it
is
a
change
to
client
go.
So
if
you
have
been
following
along
there's
a
chain
going
into
client,
go
they'll,
add
context
as
the
first
argument,
like
kind
of
the
go
pattern
for
all
the
things,
and
they
did
not
meet
coach
Frese
for
that
they're
very
closely
asked
for
like
a
one-day
extension,
but
it
points
out
an
issue
with
the
process
that
hopefully
can
be
addressed
by
some
changes
that
were
proposing
in
a
future
kept
work.
B
What
we
proved
this
exception
and
it's
part
of
that
they
went
ahead
and
opened
an
issue
to
track
it.
So
there's
a
new
enhancement
issue
1601
and
there's
no
documentation
associated
with
this
other
than
the
generated
SDK
Docs.
So
they
didn't
miss
anything
there.
The
enhancement
was
merged
before
enhancements,
freeze
and
had
all
the
criteria
it
just
didn't
get
that
issue
associated
with
it.
So
we
would
have
tracked
it
anyway.
I
just
didn't
check
that
box
for
us
moving
on
about
the
exceptions
were
granted
so
far.
The
first
one
is
taint
based
eviction
number
166.
B
They
had
kind
of
a
delayed
merge
of
some
of
the
PRS
they
had
because
they
had
incorrectly
labeled
they're
kept
in
six
scheduling.
It
should
have
belonged
to
sig
note
and
that
kept
update,
sat
open
for
a
long
time,
after
enhancement,
Rees
and
one
of
the
things
they
needed
to
do
was
move
and
and
tests.
So
the
big
tests
already
existed
and
they
were
merged,
but
they
were
in
six
scheduling.
B
They
moved
to
sick
node
so
that
PR
couldn't
merge
until
the
kept
enhancement
merged,
and
that
happened
really
late,
because
sig
node
is
busy
and
we
had
to
ping
them
a
couple
times.
I
think
they're
pretty
much
done
with
that
they're
waiting
for
one
more
PR
to
go
in
the
second
one
that
we
approved
was
for
sidecar
containers.
This
is
another
one
that
kind
of
sat
around
for
a
while
and
we
escalated
up
and
got
people
to
start
taking
a
notice
of
it
and
we
proved
the
exception.
B
Next
we
have
graduate
node
local
DNS
cache
to
GA
was
a
small
one
and
it
just
who
didn't
have
the
milestone
applied
before
code
freeze.
So
we
got
that
taken
care
of,
and
then
the
last
one
is
one
601,
which
is
the
client
go
issue.
So
those
were
the
exceptions
we
granted
of
those
for
three
of
them
are
still
there
again.
The
sidecar
containers
has
deferred
to
119.
We
have
two
exceptions
that
we
haven't
granted
or
that
we
denied
SCTP
support
in
beta
118.
B
This
was
of
interest
because
they
also
missed
the
docks
placeholder
date,
so
we
gave
them
an
exception
for
that
and
they
got
the
docks,
placeholder
thing
open,
but
this
is
adding
a
bunch
of
N
dentists
and
promoting
to
beta
at
the
same
time,
so
there's
not
really
enough
time
for
those
end-to-end
tests
of
soap
and
just
everybody
felt
like
this
wasn't
a
great
thing
to
grant.
So
we
denied
that
one
and
then
this
one
is
another
one
that
doesn't
have
associated
with
it
directly.
Its
extract
cloud
providers
been
specific
credential
providers.
B
This
is
one
that
had
been
open
for
a
little
while
and
just
didn't,
merge
before
code
freeze,
there
wasn't
a
lot
of
expediency
put
into
it,
so
we
didn't
think
that
it
made
sense
to
grant
that
one
either.
So
the
only
one
that's
outstanding
still
in
terms
of
getting
things
merged
in
is
the
sorry
the
team
based
evictions.
They
have
I,
think
1p
are
open
still
and
then
this
current
one
that
we're
tracking
now
for
oopsy
tailed.
B
So
if
anybody
has
any
thoughts
about
that,
one
we'd
love
to
hear
them,
I
think
we're
leaning
towards
approving
it.
However,
kind
of
deviates
from
the
process-
and
it's
not
really,
is
it
really
spa
keen
or
not,
really
sucking
like
at
this
point,
we
should
only
be
doing
release
blocking
PRS
hard
to
tell
if
that
one's
really
release
blocking
or
not
also,
they
knew
about
it
before
code.
Freeze.
A
Come
once
twice
so
I
guess
just
a
closing
remark
that
I
can
that
I
can
add,
is
a
what
probably
continuing
we're
talking
a
little
bit
with
a
cubic
or
a
cube,
coral
reef
after
this
meeting,
and
possibly
this
also,
this
cause.
Why
a
way
what
we
called
a
what
we
could
do
to
kind
of
rate,
to
kind
of
prevent
enhancements
from
work
related
to
enhancements
from
a
slave
from
slipping
away,
for
example,
a
for
example.
A
This
one
just
to
add
a
little
bit
to
the
story
that
can
they
keep
coral
reef
is
something
that
we
just
discovery.
Some
dead
team,
that's
working
on
that
they
also
they
had
a
separate
recognition
in
the
KK
repo.
So
in
has
been
a
sought,
recognition,
enhancements,
warning
a
warning,
KK
and
seems
to
be
that
the
whole
patch
for
it
to
fix
a
cube
coddled.
A
A
cube
conative
was
not
a
as
you
know,
a
assuming
that
people
want
to
stay
communicated
a
which
is
a
we
just
lost
track
of
it
so
somewhere
along
the
way,
but
other
than
that
I
guess
again,
Jeremy
and
Tim.
Thank
you
very
much
for
everything
that
you
all
do
and
we'll
keep
on
talking
about
enhancements
for
the
rest
of
the
week,
but
for
right
now,
moving
on
to
see
a
signal,
Nico.
C
That
is
failing
these
two
classes,
logistic
obsidians
in
the
fix,
was
supposed
to
be
in
the
PR
that
I
linked
in
the
doubt,
but
something
was
messed
up
with
a
rebase,
so
we
actually
expecting
a
different
PR
to
be
open
for
to
fix
the
job
as
well,
the
other
to
joke
start
with
DC
winters
jokes
that
are
they're
failing
and
they
were
failing
because
of
a
sick,
CLI
test
case,
which
seems
that
then,
but
the
job
software
in
some
time.
Some
point
is
seem
totally
broken.
C
So
I
open
another
issue
to
investigate
this
and
pink
Windows
theme
for
it.
The
build
product
steps
is,
this
is
still
failing,
but
it's
not
critical.
It's
also
prioritize
I
said,
but
assume
it's
the
same
dismiss.
We
have
only
worked
really
hard,
flaking
job
which
I
ended
up
below
you
check
it
out
and
in
1.18.
Blocking
in
the
opportunity
in
forming
dashboards
is
like
the
same
jobs
that
are
failing
with
muscle,
breaking
forming
corresponding
pretty
much.
That's
all.
So
any
questions
guys
I.
C
A
Skewed
close
religious
yeah,
actually
Rob
and
Jordan
have
been
working,
have
been
working
on
it.
There
is
a
third
separate,
Thursday,
perfect,
ideal
solution,
that's
a
bigger
that
is
open
and
reference.
Some
orientation
a
I
can
find
it
neither
two
notes
later,
but
there
is
not
the
ideal
solution
which
which
was
proposed
by
Jordan,
and
what
stopped
it
was
to
open
a
couple
hours
ago.
Then
there
is
a
short-term
solution
that
is
just
going
to
end.
A
That
is
just
going
to
get
the
end-to-end
test,
the
broken
into
n
test,
a
work,
a
working
for
now
that
one
is
a
currently
of
work
in
progress,
the
rough,
a
rough
Scott
up
in
a
PR
for
that
one
to
they
to
replace
a
one
that
you
reference
in
the
notes.
The
only
difference
is
on
the
PR
is
now
against
a
release.
A
117
branch
branch
because
turns
out
that
the
failure
is
because
we
were
testing
117
code
in
the
job
and
as
far
as
I
know,
that
is
a
delay
and
there
is
a
latest
right
now
with
respect
to
the
a
with
respect
to
that
issue
which,
as
some
check
in
right
now,
that
is
the
only
thing
that
we
have
broken
your
master
blocking,
correct,
yeah,
yeah,
okay,
awesome!
So
that's
kind
of
good.
A
C
A
C
It's
different
job,
but
they
are
failing.
It
seems
that
they're
fighting
for
the
same
reason
actually
most
of
the
test.
Actually
they
were
trying
to
be
formed
because
of
the
60
light
test.
Yes,
but
right
now,
as
if
we'd
taken
the
job
looks
now,
most
of
them
are
failing
because
of
some
timeouts.
Maybe
it's
related
with
actualism.
A
A
D
Hello,
our
current
status
is
red
as
far
as
careers
go
for
non-test
flake
issues
in
in
KK
we're
down
to
three,
which
is
minus
four
from
last
Friday.
We
have
one
remaining
critical,
urgent
issue
that
is
still
open,
that
we're
tracking
we
do
not
have
any
important
soon
issues
which
is
good.
So
that's
minus
two
from
us
Friday
for
open
P
ours
in
KK.
For
this
release,
we've
got
14,
so
that's
minus
12
from
Friday,
so
that
was
a
good
drop
for
critical,
urgent
PRS.
D
We've
got
two
remaining
for
importance:
we've
got
nine,
that's
minus
seven
from
Friday
and
then
open
KK
issues
for
this
release.
We
were
done.
21
for
the
rest
of
this
week
were
2
gets
any
monitoring
for
the
exceptions
for
anyone
that
we
need
to
start
tracking.
There
are
a
few
PRS
that
we
need
to
potentially
remove
from
this
current
milestone.
We
will
be
evaluating
those
this
week
and
taking
the
appropriate
action.
E
So
today
we
have
a
dog's
deadline
like
March
9th
at
as
a
placeholder
dog
spear
should
be
ready
for
review.
State
and
I
see
all
the
enhancements
dogs
are
ready
for
real
estate,
except
one,
so
I
added
link
to
the
enhancement
in
the
dog
sheet
and
other
thing
that
just
we
have
one
enhancement
which
is
not
retaining
the
deadlines
or
the
statuses
are
lowers
of
norm
and
we
have
another
hardship
with
em
1.18
branch.
So
we
accidentally
much
desync
of
between
master
and
a
1.1.
E
It
intuitive
1.18
without
a
label
tied
much
method
much
so
it
created
conflicts
within
the
branch.
So
we
reverted
it
back,
but
it
needed
rebus
for
all
the
yes
which
are
raised
against
em
1.1.
It
so
I
think
George.
You
are
aware
of
it.
There,
like
the
cig
talks.
Coaches
have
already
pulled
you
into
that
yeah,
so
we
are
doing
good,
but
it
is
one
thing
to
be
noticed.
E
Yes,
so
what
happened
was
usually
as
a
dogs
lead
I?
My
job
is
to
track
the
enhancements,
as
well
as
produce
income
between
three
branches,
which
is
de
1.18
master
and
released
1.17.
So
whoever
does
any
changes
to
the
master
should
be
part
of
the
1.18
to
make
sure
that,
on
the
day
of
release,
the
dogs
mode
happens
easily.
So
as
a
part
of
that
I
keep
sinking
of
master
and
a
1.18.
So
when
I
raised
a
clear
against
a
one
point,
one
at
the
sink,
we
are
the
dogs
release.
E
Handbook
says
that
we
should
add
a
label
tied,
much
method,
much
so
that
it
does
some
operations,
so
I
I
somehow
miss
to
do
that
label
and
we
merged
it.
So
that's
how
the
integration
we
have
started,
showing
as
a
conflicts
and
couple
of
files,
so
we
reverted
it
back
and
then
we
tried
to
make
sure
the
branch
is
healthy,
but
people
when
we
have
most
that
the
couple
of
days
earlier
we
there
was
a
deadline
for
dogs.
Please
hold
up
here.
E
People
started
cloning,
the
day,
1.18
and
trace
the
peers
with
that
revert
commit
so
they
needed
there.
All
they
need
is
to
do
a
rebase
know
before
they
merge
it
into
day,
1.18
yeah,
so
yeah
it
was
a
bit
confusing.
Yes,
I
didn't
know
like
missing.
A
label
will
causes
such
a
huge
confusion.
But,
yes,
we
are
actively
talking
tracking
all
the
talks
enhancements,
so
it
should
be
okay,
yeah!
That's.
A
E
It
is
already
documented
in
the
least
handbook,
so
I
have
done
couple
of
sync
ups
earlier,
but
somehow
I
dismiss
that
branch
and
even
Zack
missed
out.
So
we
put
together
moist
it
into
there
1.1
it
and
then
we
reverted
it
back
in
next
two
to
three
days,
but
in
this
two
to
three
days,
other
all
the
enhancements,
one
who
started
cloning,
the
1.18
and
started
doing
the
placeholder
pair.
So
that
was
an
issue
yeah.
A
E
Think,
like
I,
should
I
should
I
am
planning
to
do
one
session
with
my
shadows
so
that
how
important
are
labels
so
that
they
won't
get
into
this
problem
so
yeah
it
is
already
documented,
but
the
frequency
of
we
follow
the
docs
every
time
we
sync
up
is
a
bit
less.
So
we
just
take
the
dogs
for
first
time
and
then
the
the
next
sync
ups.
We
just
do
it
manually,
so
yeah
I'll,
just
share
it
with
my
shadows
and
I'll.
E
Try
to
ask
them
to
review
the
release
handbook
and
if
they
feel
any
capture,
I
will
try
to
add
that.
So
there
is
an
already
an
issue
raised
against
the
release:
release
to
update
the
docs
release
handbook
so
I'm,
just
waiting
with
more
time
to
gather
all
the
gaps
and
the
problems
I.
Faced
to
a
clearly
document
in
the
release
handbook:
okay,.
E
E
A
I
definitely
want
to
check
on
the
check
on
this
a
little
bit
more
with
my
first
thought
and
Jeremy.
I
would
love
also
some
of
some
recommendations
on
this
and
the
rest
of
the
and
the
rest
of
the
team
if
they
haven't
updated
anything
and
they
haven't
been
responsive,
I
will
say
that
we
I
would
say
that
we
drop
the
issue
that
we
drop,
the
enhancement
yeah.
B
E
B
C
E
A
F
G
We
are
green,
we're
finishing
voting
today.
We
just
have
one
more
thing
to
go
through
and
then
I've
actually
been
talking
to
Caitlin
Barnard
and
she's,
a
blog
editorial
lead-
and
she
mentioned
to
me
that
it
looks
like
over
the
past
few
releases.
The
blogs
have
kind
of
varied
in
terms
of
how
much
coverage
there
is
so
like
for
the
last
release.
I
think
there
are
like
two
future
blog
releases
and
then
the
one
before
that
it
was
one
and
they
think
for
1.15.
G
It
was
one
and
then
for
1.14
I
think
there
are
four
blog
releases,
so
she
mentioned
that
there
might
have
been
some
documentation
that
was
lost
between
in
terms
of
like
how
we
want
to
do
the
plugs.
But
in
the
meantime,
I've
had
my
team
staggering.
So
we've
all
chosen,
like
our
top
five
and
we'll
figure
out
like
you,
know
like
what
we
collect
you
feel
like,
should
be
covered
first
and
well-well.
G
Probably
what
I
imagine
is
happening
will
happen
is
like
we'll
probably
cover
maybe
three
features
but
I'm
still
kind
of
figuring
out
what
we
should
do.
Just
cuz
like
it
seems
like
that
pattern
got
lost
somewhere
in
between
so
yes,
I,
don't
talk
to
C&C
up
about
that
and
then
yeah
and
then
once
we
do,
that
I'm
just
gonna
try
and
get
everything
ready
to
reach
out
to
the
SIG's
for
their
blog
content
and
get
that
ready.
G
A
Quick
question
a
quick
question:
at
the
end,
this
might
be
a
dumb
question,
so
normally
normally
the
blocks
they
go
out
relatively
clear,
close
to
their
release
right
yeah.
Is
there
any
reason
why
let's
say
we
couldn't
keep
a?
We
couldn't
keep
asking
people
to
write
blogs
about
the
features.
Are
they
promoting
the
latest
release
a
for
a
longer
time,
let's
say
one
or
two
months?
Oh,
you.
G
Or
do
we
just
schedule
everything
out
in
advance,
yeah
I
think
that's
worth
looking
into
I
think
what
Caitlin
was
saying
was
that
okay,
yeah
Lockheed
says
blog
wise
as
many
as
you
can
gather
yeah
cuz.
It
sounds
like
what
they
did
like
me
for
1.13
I,
think
this
is
before
my
time,
but
I
think
Kaitlyn
said
that
they
had
like
five
different
blog
posts
and
then
they
released
like
one
a
day
during
like
the
release
week,
and
so
this
wasn't
necessarily
like
spread
out
during
the
few
after
the
release.
A
G
A
G
A
A
G
From
what
I've
seen
in
the
past,
it's
usually
like
the
co-chairs
or
like
the
sig.
Usually
we
reach
out
to
the
chairs,
and
then
they
come
back
with
the
content.
So
I
don't
know
depending
on
like
how
it's
done
like
I,
think,
usually
the
coaches
do
it
and
I
don't
know
if
they
end
up
like
reaching
out
to
the
rest
of
their
team,
but
yeah.
G
Usually
the
coaches
of
the
things
that
we're
reaching
out
to
will
give
us
the
content
and
then
it
gets
like
added
together
and
then
yeah
and
then
I
think
they
like
there
might
be
some
like
editing
work
to
weave
it
all
together,
depending
on
the
structure
of
the
blog
post.
But
the
bulk
of
the
actual,
like
technical
content,
comes
from
the
co-chairs.
Yeah.
H
I
think
yeah
I
think
+12
more
content
over
a
longer
period
of
time,
rather
than
one
blog.
It's
just
always.
You
know
in
1/16
it's
just
hard.
There
was
something
like
30
or
40
enhancements
and
we
can
get
people
to
write
about
3
yeah.
So
it's
not
actually
it's
not
doing
the
scheduling,
that's
hard
of
actually
getting
the
people
that
wrote
the
enhancements
to
provide
the
content
on
the
blog.
H
G
A
H
I
think
you
know
how
it
plays
out
George's,
it's
just
a
lot
of
work
like
people
are
doing
the
cap,
writing
the
code
getting
the
docs
done
and
then,
when
you're
asking
them
to
write
a
blog
on
top
of
it.
So
you
know
Karen
said
the
leads
work
on
it.
I've
seen
a
lot
of
the
enhancement
owners
actually
write
the
blog's
and
then
you're
asking
them
to
do
that
on
a
very
strict
timeline
and
if
you
don't
get
it
before,
the
release
goes
out,
they're
even
less
likely
to
do
it
because
they've
moved
on.
H
A
Somebody
dumb
makes
a
lot
of
sense
and
okay
I
think
something
that
might
be
interesting
to
follow
up
on
so
a
but
yeah
at
least
for
that,
at
least
for
the
time
being,
we
can
follow
up
a
afterwards
if
anyone
is
interested
from
right
now.
Does
anyone
have
any
more
comments?
Questions
so
yesterday
for
dogs
can't
gums,
sorry
I.
A
I
Hat
Monday,
we
are
doing
the
bridge
fest
forth
with
no
problem
too
far
and
missing.
Today,
I'm
gonna
do
after
this
meeting
and
we
for
tomorrow
we
have
118
better
to
reschedule
and
Daniel
will
be
cutting.
Is
the
branch
venture
associate
and
he
going
to
be
this-
cutting
for
this
beta
tube
for
tomorrow,
I
post
in
the
meeting
notes,
all
the
issues
related
to
giving
access
to
him
and
also
the
they
should
that
schedule
they
discussed.
A
H
Thanks
George,
just
one
quick
one
today,
so
we
closed
out
the
shadow
need
release
cycle
survey
on
Friday.
Thanks
to
all
that
participated,
we
had
69%
it's
a
patient
across
all
the
Sabbath
shadows.
I
just
called
out
some
observations,
I'm
going
through
the
long
sections
as
we
speak,
but
a
hundred
percent
of
the
shadows
said
they
participated
in
orientation,
a
hundred
percent
of
the
responding
shadows
and
they
have
a
clear
understanding
of
the
role
expectations
and
then
I'm
going
to
call
out
down
the
bottom
there
and
the
oranges
11%
of
responding
shadows.
H
So
they
had
an
OK
experience
which
is
still
on
the
positive
side.
That's
three
stars!
If
you
would,
but
it's
you
know,
people
saying
that
their
experience
is
just
ok,
so
maybe
we
want
to
drill
in
there
and
see
what
the
comments
state
there
as
the
hell
with
better
support
those
shadows.
So
thank
you
to
everybody,
I'm,
going
to
digest
them
and
put
them
into
subsequent
emeritus
League
guidelines
so
that
we
can
make
the
shadow
program
more
effective
for
the
release
team.
A
H
H
A
Any
more
questions,
if
not
again,
thank
you
very
much
lucky
and
moving
on
to
release
three
rotates.
So,
like
always,
let's
start
with
the
upcoming
milestones.
So
we
all
know
what's
going
on
first
off
dogs
deadline
that
is
today,
I
see
was
all
day,
I
see
what's
already
mentioned,
and
it
seems
that
the
enhancement
that
we
were
just
discussing
about
multiple
scheduling
profiles,
if
I
remember
the
name
correctly
just
cut
some
updates
other
than
that
1:18
beta
2
is
planned
to
be
released
tomorrow
and
hopefully
that
works
out.
A
I
will
leave
the
after
that
next
week,
we're
going
to
start
with
the
actual
RC
releases
as
we
get
closer
and
closer
to
the
release
deadline
and
the
next
one.
Next
deadline
dogs
have
to
be
completed,
LPS
revealed
and
ready
to
be
merged
by
Monday,
March
16,
which
I
believe
is
next
Monday,
and
the
day
after
that,
since
I
know,
everyone
has
been
enjoying
code
freeze
up
until
now,
but
next
week
called
a
we're
gonna
we're
gonna
start
with
Kota
open
up
there.
A
We
open
up
the
master
branch
and
go
into
our
118
branch
for
the
way
for
the
remaining
day.
For
the
remainder
of
this
release
cycle
and
other
than
that,
the
public
service
announcement,
like
is
that
if
you
have
found
anything
interesting,
if
you
learned
anything
that
you
want
to
make
sure
to
pass
on
to
future
generations
of
release
team
members,
please
write
a
quick
comment
about
a
whatever
that
is
or
about
your
experiences
in
general
in
there
in
the
register
and
a
in
the
release.
A
Okay,
so
it
sounds
like
something
that
we
can
check
on
it
once
like,
after
a
after
this
meeting,
just
to
make
sure
we
get
more
a
comment
on
this
and
the
your
question
that
also
I
also
need
to
start
doing
some
planning
on
a
for
next
week.
The
plan
is
like
a
like,
always
a
we're.
Next
week,
we're
gonna
start
with
Monday
with
daily
rundown
meetings,
because
I
know
that
you're
all
love
meetings,
so
I'm
gonna
reach
out
today,
I'm
gonna
reach
out
to
everyone
and
get
some
ideas
for
anytime.
A
So
you
all
want
to
do
the
means
for
Tuesday
and
Thursday,
so
hopefully
people
that
can
make
it
to
the
regular
meetings
they
can.
They
can
make
it
to
those
meetings
and
then
we
can
discuss
more
kubernetes,
goodness
other
than
that.
Does
anyone
have
any
more
comments,
questions
suggestions
and
is
everyone?
Okay,
with
time
zones,
I'm
gonna,
take
science
as
an
agreement,
and
the
last
section
a
the
last
of
day
for
today
is
from
sick
scalability.
They
finally
have
a
broken
issue.
A
A
Once
twice
sold
so
more
PSAs
from
the
open
discussion
again
from
the
a
for
the
last
couple
of
weeks,
I
had
the
same
Candice
handling
the
same
couple
of
issues
for
anyone
who
might
be
interested
in
providing
feedback.
Twenty
of
these
topics,
the
first
one,
is
a
release
retrospective
again
a
if
you
have
anything
whatsoever
that
you
want
to
pass
on
to
future
generations.
A
please
I,
don't
know
tinder.
Then
there
is
a
enhancements
Kephart,
a
artifacts.
A
If
you
are
interested
in
the
actual
mechanics
of
the
release,
if
you
want
to
propose
more
ways
for
for
us
to
communicate
and
help
the
release
team
be
more
time
some
friendly.
Please
drop
your
comments
in
the
cover.
Nettie
seek
release,
issue
877
and
if
I
haven't
checked,
haven't
checked
this
one
in
in
a
bit.
But
if
you
are
elite-
and
you
think
you
might,
you
might
benefit
from
having
a
tracking
spreadsheet
of
some
sort
or
if
you
don't
think
that
you
will
team
needs
it.
A
I'm
just
gonna
color
a
day
in
I'll
try
to
go
to
the
poor
as
synchronously
and
ping
people
I
did
a
I
did
that
a
couple
days
ago
it
seems,
like
things,
are
moving
along
for
a
for
the
most
part,
so
other
than
that
a
want
to
close
off
the
meeting
and
thank
thank
everyone
from
showing
up
and
thank
you
to
every
single
member
of
the
release
team
for
all
the
amazing
work
that
you
all
do
and
happy
Monday
I'll.
Let
you
all
and
I'll
give
you
back
15
minutes
of
your
day,
happy
Monday.