Finally catching up to this.
I'll take your suggestions and improve the copy for the release ann.
{quote}Also, should we clean up CHANGES.txt to fix entries that were
obsoleted by more recent commits? EG we still have this:
7. LUCENE-1483: Added new MultiReaderHitCollector which enables faster
hit collection by notifying the collector for each sub-reader
that's visited. All core collectors now use this API. (Mark
Miller, Mike McCandless) {quote}
I hadn't kept up enough in this area to even know this was outdated -
thanks, I'll get it - as soon as we figure out...
bq.
Causing a
cascaded renumbering... I think we should stop numbering CHANGES
entries?
+1. I've had to renumber plenty and the benefit is so limited. If you
really want numbering, a tool like the changes2html could still add the
numbers - no reason to have them in changes though - the issue already
has a good id.
Anyone really want to keep the numbers?
--
- Mark
http://www.lucidimagination.com
Michael McCandless wrote:
> Maybe add:
>
> * Scoring is now optional when sorting by Field, or using a custom
> Collector, gaining sizable performance when scores are not
> required.
>
> * New analyzers (at least PersianAnalyzer, ArabicAnalyzer,
> SmartChineseAnalyzer). Robert are there others?
>
> * New fast-vector-highlighter
>
> I would also separately call out "handling of numerics" as its own
> bullet, instead of grouping under "new query types", something like:
>
> * Lucene now includes high-performance handling of numeric fields.
> Such fields are indexed with a trie structure, enabling simple to
> use and much faster numeric range searching without having to
> externally pre-process numeric values into textual values.
>
> Also, should we clean up CHANGES.txt to fix entries that were
> obsoleted by more recent commits? EG we still have this:
>
> 7. LUCENE-1483: Added new MultiReaderHitCollector which enables faster
> hit collection by notifying the collector for each sub-reader
> that's visited. All core collectors now use this API. (Mark
> Miller, Mike McCandless)
>
> I think we can just absorb it into the LUCENE-1575 entry? (Causing a
> cascaded renumbering... I think we should stop numbering CHANGES
> entries?).
>
> Mike
>
> On Sun, Aug 30, 2009 at 6:43 PM, Mark Miller<markrmil...@gmail.com> wrote:
>
>> I started trying out a list of sample features in the RC release emails,
>> but its really just a quick hack I pulled out. If anyone has any
>> suggestions of what they would like to see incorporated into the final
>> release feature list, let me know. Not the most import thing in the
>> world I know, but as a lover of a good feature/changes list, I'd like
>> the sample features to lure you in :)
>>
>> One large omission that I will be adding: spatial contrib
>>
>> If you have any suggestions/comments, please attach to this thread. Any
>> corrections as well - sometimes its hard to summarize some of this stuff
>> I've never really looked that hard at. To be honest, its hard to
>> summarize the stuff I have looked a lot at sometimes :)
>>
>> --
>> - Mark
>>
>> http://www.lucidimagination.com
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: java-dev-h...@lucene.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: java-dev-h...@lucene.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
