Doug Cutting wrote:
Chris Mattmann wrote:
+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?
In Hadoop, most developers can resolve but not close. Only members of
a separate Jira group (hadoop-admin a subset of hadoop-developers) are
permitted to close bugs. Note that the Jira group hadoop-developers
has far more members than Hadoop has committers.
But the nutch-developers Jira group pretty closely corresponds to
Nutch's committers, so perhaps all committers should be permitted to
close, although this should be exercised with caution, only at
releases, since closes cannot be undone in this workflow.
If closing is supposed to happen only at the release, then the release
engineer (whoever that is) should be the one to have this 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 the last time that we had to re-open
an issue ... not that often, even though we usually do "resolve AND
close". So perhaps we can live with this limitation.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __________________________________
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at sigram dot com
