Apologies. I had seen only that the status had changed to closed but removing the fix version definitely did the trick.
+1 for releasing Thanks Lewis On 21 June 2013 21:46, Lewis John Mcgibbney <[email protected]>wrote: > I merely removed the fix for version numbers for the issues. > Anyone is free to amend the various issues and do this now. I am on mobile > and Jira does not render well in my browser. > Can you please see to this? > Thank you > > > On Fri, Jun 21, 2013 at 12:54 PM, Julien Nioche < > [email protected]> wrote: > >> Hi Lewis >> >> I don't think you got my comment. I was saying that won't fix is the right >> resolution for these issues but that the report should not include them. >> In >> the case of these issues ppl might get the wrong idea by looking at the >> report and think that we included the mongodb related stuff in the next >> release which we don't. >> >> J. >> >> >> On 21 June 2013 19:41, Lewis John Mcgibbney <[email protected] >> >wrote: >> >> > Hi Julien, >> > Done, thanks for the attention to detail. >> > I wonder if you got to check sigs as well? I have been dancing between >> > machines and it would be excellent to verify. >> > Thank you v much. >> > Lewis >> > >> > >> > On Fri, Jun 21, 2013 at 1:47 AM, Julien Nioche < >> > [email protected]> wrote: >> > >> > > Hi Lewis >> > > >> > > The release notes [ >> > > >> > > >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10680&version=12323281 >> > > ] >> > > list issues marked as won't fix which is probably not a great idea. >> For >> > > instance it lists >> > > *- Port nutch-mongodb-indexer to Nutch* >> > > which is a won't fix but people could get the impression that it has >> been >> > > committed. Would be good to fix it if we can. >> > > >> > > The code compiles and passes the test. +1 to release >> > > >> > > Thanks >> > > >> > > Julien >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > On 20 June 2013 22:48, lewis john mcgibbney <[email protected]> >> wrote: >> > > >> > > > Hi, >> > > > >> > > > Please VOTE on the release of the Apache Nutch 1.7 artifacts. >> > > > >> > > > As always, we solved a bunch of issues: >> > > > http://s.apache.org/1zE >> > > > >> > > > SVN source tag: >> > > > http://svn.apache.org/repos/asf/nutch/tags/release-1.7/ >> > > > >> > > > Staging repo: >> > > > >> https://repository.apache.org/content/repositories/orgapachenutch-044/ >> > > > >> > > > Release artifacts: >> > > > http://people.apache.org/~lewismc/nutch/nutch1.7/ >> > > > >> > > > PGP release keys (signed using 4E21557F): >> > > > http://nutch.apache.org/dist/KEYS >> > > > >> > > > Vote will be open for at least least 72 hours. >> > > > >> > > > I would like to say a huge thanks all contributors and committers >> from >> > > far >> > > > and wide who helped with this release. Another string to add to the >> > Nutch >> > > > bow. >> > > > >> > > > Best >> > > > >> > > > Lewis >> > > > >> > > > [ ] +1, let's get it released!!! >> > > > [ ] +/-0, fine, but consider to fix few issues before... >> > > > [ ] -1, nope, because... (and please explain why) >> > > > >> > > > p.s. here's my +1 >> > > > >> > > >> > > >> > > >> > > -- >> > > * >> > > *Open Source Solutions for Text Engineering >> > > >> > > http://digitalpebble.blogspot.com/ >> > > http://www.digitalpebble.com >> > > http://twitter.com/digitalpebble >> > > >> > >> > >> > >> > -- >> > *Lewis* >> > >> >> >> >> -- >> * >> *Open Source Solutions for Text Engineering >> >> http://digitalpebble.blogspot.com/ >> http://www.digitalpebble.com >> http://twitter.com/digitalpebble >> > > > > -- > *Lewis* > -- * *Open Source Solutions for Text Engineering http://digitalpebble.blogspot.com/ http://www.digitalpebble.com http://twitter.com/digitalpebble
