[PATCH] docs: adjust release management doc

From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xenproject.org
Cc: Juergen Gross <jgross@suse.com>,
	sstabellini@kernel.org, wei.liu2@citrix.com,
	George.Dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
	ian.jackson@eu.citrix.com, tim@xen.org, jbeulich@suse.com
Subject: [PATCH] docs: adjust release management doc
Date: Thu, 26 Apr 2018 12:48:44 +0200	[thread overview]
Message-ID: <20180426104844.15342-1-jgross@suse.com> (raw)

Signed-off-by: Juergen Gross <jgross@suse.com>
---
 docs/process/xen-release-management.pandoc | 16 ++++++++++++----
 1 file changed, 12 insertions(+), 4 deletions(-)

diff --git a/docs/process/xen-release-management.pandoc b/docs/process/xen-release-management.pandoc
index 2ff0665b99..ac324981fd 100644
--- a/docs/process/xen-release-management.pandoc
+++ b/docs/process/xen-release-management.pandoc
@@ -198,12 +198,14 @@ releases typically done mid-week (Tuesday - Thursday).
 
 4. Select the release date.
 
-5. Check with relevant stake-holders (typically community manager) whether
+5. Specify the dates regarding support and security support in SUPPORT.md.
+
+6. Check with relevant stake-holders (typically community manager) whether
 wiki documentation and PR is in good shape (for an example see
 https://wiki.xenproject.org/wiki/Category:Xen_4.9
 <https://wiki.xenproject.org/wiki/Category:Xen_4.9>)
 
-6. Obtain a formal go-ahead from
+7. Obtain a formal go-ahead from
 
     * the Community Manager
     * the Release Technician
@@ -211,7 +213,7 @@ https://wiki.xenproject.org/wiki/Category:Xen_4.9
     Ask them to dry-run their checklist and confirm everything is OK. If not,
     arrange another RC and restart this checklist.
 
-7. Give PR Personnel final go-ahead, and instruct Release Technician to make
+8. Give PR Personnel final go-ahead, and instruct Release Technician to make
 release deliverables (tags and tarballs - will usually be in place the day
 before the release). At this point, PR collateral will be sent to reporters
 (typically 2-3 working days before the release date) and we cannot undo
@@ -219,7 +221,7 @@ publications without questions being asked and risk of negative PR. It is
 acceptable to make a xen-devel@ announcement *before* the PR release date
 (blog, xen-announce@, press release).
 
-8. Make the announcement on various mailing list, publish the blog post.
+9. Make the announcement on various mailing list, publish the blog post.
 
 Allow for contingencies. It is not uncommon that some last minute (security or
 not) bugs are discovered. To provide a fix takes time, the test of the fix
@@ -234,9 +236,15 @@ following things happen for the new Release Manager.
 
 1. A JIRA (xenproject.atlassian.net) is created and proper permissions granted.
 2. Access to community test infrastructure is granted.
+   In the common case the public pages at logs.test-lab.xenproject.org will
+   suffice.
 3. Access to mailing list moderation panel is granted.
 4. An account for blog.xenproject.org is created.
+   The account can be created by the new Release Manager, it might be necessary
+   to adjust the access rights.
 5. An account for wiki.xenproject.org is created.
+   The account can be created by the new Release Manager, it might be necessary
+   to adjust the access rights.
 
 # Email templates and scripts
 
-- 
2.13.6


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
