This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients brett.cannon, ezio.melotti, georg.brandl, lemburg, ncoghlan, pitrou, r.david.murray, sbt, terry.reedy, tshepang, zach.ware
Date 2014-04-21.00:34:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
On 4/20/2014 7:59 PM, Antoine Pitrou wrote:
> Antoine Pitrou added the comment:
>> This is already not a rule because the devguide mentions inserting new
>> items at random positions to avoid conflicts due to another commit.
> Really?
> """New NEWS entries are customarily added at or near the top of their respective sections, so that entries within a section appear in approximate order from newest to oldest. However, this is customary and not a requirement."""

Random is too loose for what was actually committed and I will correct 
it. Further down in the same section: "A nice trick to make Mercurial’s 
automatic file merge work more smoothly is to put a new entry after the 
first or first two entries rather than at the very top. This way if you 
commit, pull new changesets and merge, the merge will succeed 

>> In any case, the News entries are not necessarily time ordered now.
> IME, they mostly are. It's true it's not a requirement.
Date User Action Args
2014-04-21 00:34:30terry.reedysetrecipients: + terry.reedy, lemburg, brett.cannon, georg.brandl, ncoghlan, pitrou, ezio.melotti, r.david.murray, tshepang, sbt, zach.ware
2014-04-21 00:34:30terry.reedylinkissue18967 messages
2014-04-21 00:34:29terry.reedycreate