➜

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 zach.ware
Recipients brett.cannon, ezio.melotti, georg.brandl, lemburg, ncoghlan, orsenthil, pitrou, r.david.murray, sbt, terry.reedy, tshepang, zach.ware
Date 2014-03-20.20:01:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1395345701.36.0.459342789971.issue18967@psf.upfronthosting.co.za>
In-reply-to
Content 
The earlier in a release cycle we switch NEWS methods, the better.  Does anyone have any thoughts to share about this, either on Brett's newsworthy.py, my news.py/news_release.py, or another approach entirely?

I've updated the playground branch of sandbox/new_news to mirror current default (3.5.0a0), and have added .news files in the NEWS.parts tree to match the current state of Misc/NEWS.  I've also linked the repository to this issue.

You can play with adding NEWS entries by running Tools/scripts/news.py and see how it looks put together by running Tools/scripts/news_release.py (or write Misc/NEWS and remove all parts with "Tools/scripts/news_release.py write").

Other interesting things to try:
- Create a .news file with news.py, then use `hg commit -l Misc/NEWS.parts/<section>/<filename>.news`
- Do the above in a single step: `Tools/scripts/news.py | hg commit -l -`
History
Date User Action Args
2014-03-20 20:01:41zach.waresetrecipients: + zach.ware, lemburg, brett.cannon, georg.brandl, terry.reedy, ncoghlan, orsenthil, pitrou, ezio.melotti, r.david.murray, tshepang, sbt
2014-03-20 20:01:41zach.waresetmessageid: <1395345701.36.0.459342789971.issue18967@psf.upfronthosting.co.za>
2014-03-20 20:01:41zach.warelinkissue18967 messages
2014-03-20 20:01:40zach.warecreate