[
https://issues.apache.org/jira/browse/LUCENE-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041409#comment-13041409
]
Doron Cohen commented on LUCENE-3164:
-------------------------------------
Specifically, current files are:
lucene:
- CHANGES.txt
- contrib/benchmark/CHANGES.txt
- contrib/CHANGES.txt
- contrib/grouping/CHANGES.txt
solr
- CHANGES.txt
- client/ruby/flare/vendor/plugins/engines/CHANGELOG (\?)
- client/ruby/solr-ruby/CHANGES.yml (\?)
- contrib/analysis-extras/CHANGES.txt
- contrib/clustering/CHANGES.txt
- contrib/dataimporthandler/CHANGES.txt
- solr/contrib/extraction/CHANGES.txt
- solr/contrib/uima/CHANGES.txt
In favor of this, all changes would become more easily readable for users in
the HTML format.
There is a risk that changes in contribs/modules would clutter the core
changes. For example, today, even small changes in contrib/benchmark are listed
in the changes file. But when this becomes part of the global changes file, not
sure if all bm changes would be adequate to be listed there?
> consolidate various CHANGES.txt into two files: lucene and solr
> ---------------------------------------------------------------
>
> Key: LUCENE-3164
> URL: https://issues.apache.org/jira/browse/LUCENE-3164
> Project: Lucene - Java
> Issue Type: Task
> Reporter: Robert Muir
>
> There are CHANGES.txt files everywhere: lucene/contrib has a CHANGES.txt, the
> benchmark package has its own CHANGES.txt, in trunk all the modules have
> their own CHANGES.txt, and each solr contrib has its own CHANGES.txt
> I propose we merge these files into a CHANGES.txt for each "product" we make.
> so that means lucene/CHANGES.txt and solr/CHANGES.txt
--
This message is automatically generated by JIRA.
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]
