Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

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

…re freely backported.

Backport of r17300 from trunk.

git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.3.X@17301 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit 7b9016e5a229c2269d758959e4d07a0dbe4e710f 1 parent c9ab2bf
Tim Graham authored December 30, 2011

Showing 1 changed file with 10 additions and 0 deletions. Show diff stats Hide diff stats

  1. 10  docs/internals/release-process.txt
10  docs/internals/release-process.txt
@@ -99,6 +99,13 @@ varying levels:
99 99
     * Security fixes will be applied to the current trunk and the previous two
100 100
       minor releases.
101 101
 
  102
+* Documentation fixes will generally be more freely backported to the last
  103
+  release branch (at the discretion of the committer), and don't need to meet
  104
+  the "critical fixes only" bar as it's highly advantageous to have the docs
  105
+  for the last release be up-to-date and correct, and the downside of
  106
+  backporting (risk of introducing regressions) is much less of a concern
  107
+  with doc fixes.
  108
+
102 109
 As a concrete example, consider a moment in time halfway between the release of
103 110
 Django 1.3 and 1.4. At this point in time:
104 111
 
@@ -111,6 +118,9 @@ Django 1.3 and 1.4. At this point in time:
111 118
       ``1.2.X`` branch. Security fixes will trigger the release of ``1.3.1``,
112 119
       ``1.2.1``, etc.
113 120
 
  121
+* Documentation fixes will be applied to trunk, and if easily backported, to
  122
+  the ``1.3.X`` branch.
  123
+
114 124
 .. _release-process:
115 125
 
116 126
 Release process

0 notes on commit 7b9016e

Please sign in to comment.
Something went wrong with that request. Please try again.