While having a solution for known bugs, leaving them unfixed should not be an option. +1 for #1 DIGY
-----Original Message----- From: George Aroush [mailto:geo...@aroush.net] Sent: Tuesday, January 05, 2010 3:31 PM To: lucene-net-dev@lucene.apache.org Subject: RE: Status of Lucene.Net 2.9.1 Looks like Lucene Java 2.9.2 is on its way. See: http://mail-archives.apache.org/mod_mbox/lucene-java-dev/201001.mbox/%3c023801ca8e05$ae8bf930$0ba3eb...@net%3e In this case, my vote is we do option #1, port over patches for Lucene 2.9.2. -- George -----Original Message----- From: George Aroush [mailto:geo...@aroush.net] Sent: Tuesday, January 05, 2010 12:02 AM To: lucene-net-dev@lucene.apache.org Subject: RE: Status of Lucene.Net 2.9.1 I looked over LUCENE-2190 earlier today, and the port should be easy (and I see that Mike already completed the port in LUCENE-2190, thanks Mike!) If we are going to do this, then let us go all the way and port over fixes made to 2.9.2; the list is here: https://issues.apache.org/jira/browse/LUCENE/fixforversion/12314342 I just completed examining the current list, and the associated patches, they are easy to port over. We should be able to get them done in less than a week. My concern is, if we only port over LUCENE-2190, then Lcuene.Net 2.9.1 is now Lucene.Net 2.9.1.1 (i.e.: not a 1-to-1 version match). If we are going to port over fixes made to Lucene Java 2.9.2, then we need to find out the release schedule for Lucene Java 2.9.2 which as far as I know, there isn't one (see: http://mail-archives.apache.org/mod_mbox/lucene-java-dev/201001.mbox/%3c00b101ca8dbb$7be61f00$73b25d...@net%3e). So, the way I see it, we have 3 options: 1) Port over Lucene Java 2.9.2 and tag it as such. 2) Port over LUCENE-2190 only and call this Lucene.Net 2.9.1.1. 3) Release Lucene.Net 2.9.1 as-is (do not port over LUCENE-2190, or anything else, just bug fixes related to porting). My vote is for #1 (but I would like to see what folks on the Java side will say) followed with #2. -- George -----Original Message----- From: Michael Garski [mailto:mgar...@myspace-inc.com] Sent: Monday, January 04, 2010 4:03 PM To: lucene-net-dev@lucene.apache.org Subject: RE: Status of Lucene.Net 2.9.1 I'll check it out more in detail this week as I am making some changes to our CustomSoreQuery implementations, and will open an item and post a patch then. If anyone else wants to take a crack at it in the interim, go for it. Michael -----Original Message----- From: Digy [mailto:digyd...@gmail.com] Sent: Monday, January 04, 2010 1:00 PM To: lucene-net-dev@lucene.apache.org Subject: RE: Status of Lucene.Net 2.9.1 Not yet. Any help is welcome :-) DIGY -----Original Message----- From: Michael Garski [mailto:mgar...@myspace-inc.com] Sent: Monday, January 04, 2010 10:53 PM To: lucene-net-dev@lucene.apache.org Subject: RE: Status of Lucene.Net 2.9.1 I think that's a great idea - are you working on a parch for it? Michael -----Original Message----- From: Digy [mailto:digyd...@gmail.com] Sent: Monday, January 04, 2010 12:50 PM To: lucene-net-dev@lucene.apache.org Subject: RE: Status of Lucene.Net 2.9.1 Maybe, this issue can be incorporated in 2.9.1 https://issues.apache.org/jira/browse/LUCENE-2190 DIGY -----Original Message----- From: George Aroush [mailto:geo...@aroush.net] Sent: Monday, January 04, 2010 3:32 AM To: lucene-net-dev@lucene.apache.org Subject: Status of Lucene.Net 2.9.1 Hi folks, Happy New Year! So what's the status of 2.9.1? Are there any outstanding issues need to be resolved? Has folks been giving it a try? We need to close this loose end loop and if there is no outstanding issues, officially release Lucene.Net 2.9.1 so work can start on 3.0 and beyond. My suggestion is, we announce it on the lucene-net-u...@lucene.apache.org list and then start the packaging process for an official release. If I hear no objection by 1/9/2010, I will start the process. Regards, -- George
