I think once RM releases, he will mark that JIRA to closed state and also which can not be reopened again. Only option will be to file new JIRA and track for next release. Where as in 'Resolved' case we can reopen the issue and fix on same JIRA as that might not included in any release yet. This is what my understanding, but I might be wrong as did not read this anywhere documented :-)
Regards, Uma -----Original Message----- From: Lars George [mailto:lars.geo...@gmail.com] Sent: 30 July 2013 02:11 To: dev@hbase.apache.org Subject: Re: Resolved JIRAs Hi Andy, OK, makes sense. Is that something defined somewhere, or more or less common sense, or somehow passed on verbally only? Cheers, Lars On Jul 29, 2013, at 9:19 PM, Andrew Purtell <apurt...@apache.org> wrote: > On Mon, Jul 29, 2013 at 11:06 AM, Lars George <lars.geo...@gmail.com> wrote: > >> That is exactly my point, ie the former case. If I commit to all >> major branches within a day as is common, but the branches release at >> various times, who is going to close the issue? The release manager >> who releases first? > > > IMHO: > > The commiter should set the state to 'Resolved' after the change is > applied to all desired target branches. > > The RM for the _last_ affected release should set the state to > 'Closed', essentially garbage collecting when refcount goes to 0. > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet > Hein (via Tom White)
