From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org, xen-devel@lists.xen.org
Cc: Lars Kurth <lars.kurth@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Julien Grall <julien.grall@arm.com>,
Jan Beulich <jbeulich@suse.com>
Subject: [PATCH v2 2/2] docs/process/xen-release-management: Lesson to learn
Date: Tue, 22 May 2018 17:45:23 +0100 [thread overview]
Message-ID: <1527007523-23576-3-git-send-email-ian.jackson@eu.citrix.com> (raw)
In-Reply-To: <1527007523-23576-1-git-send-email-ian.jackson@eu.citrix.com>
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: Lars Kurth <lars.kurth@citrix.com>
CC: Julien Grall <julien.grall@arm.com>
Acked-by: Juergen Gross <jgross@suse.com>
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
---
docs/process/xen-release-management.pandoc | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/docs/process/xen-release-management.pandoc b/docs/process/xen-release-management.pandoc
index 2ff0665..eee5dcf 100644
--- a/docs/process/xen-release-management.pandoc
+++ b/docs/process/xen-release-management.pandoc
@@ -211,6 +211,11 @@ 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. 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.
+
7. 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
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-05-22 16:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 16:45 [PATCH v2 0/2] Release process: lesson to learn Ian Jackson
2018-05-22 16:45 ` [PATCH v2 1/2] docs/process: Add RUBRIC Ian Jackson
2018-05-23 4:17 ` Juergen Gross
2018-05-22 16:45 ` Ian Jackson [this message]
2018-05-23 4:14 ` [PATCH v2 2/2] docs/process/xen-release-management: Lesson to learn Juergen Gross
2018-05-23 14:34 ` Ian Jackson
2018-05-23 8:15 ` Jan Beulich
2018-05-23 12:37 ` Lars Kurth
2018-05-23 14:35 ` [PATCH v2 0/2] Release process: lesson " Ian Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1527007523-23576-3-git-send-email-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=lars.kurth@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).