I agree with Benedict. We have a lot of organizational things going on right now, perhaps we just mark it as deprecated in the docs and reference alternatives in the readme? Then we can put this on a roadmap to revisit post 4.0.
On Fri, May 1, 2020 at 7:50 AM Benedict Elliott Smith <bened...@apache.org> wrote: > I vote to nuke it post-4.0, when we have time to put together a working > group to discuss its replacement. > > On 30/04/2020, 19:21, "Mick Semb Wever" <m...@apache.org> wrote: > > The C* codebase contains the cassandra-stress tool that is seeing less > maintenance and is getting replaced in popularity by other tools in > our community. This raises the question of whether cassandra-stress > still belongs in-tree, and even in the apache project at all, as we > approach 4.0 > > A) Should cassandra-stress be moved out of the main repo to its own > subproject? > > B) Should tlp-stress, and other stress tools, be allowed in as > subprojects? Other examples could be (if proposed) nosqlbench and the > stress tool from Harry. I'm sure there are others too. > > C) Should cassandra-stress be orphaned out of the project altogether, > left in github? > > > It makes sense to raise these questions now as they overlap with the > driver donation thread: how different components and subprojects are > to be managed in the project. Especially in this situation where > external tools have more momentum than the in-tree tool, which only > causes confusion for users. > > regards, > Mick > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
