On 6 April 2013 04:43, Dennis Reedy dennis.re...@gmail.com wrote:
On Apr 5, 2013, at 956PM, Peter wrote:
We can't afford to hold up 2.3.0 much longer, the 2.2.0 release has
numerous synchronization bugs, these will become more apparent on multicore
hardware. The longer we wait the more
We created a qa-refactoring branch for concurrency work
On 3 April 2013 22:10, Peter j...@zeus.net.au wrote:
Not a good idea, the qa-refactoring branch was created recently to address
the concurrency bugs in trunk.
- Original message -
On Apr 2, 2013, at 750AM, Peter
Right so we're into brutal tradeoffs aren't we?
It's beginning to smell like none of the available branches are suitable
for doing releases from. So we need a branch that is.
i.e. We shouldn't just pick a branch we have, we should get one sorted and
right now.
What are our chances of pulling
On 6 April 2013 14:44, Dennis Reedy dennis.re...@gmail.com wrote:
On Apr 6, 2013, at 532AM, Dan Creswell wrote:
Right so we're into brutal tradeoffs aren't we?
It's beginning to smell like none of the available branches are suitable
for doing releases from. So we need a branch that is.
Just to clarify:
Dennis Greg are using the 2.2.0 branch from last release to fix Levels
and release 2.2.1
trunk started failing tests after some unrelated changes exposed
synchronization errors in the qa tests, since then
skunk/qa-refactoring is being used to fix synchronization issues
The 2.2 branch is very clean. It starts from release in 2011. Since
then, Dennis applied RIVER-417, added poms for listing at Maven Central,
and applied the Levels fix. I've applied RIVER-149, and that's it.
A few days ago, I set out to see what else from the trunk should be
rolled in for a
At the risk of de-railing the conversation, is there an option to move to
git for Apache Foundation projects such as River? I was long a big
proponent of SVN but I'm now thoroughly converted and can't help but think
this situation wouldn't have occurred if git were in use. (Yes, it's
possible to
On 4/6/2013 7:26 PM, Greg Trasuk wrote:
...
Once we have a stable set of regression tests, then OK, we could
think about improving performance or using Maven repositories as the
codebase server.
...
I think there is something else you need before it would be a good idea
to release any changes
