[
https://issues.apache.org/jira/browse/LUCENE-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636352#comment-13636352
]
Robert Muir commented on LUCENE-4943:
-------------------------------------
I thought about MIGRATE.txt too, but I see its use for 'major releases'. Maybe
we dont even need it any more long term and it was mainly just needed for 4.0
(hopefully we can get releases out faster so we dont need things like this).
One advantage of the "Upgrading" section is that it would make the Lucene and
Solr CHANGES files more consistent, and I think the changes2html parser would
already work with it?
> remove 'Changes to Backwards Compatibility Policy' from lucene/CHANGES.txt
> --------------------------------------------------------------------------
>
> Key: LUCENE-4943
> URL: https://issues.apache.org/jira/browse/LUCENE-4943
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Fix For: 4.4
>
>
> CHANGES.txt is useful to summarize the changes in a release.
> However its expected that a lot of changes will impact the APIs, this
> currently hurts the quality of CHANGES.txt because it leads to a significant
> portion of changes (whether they be bugs, features, whatever) being grouped
> under this one title.
> It also leads to descriptions of CHANGES being unnecessarily verbose.
> I think it makes CHANGES confusing and overwhelming, and it would be better
> to have a simpler 'upgrading' section with practical information on what you
> actually need to do (like Solr's CHANGES.txt).
--
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]
