Re: [ANNOUNCE] Apache Solr 6.4.2 released

[Ishan Chattopadhyaya]

Hi Bernd,
Can you please double check?

I downloaded the 6.4.2 tarball and see that they have 6.4.2:

[ishan@ishanvps solr-6.4.2]$ grep -rn "luceneMatchVersion" *|grep
solrconfig.xml
CHANGES.txt:1474:  <schemaFactory class="ClassicIndexSchemaFactory"/> or
your luceneMatchVersion in the solrconfig.xml is less than 6.0
docs/changes/Changes.html:1694:&lt;schemaFactory
class="ClassicIndexSchemaFactory"/&gt; or your luceneMatchVersion in the
solrconfig.xml is less than 6.0
example/files/conf/solrconfig.xml:38:
<luceneMatchVersion>6.4.2</luceneMatchVersion>
example/example-DIH/solr/tika/conf/solrconfig.xml:38:
<luceneMatchVersion>6.4.2</luceneMatchVersion>
example/example-DIH/solr/rss/conf/solrconfig.xml:38:
<luceneMatchVersion>6.4.2</luceneMatchVersion>
example/example-DIH/solr/mail/conf/solrconfig.xml:38:
<luceneMatchVersion>6.4.2</luceneMatchVersion>
example/example-DIH/solr/db/conf/solrconfig.xml:38:
<luceneMatchVersion>6.4.2</luceneMatchVersion>
example/example-DIH/solr/solr/conf/solrconfig.xml:38:
<luceneMatchVersion>6.4.2</luceneMatchVersion>
server/solr/configsets/basic_configs/conf/solrconfig.xml:38:
<luceneMatchVersion>6.4.2</luceneMatchVersion>
server/solr/configsets/sample_techproducts_configs/conf/solrconfig.xml:38:
<luceneMatchVersion>6.4.2</luceneMatchVersion>
server/solr/configsets/data_driven_schema_configs/conf/solrconfig.xml:38:
<luceneMatchVersion>6.4.2</luceneMatchVersion>


Maybe you downloaded the 6.4.1 version by mistake?
Thanks,
Ishan


On Thu, Mar 9, 2017 at 10:19 AM, Shawn Heisey <apa...@elyograg.org> wrote:

> On 3/8/2017 2:36 AM, Bernd Fehling wrote:
> > Shouldn't in server/solr/configsets/.../solrconfig.xml
> > <luceneMatchVersion>6.4.1</luceneMatchVersion>
> > really read
> > <luceneMatchVersion>6.4.2</luceneMatchVersion>
> >
> > May be something for package builder for future releases?
>
> That does look like it got overlooked, and is generally something that
> SHOULD be changed with each new version, but in this case, changing
> between those two version numbers will have zero effect.  It is against
> project policy to make significant changes in a bugfix release (where
> third version number changes).
>
> Any change that's significant enough to be controlled by a
> luceneMatchVersion check would only be allowed a minor or major release.
>
> Thanks,
> Shawn
>
>