Home | About | Sematext search-lucene.com search-hadoop.com
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
 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 Mar 28, 2012, at 2:14 PM, Aaron T. Myers wrote:

> On Wed, Mar 28, 2012 at 1:57 PM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>
>> On on hand, we've historically bumped the version number for trunk (i.e.
>> 3.0.0-SNAPSHOT). This has the nice property that when we do cut a release
>> branch off trunk we don't have to scramble to change fix-versions on all
>> the jiras committed to trunk from 'trunk' to X.0.0. Since I've done my fair
>> share of jira manipulation for releases as the RM, as recently as last
>> night, it's nice to not force the burden on the RM for branch-3.
>>
>
> I don't think you'd have to change all the JIRAs. You'd just have to change
> the name of the "trunk" JIRA version to whatever the right number is, and
> then create a new version in JIRA also named "trunk." This would serve the
> same purpose, without having to update any individual JIRAs.
Ah, I didn't know that, thanks for the tip. That alleviates my concerns.

Arun

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
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