Code

Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#17068 closed Bug (fixed)

Document that documentation fixes will be more freely backported

Reported by: carljm Owned by: nobody
Component: Documentation Version: 1.3
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

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.

Attachments (0)

Change History (4)

comment:1 Changed 2 years ago by aaugustin

  • Triage Stage changed from Unreviewed to Accepted

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

comment:2 Changed 2 years ago by PaulM

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

comment:3 Changed 2 years ago by timo

  • Resolution set to fixed
  • Status changed from new to closed

In [17300]:

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

comment:4 Changed 2 years ago by timo

In [17301]:

(The changeset message doesn't reference this ticket)

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.