Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

In the release process doc, clarify that the original committer is re…

…sponsible for backporting trunk fixes to the bug-fix branch.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@9610 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit 453d452653bcfff8c29a112e0529d4a1c17c97e3 1 parent bde736c
@kmtracey kmtracey authored
Showing with 4 additions and 3 deletions.
  1. +4 −3 docs/internals/release-process.txt
View
7 docs/internals/release-process.txt
@@ -179,9 +179,10 @@ After a minor release (i.e 1.1), the previous release will go into bug-fix mode.
A branch will be created of the form ``branches/releases/1.0.X`` to track
bug-fixes to the previous release. When possible, bugs fixed on trunk must
*also* be fixed on the bug-fix branch; this means that commits need to cleanly
-separate bug fixes from feature additions. Each bug-fix branch will have a
-maintainer who will work with the committers to keep them honest on backporting
-bug fixes.
+separate bug fixes from feature additions. The developer who commits a fix to
+trunk will be responsible for also applying the fix to the current bug-fix
+branch. Each bug-fix branch will have a maintainer who will work with the
+committers to keep them honest on backporting bug fixes.
How this all fits together
--------------------------
Please sign in to comment.
Something went wrong with that request. Please try again.