Rework the docs for NEWS/What's New entries #1238
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Thanks, this is great! I agree that https://github.com/python/devguide/pull/1238/files#r1417449912 would improve things further.
Also: should we think about moving this information to a different file altogether? This information isn't just relevant to core developers; it's relevant to any contributors.
It's possible (and easy) for core developers to add NEWS entries to other contributors' PRs, but few core devs do so; the de-facto expectation is that contributors should write their own NEWS entries
Co-authored-by: Hugo van Kemenade <[email protected]>
That's a good idea. Let's do it in a follow-up PR. |
Co-authored-by: Hugo van Kemenade <[email protected]>
Co-authored-by: Hugo van Kemenade <[email protected]>
Co-authored-by: Hugo van Kemenade <[email protected]>
|
I'm very pleased with how this turned out. Thanks for your input, everyone! I'll land tomorrow. |
|
@AlexWaygood and @ezio-melotti, I've created follow-up issues for your suggestions regarding further improvements. Let me know if I forgot something. |
(Some minor wording changes might have snuck in, but largely, I kept the existing text.)
📚 Documentation preview 📚: https://cpython-devguide--1238.org.readthedocs.build/core-developers/committing/#updating-news-and-what-s-new-in-python