[xen staging] process/release: mention MAINTAINERS adjustments

[patchbot@xxxxxxx]

commit 86fc80ca8e6062025bea269929036d5a4dcb7f74
Author:     Jan Beulich <jbeulich@xxxxxxxx>
AuthorDate: Mon Mar 24 12:55:24 2025 +0100
Commit:     Jan Beulich <jbeulich@xxxxxxxx>
CommitDate: Mon Mar 24 12:55:24 2025 +0100

    process/release: mention MAINTAINERS adjustments
    
    For many major releases I've been updating ./MAINTAINERS _after_ the
    respective branch was handed over to me. That update, however, is
    relevant not only from the .1 minor release onwards, but right from the
    .0 release. Hence it ought to be done as one of the last things before
    tagging the tree for the new major release.
    
    See the seemingly unrelated parts (as far as the commit subject goes) of
    e.g. 9d465658b405 ("update Xen version to 4.20.1-pre") for an example.
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Julien Grall <jgrall@xxxxxxxxxx>
---
 docs/process/release-technician-checklist.txt | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/process/release-technician-checklist.txt 
b/docs/process/release-technician-checklist.txt
index 4b061bf5f2..7bbe7c1489 100644
--- a/docs/process/release-technician-checklist.txt
+++ b/docs/process/release-technician-checklist.txt
@@ -53,6 +53,9 @@ t=RELEASE-$r
     - "Xen 4.5-unstable" on unstable
     - "Xen 4.5-rc" for release candidate
 
+* for major releases, drop staging-only text from MAINTAINERS and add stable
+  maintainer(s) there
+
 * change xen-unstable Config.mk
 #   QEMU_UPSTREAM_REVISION,
 #   QEMU_TRADITIONAL_REVISION
--
generated by git-patchbot for /home/xen/git/xen.git#staging