Other than for the most trivial sorts of changes (e.g. obvious spelling errors), nearly all changes to the cpython repo should include a NEWS entry; that's our primary mechanism to communicate changes with downstream users. We should be encouraging everyone, including non core-developers to submit PRs with NEWS entries. Among other benefits, having a NEWS entry makes reviews of the PR easier and helps to focus everyone include the submitter on what problem the PR is trying to address. And the tool we have to create NEWS entry isblurb; we want to encourage everyone creating or modifying a PR to use it. It's easier to delete the occasional unnecessary NEWS item than it is to create one when committing. To that end, suggest:

1. Create a section in theGit Bootcamp and Cheat SheetAccepting and Mergingsection to describe the details of using blurb with a fallback to how to manually create aMiscNEWS.d entry: basically, adapt and move the detailed info from theAccepting Pull Requests section. We want to be careful to encourageblurb usage andnot encourage manually creation as the details could change in the future.

2. This section should also include some guidelines on what a good NEWS entry looks like, or, if not here, one place in the devguide with references to it.

3. Review the whole document and add mentions of NEWS entries and theblurb command everywhere creating or reviewing or committing a PR is discussed and include a link to the detailed section created above. In particular, theLifecycle of a Pull Request section needs to be edited to include blurb.