So, it looks like we should follow Lucene's lead on how to handle our CHANGES.txt across 3.x and trunk. If the same change is being committed to both, put it in the 3.x section of trunk's CHANGES. When something is backported to 3.x, move it from the 4.0 to the 3.1 section in trunk's CHANGES. That will handle most of the issues I think.
Of course... when a 3.x-only change is made, should that be added to the 3.1 section of trunk's CHANGES? And just another reminder: CHANGES should act as release notes. Subversion and JIRA has the full history - we don't need to repeat it all in CHANGES. -Yonik http://lucenerevolution.org Lucene/Solr Conference, Boston Oct 7-8 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
