[Xen-changelog] [xen staging] docs/process: Move MAINTAINERS update for stable to .0 release

[patchbot@xxxxxxx]

commit c7d52a5be62ea253a9baac68510683c47efbcb8c
Author:     Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
AuthorDate: Fri Nov 29 14:57:29 2019 +0000
Commit:     Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
CommitDate: Fri Nov 29 15:51:24 2019 +0000

    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@xxxxxxxxxxxxx>
---
 docs/process/branching-checklist.txt          | 7 -------
 docs/process/release-technician-checklist.txt | 8 ++++++++
 2 files changed, 8 insertions(+), 7 deletions(-)

diff --git a/docs/process/branching-checklist.txt 
b/docs/process/branching-checklist.txt
index 9e79f64157..10c2038319 100644
--- 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 59ee8bd3d2..7ed2636a12 100644
--- 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
 
--
generated by git-patchbot for /home/xen/git/xen.git#staging

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/xen-changelog