test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

In the release process doc, clarify that the original committer is responsible 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
This commit is contained in:
Karen Tracey 2008-12-08 17:15:56 +00:00
parent bde736cc5a
commit 453d452653
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -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 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 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 *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 separate bug fixes from feature additions. The developer who commits a fix to
maintainer who will work with the committers to keep them honest on backporting trunk will be responsible for also applying the fix to the current bug-fix
bug fixes. 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 How this all fits together
-------------------------- --------------------------