hoss mentioned on IRC that steve will re-spin later in his night I will
backport the fix for LUCENE-5120 to the release branch.

simon


On Thu, Jul 18, 2013 at 11:30 PM, Simon Willnauer <[email protected]
> wrote:

> if we re-spin we might want to take LUCENE-5120 into account as well?
>
> simon
>
>
> On Thu, Jul 18, 2013 at 3:27 PM, Mark Miller <[email protected]>wrote:
>
>> Bah. You are right. We should respin for this.
>>
>> I'll update it.
>>
>> - Mark
>>
>> On Jul 18, 2013, at 1:06 AM, Jack Krupansky <[email protected]>
>> wrote:
>>
>> > -1
>> >
>> > In the Solr example solrconfig.xml:
>> >
>> >   <luceneMatchVersion>LUCENE_43</luceneMatchVersion>
>> >
>> > That should be:
>> >
>> >   <luceneMatchVersion>LUCENE_44</luceneMatchVersion>
>> >
>> > Otherwise the 4.4 changes to the EdgeNGramTokenizer/Filter are disabled
>> in the Solr example config.
>> >
>> > See:
>> >
>> > https://issues.apache.org/jira/browse/LUCENE-3907
>> > (Eliminated side="back").
>> >
>> > -- Jack Krupansky
>> >
>> > -----Original Message----- From: Steve Rowe
>> > Sent: Tuesday, July 16, 2013 2:32 AM
>> > To: [email protected]
>> > Subject: [VOTE] Release 4.4
>> >
>> > Please vote to release Lucene and Solr 4.4, built off revision 1503555
>> of <https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_4_4
>> >.
>> >
>> > RC0 artifacts are available at:
>> >
>> >
>> http://people.apache.org/~sarowe/staging_area/lucene-solr-4.4.0-RC0-rev1503555
>> >
>> > The smoke tester passes for me.
>> >
>> > Here's my +1.
>> >
>> > Steve
>> > ---------------------------------------------------------------------
>> > 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]
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>

Reply via email to