Agreed. That's how I have been handling this. Either a change is committed to all lines at the same time (i.e. within a day or so), or there should be separate back or (rarely) forward porting jiras.
-- Lars ________________________________ From: Nicolas Liochon <nkey...@gmail.com> To: dev@hbase.apache.org Sent: Monday, July 29, 2013 9:38 AM Subject: 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 <yuzhih...@gmail.com> 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 <lars.geo...@gmail.com> > 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 <nkey...@gmail.com> 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 <lars.geo...@gmail.com> > > wrote: > > > > > >> Hi, > > >> > > >> Sorry to ask this lame question, but what is our policy of setting a > > >> "Resolved" issue to "Closed"? > > >> > > >> Thanks, > > >> Lars > > >> > > >> > > > > >
