Hi All, Right now I found myself facing a bit of a dilemma w.r.t "bumping on" the issues for the next Nutch release.
Currently due to legacy workflows, we have some 120 issues assigned for 1.6... however ALL issues have been addressed for 1.6 meaning that the 120 issues are for > 1.6 however not necessarily for 1.7. A suggestion from myself, can I mark these issues as no fix version? This means that we can carve/manufacture the next development drive to what developers want to fix and to what features requests we receive from the community rather than sitting with a constant pile of issues which are always for the next development drive. Additionally, may I suggest (and please shoot me down here if I sound cheeky) that we make it a priority in the next development drive, to harness the issues which are marked as patch submitted? It seems to be a waste for such issues to be stagnating. I am conscious that this comment may sound wide of me, this is not the intention, I do think however that it would be nice to work our way towards Nucth releases in a more strategic manner than we have been doing. Hopefully this proposal is a step in the right direction. Thanks for any feedback. The issue at the top I suppose is the most important one in the short term. best Lewis -- Lewis
