Patch Available status?

Chris Mattmann wrote:
> Hi Guys,
> 
>  I've seen on the Hadoop mailing list recently that
there was a new status
> added for issues in JIRA called "Patch
Available" to let committers know
> that a patch is ready for review to commit. How about
we add this to the
> Nutch jira instance as well? 

+1

I tried doing this, but I don't think I have
> the permissions to do so.

I am not able to do it either, or then I just don't know
how, can Doug 
help us here?

--
  Sami Siren

Sami Siren wrote:
> I am not able to do it either, or then I just don't
know how, can Doug 
> help us here?

This requires a change the the project's workflow.  I'd be
happy to move 
Nutch to use the workflow we use for Hadoop, which supports
"Patch 
Available".

This workflow has one other non-default feature, which is
that bugs, 
once closed, cannot be re-opened.  This works as follows:
Only project 
administrators are allowed to close issues.  Bugs are
resolved as 
they're fixed, and only closed when a release is made. 
This keeps the 
release notes Jira generates from changing after a release
is made.

Would you like me to switch Nutch to use this Jira workflow?

Doug

Doug Cutting wrote:
> Sami Siren wrote:
>> I am not able to do it either, or then I just
don't know how, can 
>> Doug help us here?
>
> This requires a change the the project's workflow. 
I'd be happy to 
> move Nutch to use the workflow we use for Hadoop, which
supports 
> "Patch Available".
>
> This workflow has one other non-default feature, which
is that bugs, 
> once closed, cannot be re-opened.  This works as
follows: Only project 
> administrators are allowed to close issues.  Bugs are
resolved as 
> they're fixed, and only closed when a release is made.
 This keeps the 
> release notes Jira generates from changing after a
release is made.
>
> Would you like me to switch Nutch to use this Jira
workflow?

+1, this would finally make sense with the
"resolved" vs. "closed" ...

-- 
Best regards,
Andrzej Bialecki     <><
 ___. ___ ___ ___ _ _   __________________________________
[__ || __|__/|__||\/|  Information Retrieval, Semantic Web
___|||__||  \|  ||  |  Embedded Unix, System Integration
http://www.sigram.com 
Contact: info at sigram dot com

Hi Doug and Andrzej,

  +1. I think that workflow makes a lot of sense. Currently
users in the
nutch-developers group can close and resolve issues. In the
Hadoop workflow,
would this continue to be the case?

Cheers,
  Chris



On 8/30/06 3:14 PM, "Andrzej Bialecki"
<abgetopt.org> wrote:

> Doug Cutting wrote:
>> Sami Siren wrote:
>>> I am not able to do it either, or then I just
don't know how, can
>>> Doug help us here?
>> 
>> This requires a change the the project's workflow.
 I'd be happy to
>> move Nutch to use the workflow we use for Hadoop,
which supports
>> "Patch Available".
>> 
>> This workflow has one other non-default feature,
which is that bugs,
>> once closed, cannot be re-opened.  This works as
follows: Only project
>> administrators are allowed to close issues.  Bugs
are resolved as
>> they're fixed, and only closed when a release is
made.  This keeps the
>> release notes Jira generates from changing after a
release is made.
>> 
>> Would you like me to switch Nutch to use this Jira
workflow?
> 
> +1, this would finally make sense with the
"resolved" vs. "closed" ...