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 pitrou
Recipients brett.cannon, ezio.melotti, georg.brandl, lemburg, ncoghlan, pitrou, r.david.murray, sbt, terry.reedy, tshepang, zach.ware
Date 2014-04-20.23:59:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398038381.28.0.0719956846162.issue18967@psf.upfronthosting.co.za>
In-reply-to
Content
> 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."""

> In any case, the News entries are not necessarily time ordered now.

IME, they mostly are. It's true it's not a requirement.
History
Date User Action Args
2014-04-20 23:59:41pitrousetrecipients: + pitrou, lemburg, brett.cannon, georg.brandl, terry.reedy, ncoghlan, ezio.melotti, r.david.murray, tshepang, sbt, zach.ware
2014-04-20 23:59:41pitrousetmessageid: <1398038381.28.0.0719956846162.issue18967@psf.upfronthosting.co.za>
2014-04-20 23:59:41pitroulinkissue18967 messages
2014-04-20 23:59:40pitroucreate