Hey Lewis, On Nov 29, 2012, at 5:54 AM, Lewis John Mcgibbney wrote:
> 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. I would just set them for 1.7. I just use N+1 as the next release whether or not we actually plan to solve them for 1.7. Then when 1.7 comes along you can bump those 1.7s that we didn't get to, to 1.8, etc. > > 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. Marking them as no fix version destroys pretty important reporting that I like to use which is pulling up a list of all the upcoming issues of relevance set for the next release. Without setting a Fix version you have to use the other JIRA search tools to search by things other than next version. > > 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. +50. That was one of my keys to success when I had more time. I would look for issues sitting with patches and just commit them. If I can wrangle some Nutch time over Christmas, I'll do a bunch of this as well. :) > > Thanks for any feedback. The issue at the top I suppose is the most > important one in the short term. Cheers my friend. Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
