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 lemburg
Recipients brett.cannon, ezio.melotti, georg.brandl, lemburg, ncoghlan, pitrou, r.david.murray, sbt, terry.reedy, tshepang, zach.ware
Date 2014-04-22.10:52:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
FWIW: I don't think we need to manage the news entries in the NEWS
file. Instead, we could simply add a field to the bug tracker
called "news entry" and populate that as necessary.

During release, this information can then be used to create a
NEWS file per release. This file would not be touched by anyone
other then the release manager.

As a result, there would not longer be any merge conflicts, and
the news entries can still be changed before the release
if necessary, and, of course, the generated NEWS file can also
be edited as the release manager sees fit.

Tickets which do not need a news entry simply leave the news entry
field blank.

We really don't need a file system database for these things.

(PS: eGenix has been using such a system internally for several
years and it works great.)
Date User Action Args
2014-04-22 10:52:43lemburgsetrecipients: + lemburg, brett.cannon, georg.brandl, terry.reedy, ncoghlan, pitrou, ezio.melotti, r.david.murray, tshepang, sbt, zach.ware
2014-04-22 10:52:43lemburglinkissue18967 messages
2014-04-22 10:52:43lemburgcreate