[jira] Closed: (LUCENE-205) [PATCH] Patches for RussianAnalyzer

2008-01-12 Thread Grant Ingersoll (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll closed LUCENE-205. -- Resolution: Won't Fix Assignee: (was: Lucene Developers) I don't see what this

A bit of planning

2008-01-12 Thread Grant Ingersoll
I can't remember, did we say we are going to go to 2.4 or 2.9 next? I suppose it depends a bit on 2.3, but I generally think we should move onto 2.9 and then 3.0 fairly quickly. Thoughts? -Grant - To unsubscribe, e-mail:

[jira] Updated: (LUCENE-494) Analyzer for preventing overload of search service by queries with common terms in large indexes

2008-01-12 Thread Grant Ingersoll (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll updated LUCENE-494: --- Affects Version/s: 2.4 I think it makes sense to add this in after the 2.3 release.

[jira] Closed: (LUCENE-1104) Clean up old JIRA issues in component Analysis

2008-01-12 Thread Grant Ingersoll (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll closed LUCENE-1104. --- Resolution: Fixed I think the remaining 3 issues are reasonable to keep open Clean up old

Re: A bit of planning

2008-01-12 Thread Michael Busch
I think we said that we wanted a 2.4 release. There are a bunch of issues with Fix Version 2.4. And it would be nice to get them into 2.4 instead of 3.x, because some of them involve fairly big API changes, like LUCENE-584 or LUCENE-831. Then we could get rid of all the deprecated APIs in 3.0 and

[jira] Resolved: (LUCENE-685) Extract interface from IndexWriter

2008-01-12 Thread Grant Ingersoll (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll resolved LUCENE-685. Resolution: Won't Fix Interfaces are hard to maintain from an API perspective and we have

[jira] Resolved: (LUCENE-671) Hashtable based Document

2008-01-12 Thread Grant Ingersoll (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll resolved LUCENE-671. Resolution: Won't Fix Hashtable based Document

Re: Javadocs and Nightly Builds

2008-01-12 Thread Michael Busch
Cool, thanks Grant! Grant Ingersoll wrote: Sorry, missed that one. I put it in and ran the script. Should propagate in an hour or so. -Grant On Jan 12, 2008, at 4:50 PM, Michael Busch wrote: Grant Ingersoll wrote: Done. For the record, the script runs: It works fine! I just

[jira] Resolved: (LUCENE-737) Provision of encryption/decryption services API to support Field.Store.Encrypted

2008-01-12 Thread Grant Ingersoll (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll resolved LUCENE-737. Resolution: Won't Fix Lucene Fields: [Patch Available] (was: [Patch Available,

[jira] Commented: (LUCENE-685) Extract interface from IndexWriter

2008-01-12 Thread Kenny MacLeod (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12558315#action_12558315 ] Kenny MacLeod commented on LUCENE-685: -- Interfaces in APIs are hard to manintain...

Re: A bit of planning

2008-01-12 Thread Chris Hostetter
: Hmm, actually this is probably too restrictive. But maybe we could say : that Lucene 3.0 doesn't have to be able to read indexes built with : versions older than 2.0? that is in fact the position that lucene has had since as long as i've ben involved with it...

Re: A bit of planning

2008-01-12 Thread Michael Busch
Chris Hostetter wrote: : Hmm, actually this is probably too restrictive. But maybe we could say : that Lucene 3.0 doesn't have to be able to read indexes built with : versions older than 2.0? that is in fact the position that lucene has had since as long as i've ben involved with it...

[jira] Commented: (LUCENE-400) NGramFilter -- construct n-grams from a TokenStream

2008-01-12 Thread Steven Rowe (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12558350#action_12558350 ] Steven Rowe commented on LUCENE-400: Lucene has *character* NGram support, but not

Hudson build is back to normal: Lucene-Nightly #336

2008-01-12 Thread hudson
See http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/336/changes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]