Author: kmtracey Date: 2008-12-08 11:15:56 -0600 (Mon, 08 Dec 2008) New Revision: 9610
Modified: django/trunk/docs/internals/release-process.txt Log: In the release process doc, clarify that the original committer is responsible for backporting trunk fixes to the bug-fix branch. Modified: django/trunk/docs/internals/release-process.txt =================================================================== --- django/trunk/docs/internals/release-process.txt 2008-12-08 17:01:17 UTC (rev 9609) +++ django/trunk/docs/internals/release-process.txt 2008-12-08 17:15:56 UTC (rev 9610) @@ -179,9 +179,10 @@ 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 -------------------------- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-updates?hl=en -~----------~----~----~----~------~----~------~--~---
