quick look at JIRA, tried editing an issue, but didn't see the status
option anywhere.
Otis
- Original Message
From: Chris Mattmann <[EMAIL PROTECTED]>
To: "nutch-dev@lucene.apache.org"
Sent: Tuesday, August 15, 2006 4:18:28 PM
Subject: Patch Available status?
Hi
this workflow.
>
> Another alternative would be to construct a new workflow that just adds
> the "Patch Available" status and still permits issues to be re-opened.
>
> Which sounds best for Nutch?
Good question. Well, my personal preference would be for one that allows
issue cl
rkflow.
>
> Another alternative would be to construct a new workflow that just adds
> the "Patch Available" status and still permits issues to be re-opened.
>
> Which sounds best for Nutch?
Good question. Well, my personal preference would be for one that allows
issue closes t
Another alternative would be to construct a new workflow that just
adds the "Patch Available" status and still permits issues to be re-
opened.
+1
right, and
perhaps 1 other person if the RE person is unavailable.
Another alternative would be to construct a new workflow that just
adds the "Patch Available" status and still permits issues to be
re-opened.
Which sounds best for Nutch?
I'm trying to remember when it was t
hould be permitted to
close, although this should be exercised with caution, only at releases,
since closes cannot be undone in this workflow.
Another alternative would be to construct a new workflow that just adds
the "Patch Available" status and still permits issues to be re-opened.
Chris Mattmann wrote:
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?
+1
Regards,
Uros
Cheers,
Chris
On 8/30/06 3:14 PM, "And
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" <[EMAIL PROTECTED]> wrote:
> Do
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 h
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-defa
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
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? I tried doing this, but I don't think I
12 matches
Mail list logo