[
https://issues.apache.org/jira/browse/SOLR-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712517#comment-13712517
]
Jack Krupansky commented on SOLR-5048:
--------------------------------------
On the ReleaseToDo wiki I see this step: "Find/replace LUCENE_XY ->
LUCENE_X(Y+1) across all of Lucene and Solr, but do NOT change usages under the
lucene/analysis/ that allow version-specific behavior", but when I look at the
example solrconfig.xml in branch_4x, it still says LUCENE_43, suggesting that
this step has been skipped twice now. I think it should say 4.5, since
LUCENE_45 is the only un-deprecated version for branch_4x now, right?
Maybe the step "After creating a new release branch, update the version in the
base release branch (e.g. branches/branch_4x)" needed to be reviewed (or merely
followed) a little more closely.
See:
http://wiki.apache.org/lucene-java/ReleaseTodo#Branching_.26_Feature_Freeze
> fail the build if the example solrconfig.xml files don't have an up to date
> luceneMatchVersion
> ----------------------------------------------------------------------------------------------
>
> Key: SOLR-5048
> URL: https://issues.apache.org/jira/browse/SOLR-5048
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Assignee: Hoss Man
> Attachments: SOLR-5048.patch
>
>
> 4.4 RC0 still had {{<luceneMatchVersion>LUCENE_43</luceneMatchVersion>}} ...
> the build should fail in a situation like this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
