Nick Coghlan added the comment: Folks, this is *really, really, simple*: one file per NEWS entry. How we arrange them is just a detail. Don't go off trying to invent wild exotic alternatives that spread state across multiple sources of truth - significant historical info belongs in the version control system, and NEWS entries are how we highlight "this one is significant" (relative to other commits). A hg extension that prepopulates the commit message from a NEWS entry included in the patch wouldn't be difficult (especially since some of the Mercurial devs are likely to join the new core workflow list).
---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18967> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
