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
Zookeeper >> mail # dev >> reviewboard


Hey Ben, if we have multiple patches in the same jira, perhaps we  
should use subtasks and name the review requests accordingly? Does it  
work for the cases you're referring to?

I was wondering, though, what other projects do to maintain the jira  
consistent with respect to discussion on the review board, if  
anything. We should at least post the link to the review board request  
so that we have it documented.

-Flavio

On Jan 9, 2011, at 7:47 AM, Benjamin Reed wrote:

> hey, reviewboard is pretty cool. i'm wonder about conventions to using
> it. the problem is how to correlate the review with the patch. since a
> JIRA number may contain multiple patches, we need a way to identify a
> particular patch. perhaps we should name our patches
> ZOOKEEPER-<JIRA#>_<revision#>, then we can use the patch name when we
> create a review board request. what do you all think?
>
> thanx
> ben

flavio
junqueira

research scientist

[EMAIL PROTECTED]
direct +34 93-183-8828

avinguda diagonal 177, 8th floor, barcelona, 08018, es
phone (408) 349 3300    fax (408) 349 3301

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