Home | About | Sematext search-lucene.com search-hadoop.com
 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 11:06 AM, Lars George <[EMAIL PROTECTED]> 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?

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)