Now that you point it out Nick and Andy.

It seems to be that we need three branches:
- next major version (2) in trunk
- current major version (1) in a "branch-1" (at some point that was branched of trunk)

- current minor (1.0) in a "branch-1.0". This was branched of a minor branch. From this we create the actual release tags (1.0.0).

So if we want allow working on the next major version while maintaining minor version of the current major version we would not release from trunk. Is that what you are concerned about, Andy?
 From: Andrew Purtell <[EMAIL PROTECTED]>
Sent: Wednesday, April 16, 2014 9:44 PM
Subject: Re: 0.99.0 and 1.0.0 targets in Jira

One thing I would like to make sure of is we do not get into a situation
like Hadoop common where we are no longer making regular releases off of

On Wed, Apr 16, 2014 at 9:40 PM, Nick Dimiduk <[EMAIL PROTECTED]> wrote:
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB