Ned Deily <n...@python.org> added the comment: The changelog for a release is our primary notification to users about what has changed in a Python release. With 3.6.5, we just had a case where it seemed important to update pip between the release candidate and the final, something we normally would not do. In the past, we could manually munge the changelog to include this info but it's much more difficult to do so now with the NEWS entries managed via blurb. In fact, IIRC, it was a design decision to require a b.p.o issue for any item meriting a NEWS item. So, it's a bit of extra work for you all but it does make life a lot easier for the release team as it's a lot easier to add the NEWS item at the time when the updates are checked in rather than having to go back and do it after the fact. Thanks!
https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-5-final ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33131> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com