I was about to merge a PR pertaining to Solr's new Docker module when it occurred to me that I ought to add a CHANGES.txt entry. But, for Solr users (which includes me and everyone reading this), it's annoying to have to go to Solr's all-encompassing CHANGES.txt to find Docker upgrade notes, which is a distinct way of running Solr. I think the same could be said for our contribs, and perhaps even SolrJ, which is another distinct consumable. The idea of separated CHANGES.txt aligns well with contribs being further isolated (see both the discussion on separate git repos for them, and also the discussion of getting rid of "dist" (each contrib's jar goes in its own folder; keeps to itself)).
Solr's root /CHANGES.txt could at the very top reference the other CHANGES.txt files. WDYT? ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley
