Browse files

[1.3.X] Fixed #17068 - Documented that documentation fixes will be mo…

…re freely backported.

Backport of r17300 from trunk.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent c9ab2bf commit 7b9016e5a229c2269d758959e4d07a0dbe4e710f @timgraham timgraham committed Dec 30, 2011
Showing with 10 additions and 0 deletions.
  1. +10 −0 docs/internals/release-process.txt
@@ -99,6 +99,13 @@ varying levels:
* Security fixes will be applied to the current trunk and the previous two
minor releases.
+* Documentation fixes will 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 as it's highly advantageous to have the docs
+ for the last release be up-to-date and correct, and the downside of
+ backporting (risk of introducing regressions) is much less of a concern
+ with doc fixes.
As a concrete example, consider a moment in time halfway between the release of
Django 1.3 and 1.4. At this point in time:
@@ -111,6 +118,9 @@ Django 1.3 and 1.4. At this point in time:
``1.2.X`` branch. Security fixes will trigger the release of ``1.3.1``,
``1.2.1``, etc.
+* Documentation fixes will be applied to trunk, and if easily backported, to
+ the ``1.3.X`` branch.
.. _release-process:
Release process

0 comments on commit 7b9016e

Please sign in to comment.