►
From YouTube: 2020-09-29 Apache Cassandra Contributor Meeting
Description
- Discussion around CASSANDRA-15536 and getting 4.0 in its final state for shipping.
- Making things easier for new contributors for some of the 4.0 backlog
- Creating a place for users to contribute data models for testing boundaries of Cassandra
B
A
Just
a
tuesday,
it's
just
a
tuesday.
Okay,
welcome
everyone!
Welcome
to
a
contributor
meeting,
we're
all
family
and
friends
here.
If
anyone
would
like
to
start
start
with
yelling
at
somebody.
That
would
be
a
great
way.
That's
how
my
family
starts
a
meeting.
So
maybe
not
yours,
okay,
not
yours!
I
think
it
would.
The
the
purpose
of
this
meeting
in
the
agenda
was
around
cassandra
4.0
getting
that
out
the
door,
but
specifically
it
was
cassandra.
B
I
was
one
that
created
that
epic,
so
I'm
guilty,
we
got
two
things:
number
one
is
assignees
and
number
two
is
shepherds
and
whether
or
not
the
shepherds
that
are
on
there
have
the
bandwidth
to
engage
or
not.
I
talked
to
jordan
john
last
week
about
this,
because
we
were
gonna,
get
the
project
management
emails
back
up
and
going
because
we
kind
of
dropped
those
after
the
beta
hit.
B
So
what
we
were
like
as
a
shared
point
of
view,
gonna
propose
is
just
let's
figure
out
if
the
shepherds
that
are
on
there
have
the
bandwidth
to
help
mentor
and
guide
those
tickets
and
if
not,
we'll,
pull
them
off,
and
that
way
we
have
a
view
of
which
of
these
tickets
need
shepherds
which
one's
the
assignees.
Then
we
know
where
the
gaps
are
in
terms
of
resourcing
and
go
from
there
does
that
seem
sane.
B
Yeah
and
that's
gonna
require
just
constant
attention.
Essentially,
somebody's
just
gonna
have
to
have
a
checkbox
where
every
day
or
every
other
day
they
go
through
and
make
sure
that
things
are
still
moving
along
and
to
paulo's
point
from
the
dev
list.
There's
there's
an
opportunity
to
use
the
status
and
jira
to
surface
this
stuff,
so
blocked
or
awaiting
feedback.
We
can
just
create
quick
filters
and
see
when
things
are
stalling
and
just
poke
and
keep
them
going.
C
D
Those
yeah-
I
think
that
we
talked
about
too,
which
is
important,
is
right.
Now,
there's
no
progress
on
them.
We
don't
have
to
make
progress
on
all
of
them.
Just
like
progress
on
some
is
is
progress,
so
you
know,
I
think
it's
also
paulo's
picture
is
nice
to
see,
because
we
see
that
also
three
of
them
have
had
some
work
done
and
I
think
those
can
be
a
model
for
for
how
the
others
get
done.
A
D
C
That'll
go
a
really
long
way,
yeah
and
in
cases
where
folks
are
assigned
to
something,
but
are
currently
working
on
something
else
if
they
can
offer
an
estimate
of
when
they
expect
to
be
able
to
pick
it
up.
I
think
that'll
help
us
all
plan
as
contributors
to
a
project
or
figure
out
if
it
might
be
good
for
somebody
else
to
pick
it
up.
If
that's
too
far
out.
D
D
Here,
yes,
this
one
yeah,
eight
two,
I
think
the
metrics
one
has
been
a
good
example
of
I
think
like
ideally,
what
would
happen
where
a
few
people
got
together?
I
don't
know
if
david
and
dinesh
and
others
want
to
speak
to
this-
that
were
involved,
but
they
got
together
and
sort
of
figured
out.
You
know
here's
a
proposal
for
some
testing,
here's
how
we
can
take
that
and
make
it
a
little
bit
better.
A
D
Yeah,
I
don't
think
we've
had
the
like.
I
think
an
area
we
could
improve
is
probably
like
project
management
hygiene,
both
in
this
case
and
another
one
that
josh
john
and
I
talk
a
lot
about
is
fixed
version.
4.0
beta
just
tends
to
be
the
default
for
everybody,
so
I
think
there's
a
few
areas
where
we
could
be
like
as
a
group
a
little
bit
more.
On
top
of
that.
D
B
B
What
we're
leaning
on
is
the
qualitative
assessment
and
synthesis
of
practitioners
of
operators,
people
that
know
the
codebase
but
also
run
it,
but
that
means
we've
got
to
figure
out
a
way
to
articulate
and
then
kind
of
codify.
What
that
what
that
is?
Where
is
the
uncertainty?
Where
is
the
fear
where
the
defects
seem,
and
I
think
that's
the
big
gap
that
we've
got
to
bridge
on
these
tickets
right?
Where
the
statement
is,
we
don't
trust
subsystem
x,
there's
a
massive
amount
of
value
and
signal
there.
But
the
question
is
what
aspects
of
it?
B
D
Agreed-
and
I
think
again
for
some
background
on
the
shepherd
to
point
that
out
like
that,
was
a
proposal
joey
made
to
address,
I
think
kind
of
exactly
what
you're
talking
about,
which
is.
We
may
not
need
subsystem
experts
to
be
working
on
the
tests
all
the
time,
but
there
does
need
to
be
a
subsystem
expert.
The
shepherd
who
has
an
idea
of
sort
of
where
is
valuable
test,
et
cetera
because
of
that
knowledge,
because
we
don't
have
that
data
to
drive
those
decisions
out
in
the
public.
A
D
A
A
F
G
B
B
Yeah,
I
think
that
that
that
right
there
is
the
bridge
for
each
of
these.
If
we
can
figure
out
what
the
acceptance
criteria
is,
it's
going
to
require
some
exploration.
That's
going
to
require
a
shepard
input,
that's
going
to
require
that
dialogue,
but
then,
once
we
have
that
anybody
should
be
off
to
the
races
that
can
work.
D
F
D
And
I
felt
that
too
so,
when
I
first
joined,
went
back
to
working
on
cassandra
because
I
had
taken
a
break
in
between.
I
started
with
testing
and
I
kind
of
said
like
I
need
a
domain
expert
to
tell
me
what's
valuable
to
test
because
I've
been
out
of
it
so
long.
So
I
definitely
think
that's
important.
A
A
We
get
a
good
set
of
energy,
there's
a
lot
of
excitement,
a
lot
of
things
happen
and
then
just
because
we're
disconnected
it
tapers
off
and
the
shepherd
seems
like
that's
a
good
move
to
you
know
someone
who's
like
feeling
like
they
can
keep
it
moving,
but
like
to
your
point,
jordan,
it's
like
hey.
I
want
to
dig
in
here.
B
Where
do
I
even
start?
Well,
people
come
and
go
right
on
open
source
projects
and,
like
steven
being
a
great
example
of
that.
Essentially
somebody
has
to
take
on
the
mantle
of
applying
energy
into
the
system
and
of
continuing
to
check
to
make
sure
that
shepherds
are
engaging
of
seeing
if
things
are
blocked
for
a
long
time.
If
seeing
that
people
aren't
responding
and
things
are
stuck
awaiting
feedback
and
of
helping
kind
of
navigate
transitioning
to
different
shepherds.
B
If
somebody
doesn't
have
the
time
to
take
on
that
role-
and
I
think
that's
really
all
all
this
subset
of
work
actually
needs
is-
is
just
that
energy
put
into
making
sure
the
shepherds
are
available
and
engaged
for
the
time
frame
being
worked
on.
Expectations
are
clear
of
availability
and
that
we
get
acceptance
criteria
for
everything
that's
on
here
and
then
the
role
the
shepherd
becomes
significantly
less
necessary
because
we've
codified
the
value,
but
we
want
to
explore
in
the
domain
and
then
the
work
can
be
done
and
it's
like
utopian
and
ideal
right.
B
It's
a
lot
more
complex
than
that,
and
then
you
get
into
it
like
here's
all
the
reasons
why
none
of
this
works
and,
like
we've
all
been
through
it
before
this
code
base,
but
I
don't
think,
there's
anything
like
too
too
terribly
existentially
threatening
about
this.
I
just
think
it's
going
to
require
someone
doing
it,
which
is
easier
said
than
done
with
an
open
source
project
and
volunteer.
F
H
Also,
another
question
I
had
was
you
know.
I
looked
at
the
epic
and
I
saw
all
these
unassigned
tickets
like
at
the
very
least.
What
I
would
want
to
know
is
which
one
do
we
want
to
hack
away
at
first
right.
What
is
more
critical,
like
I
don't
believe,
and
everything
is
important.
That's
total,
like
there's,
always
going
to
be
something
that's
slightly
more
important
than
something
else
right.
So
I
look
at
these
tickets.
H
H
You
know,
at
least
knowing
the
priority
gives
me
a
signal
and
I'm
being
selfish
when
I
say
that,
but
I
think
it
actually
gives
other
people
a
signal
too.
It's
like
hey.
These
are
the
things
that
need
to
be
done
in
order.
Here's
an
easy
one,
here's
a
hard
one.
So
that's
hard
to
understand
too,
like
somebody
who's,
an
expert
can
say
this
is
probably
going
to
be
difficult
because
you
got
to
go
through
the
code
and
look
at
which
metrics
are
in
in
each
of
the
versions.
Make
an
ex
file
compare.
C
Sure,
yep
good
day
to
clarity,
there
sounds
super
important.
We
can
use
the
priority
field
to
indicate
what
we
assess
as
the
relative
priority
for
the
project.
I
know
that
I
have
a
couple
personal
biases
in
terms
of
like
correctness
of
the
read,
write,
path,
repair,
compaction
and
that
type
of
thing,
and
a
little
less
concern
about
like
first
party
and
bundled
tooling,
but
yeah,
absolutely.
B
But
you
know
here
we
dragons
right,
because
the
relative
priority
of
different
tickets
to
each
other
on
a
granular
basis
to
queue
work,
is
something
that
we
probably
have
a
lot
of
different
opinions
on,
and
so
I
think
I
think,
scott's
kind
of
more
broad
brush
of
let's
just
set
the
priority
field
for
how
important
it
is
to
like
the
fundamentals
of
what
the
database
offers
is.
Probably
the
right.
A
A
B
Chris
jordan
alluded
to
this.
Thank
you.
Chris
jordan
alluded
to
this.
Where,
like
the
fixed
version,
we
kind
of
have
this
default
bucket
that
we're
dumping
everything
into,
and
we
don't
really
have
a
muscle
as
a
project
for
going
through
and
grooming
that
backlog
and
saying
you
know
this
is
this
is
okay
to
go
on
4.1,
for
instance,
so,
the
from
a
from
an
optics
perspective,
the
backlog
of
work
for
40
is
growing
at
a
pretty
intimidating
rate,
but
from
a
reality
perspective
we
could
probably
serve
to
groom
that
stuff
out.
B
I
B
I
mean
there's
I'm
just
kind
of
like
brainstorming
here,
so
probably
stupid
ideas
forthcoming,
but
dropping
everything
into
some
kind
of
like
40,
triage,
fixed
version
or
giving
them
a
label
and
then
having
people
actually
go
through
and
select
from
that
bucket
and
opt
in
for
them
into
something
where
we
say:
okay,
a
human
being
that
is
on
the
project.
Right
now,
cares
about
this
being
done.
B
D
B
A
B
D
B
C
One
of
the
things
that
I
think
we
see
a
lot
pattern
wise
when
looking
at
the
burn
up
charts
that
josh
has
shared
is
that
we're
making
rapid
progress
on
new
issues
that
are
identified
and
fixed
quickly
as
part
of
different
contributors
for
upgrade
programs
and
their
quality
and
testing
work.
But
we
probably
have
a
pretty
substantial
backlog
that
isn't
moving
much
hasn't
moved
much
in
a
long
time
and
isn't
really
being
actively
worked
on.
A
Well,
I'm
gluing
what
you're
saying
scott
with
what
rahul
is
saying-
and
it's
like,
I
think,
that's
really
important-
is
like
there's
an
overwhelm
factor
when
you
show
up
and
you
look
at
a
kanban
or
something
like
that.
Like
I
I
I
can,
I
have
the
ability
I
just
I'm
a
little
nervous
about
where
to
start
or
I'm
not
sure
where
to
start
and
it's
yes
and
you
can
go
into
the
dev
list
or
you
can
go
somewhere
and
ask.
But
it's
not
you
know,
I'm
just.
How
do
you
lower
the
barrier?
A
A
A
B
D
A
I'll
drop
it
in
the
chat.
I
think
this
is
something
I'm
I'm
thinking
in
terms
of,
I
think
everyone
here
is
is
probably
much
more
in
the
know
about
a
lot
of
things
in
the
project,
but
I'm
thinking
of
like
melissa,
you
and
I
come
together
on
like
a
blog
post
that
talks
about
like
hey,
you
want
to
help
get
4.0
across
the
board.
Here's
some
stuff
that
would
be
really
helpful
right
now,
and
it's
it's
these,
like
this
backlog
that
we
could
clear
out
but
be
more
forthcoming
about
it.
J
D
I'm
also
not
sure
any
of
those
wiki
tickets
are
marked
low
hanging
from
trying
to
see
what
is
bajirao's
being
very
slow
for
me
right
now,
but
the
links
in
the
chat,
if
folks,
want
to
pull
it
up,
it's
lhf
with
the
no
assignee
open
only,
but
you
can
pull
the
no
assignee
off.
If
you
want
to
see
what
other
tickets
are
in
there
as
an
example,
I
don't
know
what's
in
there,
it
may
be
completely
not
valuable
to
new
contributors
or
people
that
can
help.
J
But
the
things
I
would
think
of
in
that
bucket
are
possibly
the
non-um
non-deeply
coding
tasks,
so
perhaps
things
like
reviewing
release,
notes,
reviewing
documentation
and
checking
that
you
can
actually
do
the
things
that
it
says
that
you
can
in
the
docs.
Looking
for
holes
where
you
know
when
you
try
to
do
something
and
raise
it
as
a
flag,
saying
hey,
I
tried
to
install
cassandra,
40
and
and
I'm
in
this
terrible
mess.
You
know
those
sorts
of
things
that
could
smooth
the
path
for
other
upgrades.
Later.
D
Scott
go
ahead.
I
know
you're
good.
It's
also
actually
a
wonderful
opportunity,
I
think,
to
bring
people
in
if
you
have
an
active
shepherd,
because
I've
always
found
at
least
that
pairing
someone
with
a
fresh
set
of
eyes
with
an
experienced
person
leads
to
some
really
like
effective
testing,
and
it
gives
the
person
who's
new
a
chance
to
learn
a
subsystem
that
they're
probably
going
to
need
to
learn
deeply
to
work
on
it
anyways.
C
Yeah,
what
I
was
going
to
add
as
well
was
that
I
think
one
of
the
best
opportunities
for
new
contributors
to
contribute
to
the
project
would
be
to
help
prepare
for
their
own
upgrade
via
things
like
executing
diff
tests
or
any
performance
tests
that
they'd
like
to
run
on
their
side.
That
will
both
help
them
gain
confidence
in
the
quality
of
the
build
and
their
ability
to
upgrade
to
it,
but
also
help
us
identify
performance
issues
or
potential
correctness
issues
before
we
cut
the
release
too.
A
C
J
So
one
of
the
other
ways
that
we
could
perhaps
push
those
is
through
the
status
updates
that
the
three
of
three
of
us
jays
were
sending
out,
and
we
can
include
things
that
that
aren't
being
worked
on
right
now
and
and
will
be
good
to
being
picked
up,
which
is
an
interesting
segue
into
asking
the
community
more
broadly,
how
useful
they
found
them.
And
if
we
would
be
able
to
pick
up
the
pace
by
producing
them
slightly
more
frequently
like
two
or
three
times
a
week
and
listing
what
we
think.
J
So
yeah,
I
guess
the
reason
we're
doing
it
specifically
now
is
to
try
and
accelerate
the
the
completion
of
the
40
project
as
much
as
as
general
community
health,
which
I
do
think
is
important,
but
everyone
seems
very
hung
up
on
completing
400
and
being
able
to
move
on
past
it.
So
that
to
me
feels
like
it's
most
important
to
achieve
some
success,
fair
and
then
we'll.
If
we're
smart,
we'll
build
on
that
momentum
and
continue
to
to
keep
the
community
strong
by
pushing
them
past.
That.
A
This
is
a
good
line.
So,
okay!
Well,
I
think
we'll
pick
this
up.
I
mean
this
is
this
is
really
good.
I
think
this
is
a
nice
direction
that
we're
getting
out
of.
This
is
a
good
discussion,
but
I
know
melissa
and
I
will
talk
about
how
we
can
do
like
a
blog
post
and
I'm
gonna
go
tap
on
people
and
who,
if,
if
I'm
gonna,
be
the
person
who's
gonna
rattle,
the
cage
on
hey
who's
got
some
lhf.
For
me,
I
need
to
make
sure
that
I'm
not
just
bugging.
B
J
H
G
G
H
C
A
C
I
was
gonna
highlight
the
update
that
iphone
added
on
15537,
because
it
is
something
that
I'm
I'm
glad
that
we're
able
to
to
get
up
on
the
ticket.
Iphone's
update
on
the
status
of
upgrade
and
diff
test
was
the
dozens
of
clusters
so
far
that
he's
been
working
with
and
passed.
The
diff
test,
which
compare
a
3-0
build
with
the
latest
4-0
with
the
number
of
clusters
increasing
each
week
and
tested
clusters
with
data
sizes,
ranging
from
gigabytes
tens
of
terabytes.
C
B
I
mentioned
this
to
random
people
in
random
context,
but
a
couple
of
contributors
are
looking
at
open
sourcing,
something
that
does
similar
things
that
uses
cassandra
diff,
that
uses
workload
generation
tools
to
compare
different
clusters
spanning
different
versions
and
things
of
that
nature
to
make
it
available
for
the
community.
It's
pretty
nascent
but
clear
through
legal,
just
have
to
find
a
name
that
is
not
terrible
and
naming
things
is
hard,
so
you
can
expect
that
to
be
around
whenever
we
can
think
of
a
good
name.
B
A
H
B
B
A
I
I
just
threw
shade
at
kaz
operator,
because
it
first
of
all
it's
the
most
unoriginal
name
and
it
doesn't
have
a
logo
I
did.
That
was
in
my
talk
for
a
patch
con
come
on
we're
not
even
trying
anymore,
we'll
just
use
a
fixed
font
and
move
on
with
life.
So
yeah
I
mean
I
just
general
feel
I
mean
the
thing
that
I
felt
after
many
conversations
last
week
is
we're
a
lot
closer
to
shipping
4.0
than
we
thought
is
that
fair.
A
A
Because
I
was
serious
in
that
mail,
I
I
would
really
love
to
stick
it
to
2020
and
ship
this
year,
just
because
I
need
something
good
this
year.
I
don't
know
about
you
all,
but
this
hasn't
been
a
fun
year.
I
feel
like.
I
need
to
end
on
a
good
note
and
right
now
this
is
pretty
much
all.
I
hope.
I'm
hinging
all
my
hopes
on
right
now.
You
are
tying
this
project
to
2020.
In
any
way,
you.
B
B
Yeah,
I
think,
in
terms
of
next
steps,
I
don't
want
to
volunteer
the
other
2js
for
things
they
don't
want
to
volunteer
for,
but
we
were,
we
were
putting
energy
into
the
project
management
side
of
things
before
and
I'd
be
I'd
be
happy
to
do
that
again.
In
terms
of
the
whole
add
a
new
fix
version,
let's
opt
in
for
what
we
want
to
do.
Let's
get
our
status
updates
out
prune
the
shepherds,
all
that
I'm
okay,
helping
take
on
that
mantle
of
other
people
are
as
well
so.
A
B
A
C
B
K
K
What
would
a
broad
ask
of
the
community
to
say,
as
we
lead
up
to
the
affordable
release,
if
you
want
to
find
a
way
to
contribute?
One
thing
you
can
do
is
anonymize
your
data
model
and
contribute
that
to
a
github
repo,
that's
separate
from
the
project
to
say:
let's
go
through
and-
and
I
don't
know
if
this
is
too
broad,
but
maybe
have
some
selective
selection
of
selective
criteria
from
a
shepherd
like
what
you
guys
have
been
talking
about
to
say.
K
We
get
as
far
as
we
can
with
the
the
testing,
but
we
don't
know
one
of
the
one
of
the
things
that
is
more
exotic
that
comes
in
in
the
four-point
part
like
the
the
1.2.3
bugs
is
oh
wow.
We
didn't
realize
that
this
upgrade
scenario
with
this
data
model
would
be
problematic,
or
something
like
that
is
that
reaching
at
straws
here
or
is
that
something
that
would
be
helpful
for
for
the
separate
now
that
we
have
like
data
generative
tools
and
testing
tools
that
allow
us
to
do
some
of
this?
K
D
That's
a
ideal
goal
we
want
to
get
to.
I
would
even
add
that,
on
top
of
capturing
data
models,
we'd
want
to
capture
the
shape
of
people's
rights
and
queries,
because
often
we
find
those
edge
cases
are
some.
We,
like
reverse
iteration
on
some
weird
boundary,
mixed
with
exactly
the
things
that
you
mentioned.
D
K
D
Absolutely,
and
I
think
the
idea
there
is
right
now
harry
just
pulls
from
a
uniform
distribution.
I
don't
work
on
harry
day
today,
so
alex
and
them
may
tell
me
I'm
missing
something
horrible
here,
but
in
my
mind
and
the
parts
that
I
have
used,
it
should
be
possible
to
feed
it
a
different
class
that
pulls
from
a
distribution
that
exactly
what
you
said
has
been
built
from
scanning.
B
D
B
Data
yeah
suspect
the
modification
fql
tool
may
give
us
the
ability
to
do
live
profiling
of
like
cardinality
and
iteration
direction.
Things
like
that
without
actually
dumping
the
binary
content
itself.
I
haven't
looked
at
it,
so
I
am
arguably
probably
very
wrong
on
some
points
there
as
well,
but
profiling.
Those
aspects
of
a
workload
to
feed
into
a
generator
shouldn't
be
rocket
science.
I'm
just
gonna
apply
energy
to
it.
B
B
Yeah,
I
think
we're
we're
probably
going
to
need
to
as
a
community
figure
out
what
we
want
to
do
from
that
front,
because
my
understanding
is
that
jean
luca
he's
the
engineer
that's
working
on
this
took
a
look
at
nosql
bench
and
at
least
the
the
usability
and
its
initial
incarnation
of
trying
to
get
generative
workloads
based
on
schemas
was
prohibitively
complex,
assuming
the
functionality
was
actually
there.
I
think
shooky
jonathan
chuck
is
actually
working
on
that
right
now,
so
I
mean
there's,
there's
moving
parts.
K
Sure
would
somebody
want
to
shepherd
that,
like
like
this
data
model
collection
of
of
type
of
thing,
I
think
there's
some
management
to
that
to
to
make
it
useful
and
then
put
that
into
the
machinery
of
of
the
harry
and
other
things
so,
like,
I
think,
there's
the
collection
and
that's
the
easy
part.
I
think,
but
it
but
important
to
make
it
simplistic
enough
for
people
to
contribute
on
a
wide
basis
and
then
there's
the
curation
and
there's
putting
it
and
adapting
it
to
the
machinery.
That
is
the
testing.
H
I
have
a
bunch
of
data
models
that
I've
been
collecting,
because
you
know
I
mean
if
you
work
in
the
practice.
It's
like
that's.
Essentially
the
80
of
the
in
a
failure.
Is
this
data
model
right,
so
I
can
lend
a
hand
with
the
shepherding.
I
don't
have
the
bandwidth
to
do
the
the
whatever
hairy
or
nosql
kind
of
test
cases
around
it.
H
H
K
And
I,
and
I'm
not,
the
intent
is
not
to
add
more
kind
of
work
creep
into
the
finalization
of
the,
but
I
was
thinking
of
of
things
that
I've
seen
in
the
past
that
have
been
problematic
on
on
the
initial
release
that
we
can
mitigate
and
also
encourage
contribution
in
a
simplistic
way
as
we
get
closer.
So
I
I'm
not
trying
to
add
to
the
the
work
that
needs
to
be
done
for
the
release.
That's
absolutely
not
the
the
goal
there.
A
Is
this
a
good?
I
think
this
might
be
a
good
opportunity
to
take
this
to
a
discuss
thread
on
the
dev
list,
just
to
broaden
the
net
and
jeremy.
I
think
you
what
you've
outlined
is
great.
It
may
be
too
much
of
an
effort
too
soon
or
I'm
not
sure,
you're
right,
you
could
get
in
the
way,
but
you
know
there
are
a
very
few
people
on
this
call
to
say
that
this
is
an
exciting
factor.
Now,
let's,
let's
open
it
up
as
a
discuss.
K
D
Yeah
two
things:
I've
I'd
add
I
I
think
this
is
a
goal
that
we
should
get
to.
It
may
not
be
in
the
4-0
cycle,
but
regardless,
I
think
it
will
help.
You
know
towards
this
idea
of
us
wanting
to
have
a
better
definition
of
done.
You
know
saying
that
we
run
whatever
changes
through
an
arsenal
of
real
users,
schemas
and
queries,
etc,
will
really
up
the
game
in
terms
of
like
cassandra,
quality
and
stability,
and
then
the
other
thing
it
definitely.
I
don't.
D
I
think
there
is
a
significant
amount
of
work
to
get
to
that
point
from
the
sort
of
like
primitives.
We
have
right
now
it's
non-trivial,
but
we
may
find
if
we
do
better
define
the
work
in
the
testing
ethics
that
a
lot
of
what
we
want
to
test
is
covered
by
that.
So
you
know
we
may
find
that
we
kind
of
knock
out
a
whole
bunch
of
testing
by
accomplishing
it.
So
I
think
it
kind
of
goes
multiple
ways.
A
I
would
also
pile
on
fallout
into
this
same
type
of
thing,
define
something
that
would
break
cassandra.
It's
a
little.
It's
not
data
model
specifically,
but
fallout
any
kind
of
programmatic
defined
testing
tool.
There's
there's
some
cool
bug,
boundary
kind
of
stuff
that
you
could
do
there
here,
define
it.
Oh
you
found
something
that
really
broke
cassandra.
Congratulations!
Here's
some
dough.
K
Yeah
and
this
and
like
I
think
it's
a
good
point
to
say
that
this
isn't
this
isn't
on
the
critical
path
to
the
release,
but
it's
this
could
be
a
broader
effort
to
just
say
you
know
we
could
add
to
our
library
of
things
that
could
like
with
fallout
one
with
this
generation,
and
things
like
that.
This
can
this
could
help
with,
because
I
think
anybody
in
the
project-
and
I'm
hoping
this-
this
comes
out
on
the
discussion
thread-
is
that
anybody
in
the
project-
this
isn't
like
a
new
feature.
This
isn't
a
cep.
K
D
or
maybe
a
good
exam,
just
I
guess
in
the
sense
of
saying,
like
you
know,
I
think,
there's
some
something
to
be
said
for
like
putting
in
more
effort
into
testing
as
we
go
forward
and
not
just
saying
like
okay,
we've
reached
this
like
new,
you
know
status
quo
for
40
and
it's
what
we
need
for
the
future,
but
either
way.
I
think
it
would
be
a
great
addition
over
time.
I
don't.
I
don't
know
where
it
falls
in
terms
of
release
cycle.
A
D
A
A
That's
another
big
one
melissa,
and
I
will
be
talking
about
that
shortly.
Today.
We've
already
been
thinking
back
and
forth
like
let's
get
on
this
and
then
the
other
one
was
was
jeremy's,
discuss,
thread
topic
on.
You
know
the
testing.
How
do
we?
How
do
we
improve
testing
and
use
a
contributed
test?
A
I
will
have
the
transcripts
well,
my
virtual
assistant
will
have
the
transcripts
done
shortly,
hopefully,
and
then
I'll
get
those
posted
up
into
the
c
wiki
and
I'll
get
this
posted
on
the
youtube
channel,
planet,
cassandra,
and
so
everyone
can
see
what
happened,
but
thanks
again,
everyone
for
showing
up
good
participation
today,
we'll
do
it
when
needed.
We
won't
schedule
it
just
yet,
but
as
needed
thanks
everyone.