Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
MapReduce >> mail # dev >> Re: [RESULT] - [VOTE] Rename hadoop branches post hadoop-1.x

Copy link to this message
Re: [RESULT] - [VOTE] Rename hadoop branches post hadoop-1.x
On Wed, Mar 28, 2012 at 11:59 AM, Aaron T. Myers <[EMAIL PROTECTED]> wrote:
> On Wed, Mar 28, 2012 at 11:53 AM, Todd Lipcon <[EMAIL PROTECTED]> wrote:
>> Proposal: is it possible to call the JIRA fixVersion "trunk", and then
>> when we branch off trunk to make a release, rename it at that point to
>> "2.1" or "3.0" or whatever it gets called?
> I like this idea. Just to be clear, I think the exact workflow would be:
> 1. Set the version fields to "trunk" if you're not committing the JIRA to
> any current versioned branch.
> 2. When a new release branch is made off of trunk, rename the "trunk" JIRA
> version to whatever the appropriate version number is.
> 3. At the same time as (2), create a new JIRA version also called "trunk".
> 4. Go to 1.
> Is this what you were thinking, Todd?

Yep, that's right.

Todd Lipcon
Software Engineer, Cloudera