I like Hadoop version of workflow. I do not think that we would have problems with reopenning as issues would not be closed immidiatelly after resolving them. In some extreme situations one can always open a new bug that references closed one. Piotr On 9/1/06, Chris Mattmann <[EMAIL PROTECTED]> wrote: > Hi Doug, > > > > > 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. > > > > 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 to be undone, as I've seen several cases (even some recent ones > such as NUTCH-258) where someone in the nutch-developers group has closed an > issue (including myself) that users in fact don't believe is resolved. > > So my +1 for having the 2nd option above: an alternative workflow to that of > the Hadoop one that simply adds the "Patch Available" status and still > permits issues to be re-opened. > > Just my 2 cents. > > Thanks! > > Cheers, > Chris > > > > > Doug > > >
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Nutch-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nutch-developers
