Re: [discuss] Modernization of Cassandra build system

2015-04-02 Thread Pierre Devops
Hi all, Not a cassandra contributor here, but I'm working on the cassandra sources too. This big cassandra source root caused me trouble too, firstly it was not easy to import in an IDE, try to import cassandra sources in netbeans, it's a headcache. It would be great if we had more small modules

Re: [discuss] Modernization of Cassandra build system

2015-04-02 Thread Benedict Elliott Smith
There are three distinct problems you raise: code structure, documentation, and build system. The build system, as far as I can tell, is a matter of personal preference. I personally dislike the few interactions I've had with maven, but gratefully my interactions with build system innards have bee

Re: [discuss] Modernization of Cassandra build system

2015-04-02 Thread Robert Stupp
TL;DR - Benedict is right. IMO Maven is a nice, straight-forward tool if you know what you’re doing and start on a _new_ project. But Maven easily becomes a pita if you want to do something that’s not supported out-of-the-box. I bet that Maven would just not work for C* source tree with all the

Re: March 2015 QA retrospective

2015-04-02 Thread Philip Thompson
To add to this: *Went well* Tyler Hobbs has reduced failing dtests on trunk by ~90%. By next month, test results should be at 100% pass. *Went poorly* We've failed to make progress on running the full test suite across all contributor branches. By the end of this month, I assume we will at least

Re: 3.0 and the Cassandra release process

2015-04-02 Thread Jonathan Haddad
In this tick tock cycle, is there still a long term release that's maintained, meant for production? Will bug fixes be back ported to 3.0 (stable) with new stuff going forward to 3.x? On Thu, Mar 26, 2015 at 6:50 AM Aleksey Yeschenko wrote: > Hey Jason. I think pretty much everybody is on board

Re: 3.0 and the Cassandra release process

2015-04-02 Thread Jonathan Ellis
We are moving away from designating major releases like 3.0 as "special," other than as a marker of compatibility. In fact we are moving away from major releases entirely, with each release being a much smaller, digestible unit of change, and the ultimate goal of every even release being productio

Re: 3.0 and the Cassandra release process

2015-04-02 Thread Colin
Hey Jonathan, I have been hoping for this approach for years now-one of the reasons I left Datastax was due to my feeling that quality was always on the backburner and never really taken seriously vs marketing driven releases. I sincerely hope this approach reverses that perceived trend. -- Col