Zachary Ware added the comment: 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 -` ---------- hgrepos: +228 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18967> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
