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
It's my understanding as well. I think exceptions are tolerated (the first
RM to release being the only one to close), but I may be wrong.
On Mon, Jul 29, 2013 at 3:57 PM, Ted Yu <[EMAIL PROTECTED]> wrote:

> Since different branches have their own release cycles, my understanding is
> that different JIRA(s) should be opened for the respective branch(es) on
> the same fix.
> This way, RM can close the issue independently.
>
> Cheers
>
> On Mon, Jul 29, 2013 at 6:46 AM, Lars George <[EMAIL PROTECTED]>
> wrote:
>
> > Hi Nicholas,
> >
> > Wait, what if the issue is against multiple branches which are still
> > maintained and released? Who is closing the issue then?
> >
> > Lars
> >
> > On Jul 29, 2013, at 3:18 PM, Nicolas Liochon <[EMAIL PROTECTED]> wrote:
> >
> > > Hi Lars,
> > >
> > > The committer changes the value to resolved when the patch is
> committed.
> > > The release manager changes the value to closed when the version which
> > > includes the fix is released.
> > >
> > > Cheers,
> > >
> > > Nicolas
> > >
> > >
> > > On Mon, Jul 29, 2013 at 3:06 PM, Lars George <[EMAIL PROTECTED]>
> > wrote:
> > >
> > >> Hi,
> > >>
> > >> Sorry to ask this lame question, but what is our policy of setting a
> > >> "Resolved" issue to "Closed"?
> > >>
> > >> Thanks,
> > >> Lars
> > >>
> > >>
> >
> >
>
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