Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

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
Karen Tracey authored December 08, 2008

Showing 1 changed file with 4 additions and 3 deletions. Show diff stats Hide diff stats

  1. 7  docs/internals/release-process.txt
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.
179 179
 A branch will be created of the form ``branches/releases/1.0.X`` to track
180 180
 bug-fixes to the previous release. When possible, bugs fixed on trunk must
181 181
 *also* be fixed on the bug-fix branch; this means that commits need to cleanly
182  
-separate bug fixes from feature additions. Each bug-fix branch will have a
183  
-maintainer who will work with the committers to keep them honest on backporting
184  
-bug fixes.
  182
+separate bug fixes from feature additions. The developer who commits a fix to 
  183
+trunk will be responsible for also applying the fix to the current bug-fix
  184
+branch.  Each bug-fix branch will have a maintainer who will work with the
  185
+committers to keep them honest on backporting bug fixes.
185 186
 
186 187
 How this all fits together
187 188
 --------------------------

0 notes on commit 453d452

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