[xen master] docs/process/xen-release-management: Lesson to learn

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[xen master] docs/process/xen-release-management: Lesson to learn

patchbot
commit 09afb9e78e1e90ce77d5107677a8464e8410802b
Author:     Ian Jackson <[hidden email]>
AuthorDate: Wed Dec 13 11:58:00 2017 +0000
Commit:     Ian Jackson <[hidden email]>
CommitDate: Tue May 29 10:51:02 2018 +0100

    docs/process/xen-release-management: Lesson to learn
   
    The 4.10 release preparation was significantly more hairy than ideal.
    (We seem to have a good overall outcome despite, rather than because
    of, our approach.)
   
    This is the second time (at least) that we have come close to failure
    by committing to a release date before the exact code to be released
    is known and has been made and tested.
   
    Evidently our docs makes it insufficiently clear not to do that.
   
    CC: Julien Grall <[hidden email]>
    Acked-by: Juergen Gross <[hidden email]>
    Acked-by: Jan Beulich <[hidden email]>
    Acked-by: Lars Kurth <[hidden email]>
    Signed-off-by: Ian Jackson <[hidden email]>
---
 docs/process/xen-release-management.pandoc | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/docs/process/xen-release-management.pandoc b/docs/process/xen-release-management.pandoc
index 2ff0665b99..d7fdca5656 100644
--- a/docs/process/xen-release-management.pandoc
+++ b/docs/process/xen-release-management.pandoc
@@ -211,7 +211,12 @@ 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
+7. Do not commit to a release date until
+
+    * The exact xen.git commit id to be released is known.
+    * That commit id has been satisfactorily tested.
+
+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 +224,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
--
generated by git-patchbot for /home/xen/git/xen.git#master

_______________________________________________
Xen-changelog mailing list
[hidden email]
https://lists.xenproject.org/xen-changelog