You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2013/04/19 15:09:27 UTC
[jira] [Created] (LUCENE-4943) remove 'Changes to Backwards
Compatibility Policy' from lucene/CHANGES.txt
Robert Muir created LUCENE-4943:
-----------------------------------
Summary: 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org