> > To achieve this, significant modifications will be required to the codebase, > mostly cleaning up existing abstractions. Specifically, we will need to be > able to mock executors, any blocking concurrency primitives, time, filesystem > access and internode streaming. > > The work is – in large part – already complete, with JIRA and PRs to follow > in the coming weeks. Of course, the work is subject to the usual community > input and review, so this does not preclude changes to the work (even > significant ones, if they are warranted). I know a lot of incoming CEP are > likely to be backed up by significant off-list development as a result of the > focus on a shippable 4.0. Hopefully this is just a temporary growing pain, > particularly as we move towards a shippable trunk. > > I hope this work will be of huge value to the project, particularly as we > race to catch up on years of limited feature development. > > JIRA and PRs will follow, but I wanted to kick-off discussion in advance. >
Should target release be 4.1. (not 4.0.x) ? I'd be interested in seeing a rough timeline/plan of how the proposed changes are to be defined in JIRAs and ordered. I'd like to hear a bit more about the test plan. Not so much about how the CEP itself improves testability of the project, but for example the testing required to be in place to introduce the changes of the CEP (and if it already exists, where). My concern is that changing code and tests at the same time risks regressions… And seconding Benjamin's comments… some documentation on how to write a test, and a simple test example, that this CEP then allows us to write would help a lot (a la "working backwards"). --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
