Message 216977 - Python tracker

Message216977

Author	ncoghlan
Recipients	brett.cannon, ezio.melotti, georg.brandl, lemburg, ncoghlan, pitrou, r.david.murray, sbt, terry.reedy, tshepang, zach.ware
Date	2014-04-22.00:51:04
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<CADiSq7ca9EtHjvpU7j+DveUu7iUvTVd1NMpO29jXpKEz2gfQkg@mail.gmail.com>
In-reply-to	<1398112908.13.0.755730209999.issue18967@psf.upfronthosting.co.za>

Content
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).

Content

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).

History
Date	User	Action	Args
2014-04-22 00:51:05	ncoghlan	set	recipients: + ncoghlan, lemburg, brett.cannon, georg.brandl, terry.reedy, pitrou, ezio.melotti, r.david.murray, tshepang, sbt, zach.ware
2014-04-22 00:51:05	ncoghlan	link	issue18967 messages
2014-04-22 00:51:04	ncoghlan	create