[
https://issues.apache.org/jira/browse/LUCENE-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041425#comment-13041425
]
Doron Cohen commented on LUCENE-3164:
-------------------------------------
I agree that with frequent releases this is less of an issue.
What are your thoughts about trunk in this regard - would you like there 3
changes files, i.e. keep one for modules?
> 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]
