On Fri, Aug 30, 2013 at 11:48:56AM +0200, Johan Corveleyn wrote: > At my workplace, we have a convention (enforced by pre-commit hook) to > use a prefix between square brackets ([U] for the user-facing text, > [S9] for the developer details (our team is called the "system9" team) > -> which also get extracted to another text file for an overview of > all the dev-messages of a single release). Here we could use something > similar to the contribulyzer syntax (for instance "Change: blablabla > (issue #1234)").
I like this. No need for pre-commit enforcements, of course. We often don't know in advance which changes will be backported to a release. I guess we would have to delay updates to CHANGES until the moment tarballs are rolled. And instead of updating CHANGES manually we'd simply add or change 'Change:' annotations in log messages, and the release.py script would update CHANGES as necessary before tagging a release.
