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? -- Lars ________________________________ From: Andrew Purtell <[email protected]> To: "[email protected]" <[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 trunk. On Wed, Apr 16, 2014 at 9:40 PM, Nick Dimiduk <[email protected]> wrote: > On Wed, Apr 16, 2014 at 9:28 PM, Jonathan Hsieh <[email protected]> wrote: > > > I'd prefer if we got rid of one -- maybe mark all as 0.99 and remove > 1.0.0. > > When we branch 1.0, we rename 0.99 to 1.0 and create a 1.1-SNAPSHOT > branch > > and make trunk 2.0-SNAPSHOT (or 1.99-SNAPSHOT?). > > > > Wouldn't trunk become 1.1-SNAPSHOT? > > On Wed, Apr 16, 2014 at 9:11 PM, lars hofhansl <[email protected]> wrote: > > > > > I see we have both targets in Jira and some issues targeted to 0.99.0 > and > > > some to 1.0.0. > > > > > > Which one should we use? > > > > > > -- Lars > > > > > > > > > > > -- > > // Jonathan Hsieh (shay) > > // HBase Tech Lead, Software Engineer, Cloudera > > // [email protected] // @jmhsieh > > > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
