docs/process: Move MAINTAINERS update for stable to .0 release

This should be done not while branching, but right after .0 is
released.

Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>

diff --git a/docs/process/branching-checklist.txt b/docs/process/branching-checklist.txt
index 9e79f64157efdfb17b4d5a07628c0e13da622233..10c203831941875a249f277686ea6d6acfb284dd 100644 (file)
--- a/docs/process/branching-checklist.txt
+++ b/docs/process/branching-checklist.txt
@@ -84,13 +84,6 @@ Update newly diverging staging-$v according to
 release-technician-checklist.txt section re README etc.,
 including turning off debug.
 
-Update new stable tree's MAINTAINERS to contain correct info for this
-stable branch: usually, copy text from previous
-staging-$ov:MAINTAINERS section "Stable Release Maintenance"
-into new staging-$v, deleting what's there.
-  git cat-file blob origin/staging-$ov:MAINTAINERS >MAINTAINERS
-and review the changes, commiting ONLY THE RELEVANT ONES
-
 Set off a manual osstest run, since the osstest cr-for-branches change
 will take a while to take effect:
   ssh osstest.test-lab

diff --git a/docs/process/release-technician-checklist.txt b/docs/process/release-technician-checklist.txt
index 59ee8bd3d2b6fd195fcb9bdd0d4a9b370c5fa403..7ed2636a12ba98d70e90de30b340c73b2ef477e1 100644 (file)
--- a/docs/process/release-technician-checklist.txt
+++ b/docs/process/release-technician-checklist.txt
@@ -148,5 +148,13 @@ RELEASE TARBALL
 
 After a .0 release, update XEN_EXTRAVERSION again (to .1-pre, see above).
 
+After a .0 release,
+Update new stable tree's MAINTAINERS to contain correct info for this
+stable branch: usually, copy text from previous
+staging-$ov:MAINTAINERS section "Stable Release Maintenance"
+into new staging-$v, deleting what's there.
+  git cat-file blob origin/staging-$ov:MAINTAINERS >MAINTAINERS
+and review the changes, commiting ONLY THE RELEVANT ONES
+
 Notify release manager of completion