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
HBase >> mail # dev >> Resolved JIRAs


Copy link to this message
-
Re: Resolved JIRAs
On Mon, Jul 29, 2013 at 9:30 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:

> As long as we all agree. :)
>
> We have three options:
>
> 1. separate jiras for each version
> 2. last release closes jira
> 3. first release closes jira, separate jiras needed for further changes
>
> It should also be easy to determine which jiras need to be close and be
> able to do that in bulk. That is easy in #1 and #3, but hard for #2.
> #1 and #2 are easier to understand.
> #3 can be confusing.
> #1 is cumbersome.
>
> My vote would remain with #3.
>

+1 on #3.

I added this 'decision' to our refguide (will show next time I push out a
site build -- I need to rig up site push in jenkins).

St.Ack
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