mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-07-05 18:29:11 +00:00
Code Issues 32 Releases Wiki Activity

[1.3.X] Fixed #17068 - Documented that documentation fixes will be more freely backported.

Browse Source 
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
This commit is contained in:
Timo Graham 2011-12-30 15:31:09 +00:00
parent c9ab2bfb39
commit 7b9016e5a2
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/internals/release-process.txt
View File

@ -99,6 +99,13 @@ varying levels:
* Security fixes will be applied to the current trunk and the previous two * Security fixes will be applied to the current trunk and the previous two
minor releases. 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 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: 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.X`` branch. Security fixes will trigger the release of ``1.3.1``,
``1.2.1``, etc. ``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:
Release process Release process