You mean -- put it under lucene/CHANGES on both dev. lines? It does make sense to place it in SOLR's file too though because it affects Solr's functionality... Darn. I think I'll just leave it the way it's already done.
Dawid On Sat, Sep 17, 2011 at 6:52 PM, Robert Muir <[email protected]> wrote: > i'd put it where the code is in 3.x, since thats the version where the > change will appear? > > > On Sat, Sep 17, 2011 at 12:30 PM, Dawid Weiss <[email protected]> wrote: >> I was wondering where to place this in CHANGES files -- the issue is >> marked SOLR in Jira, but is in a module on 4.x line... and in the 3.x >> line it is part of Lucene. Any hints how to do it consistently or >> better? >> >> Dawid >> >>> ============================================================================== >>> --- lucene/dev/branches/branch_3x/lucene/CHANGES.txt (original) >>> +++ lucene/dev/branches/branch_3x/lucene/CHANGES.txt Sat Sep 17 16:26:43 >>> 2011 >>> @@ -7,6 +7,9 @@ http://s.apache.org/luceneversions >>> >>> Bug fixes >>> >>> +* SOLR-2762: (backport form 4.x line): FSTLookup could return duplicate >>> + results or one results less than requested. (David Smiley, Dawid Weiss) >>> + >>> * LUCENE-3412: SloppyPhraseScorer was returning non-deterministic results >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > > -- > lucidimagination.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
