+1 - next should be nuked, the issues should simply be plopped into the next likely release and dealt with (done, moved, pushed) before release.
On May 5, 2011, at 3:24 PM, Chris Hostetter wrote: > > : > We should definitely kill of "Next" ... i would suggest just removing it, > : > and not bulk applying a new version (there is no requirement that issues > : > have a version) > ... > : Based on that, I think it would be irresponsible to just delete "Next" > : because any issues assigned to this version on the basis of that > : description (like SOLR-2191) is going to be dropped on the floor. > > Of course you're right ... i was thinking about it from a "what's the > minimum that must be done in order to eliminate a version, but that > doesn't mean it would leave those issues in a good state. > > Doing a little more reading about Jira version management, I realized that > Jira allows Versions to be "merged" > > I suggest we marge "Next" into "3.2" ... > > http://confluence.atlassian.com/display/JIRA/Managing+Versions#ManagingVersions-Mergingmultipleversions > > > ...objections? > > > > -Hoss > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > - Mark Miller lucidimagination.com Lucene/Solr User Conference May 25-26, San Francisco www.lucenerevolution.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
