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 sbt
Recipients brett.cannon, ezio.melotti, georg.brandl, lemburg, ncoghlan, orsenthil, pitrou, r.david.murray, sbt, tshepang
Date 2013-09-17.09:50:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1379411457.93.0.540582683464.issue18967@psf.upfronthosting.co.za>
In-reply-to
Content
An alternative would be to have separate files NEWS-3.2, NEWS-3.3, NEWS-3.4 etc.  If a fix is added to 3.2 and will be merged to 3.3 and 3.4 then you add an entry to NEWS-3.2 and append some sort of tags to indicate merges:

    - Issue #1234: Fix something that was not working properly.
      #Merge-3.3 #Merge-3.4

Then NEWS can be auto-generated from NEWS-3.*.
History
Date User Action Args
2013-09-17 09:50:57sbtsetrecipients: + sbt, lemburg, brett.cannon, georg.brandl, ncoghlan, orsenthil, pitrou, ezio.melotti, r.david.murray, tshepang
2013-09-17 09:50:57sbtsetmessageid: <1379411457.93.0.540582683464.issue18967@psf.upfronthosting.co.za>
2013-09-17 09:50:57sbtlinkissue18967 messages
2013-09-17 09:50:57sbtcreate