Document that documentation fixes will be more freely backported

[Carl Meyer]

My understanding of the backporting policy is that documentation fixes should generally be more freely backported to the last release branch (at the discretion of the committer), and don't need to meet the "critical fixes only" bar. I think this only makes sense, because it's highly advantageous to have the docs for the last release be up-to-date and correct on djangoproject.com, and the downside of backporting (risk of introducing regressions) is much less of a concern with doc fixes.

This recently came up on #16072 - I think that the re-opener is correct in that case, and the 1.3 docs should be updated to be correct.

I think the ​supported-versions section of the release-process documentation should be updated to make specific note of the fact that doc fixes will be more often backported. Opening this ticket in order to give an opportunity for someone to disagree before I go ahead and make the change.

[Aymeric Augustin]

I'm seconding carljm here. I had the same reaction to #16072.

[Paul McMillan]

I agree as well. Doc fixes are unlikely to introduce serious regressions and are the most instantly useful type of fixes we can provide.

[Tim Graham]

In [17300]:

Fixed #17068 - Documented that documentation fixes will be more freely backported.

[Tim Graham]

In [17301]:

(The changeset message doesn't reference this ticket)