Note when to backport changes

[JacobCoffee]

• Adds guidelines on what release cycles (where) should get backports of documentation and testing improvements.

Closes

• Require to backport all documentation and tests changes to stable Python branches #1168
• Maybe Clarify where docs fixes can be backported #1069(?)

Changes visualized:

Dev. CycleVersions

---

📚 Documentation preview 📚: https://cpython-devguide--1169.org.readthedocs.build/

[AA-Turner]

Thanks for this Jacob. I agree with Victor's comments, this needs a few edits in the first instance.

A tip for using admonitions: they stand out and are highlighted, which means that using them must be done sparingly -- when is is most critical for a reader to be aware of a point? I think in this instance, backporting is not of sufficient import; so regular prose is fine. This is very akin to the boy who cried wolf, just in this instance replace the villagers with readers and the wolf with admonitions!

A

[JacobCoffee]

Thanks Adam, and understood. That makes sense - the use of admonitions is quite a bit different than I am used to 😄

[JacobCoffee]

Please re-review at your earliest convenience to see if it is in line with what we want to communicate

[AA-Turner]

Please avoid force-pushing, it makes reviewing in the GH interface much harder. PRs are squash merged.

A

[AA-Turner]

Thanks!

A