xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Tim Deegan <tim@xen.org>, Jan Beulich <jbeulich@suse.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: [PATCH 3/4] misc/release-checklist: Split out branching-checklist.txt
Date: Thu, 9 Mar 2017 15:19:26 +0000	[thread overview]
Message-ID: <1489072767-21441-4-git-send-email-ian.jackson@eu.citrix.com> (raw)
In-Reply-To: <1489072767-21441-1-git-send-email-ian.jackson@eu.citrix.com>

This is almost all just motion.  There is one new paragraph in
branching-checklist.txt:

+ Update both new branches according to release-checklist.txt section re
+ README etc.

Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
---
 misc/branching-checklist.txt | 97 ++++++++++++++++++++++++++++++++++++++++++++
 misc/release-checklist.txt   | 95 -------------------------------------------
 2 files changed, 97 insertions(+), 95 deletions(-)
 create mode 100644 misc/branching-checklist.txt

diff --git a/misc/branching-checklist.txt b/misc/branching-checklist.txt
new file mode 100644
index 0000000..c905383
--- /dev/null
+++ b/misc/branching-checklist.txt
@@ -0,0 +1,97 @@
+v=4.1
+ov=4.0
+
+##* tag branchpoint
+##        hg tag $v.0-branched
+##        hg sign -k 'Xen tree' 4.1.0-branched
+
+* make branch in qemu-iwj.git
+        git-branch $v-testing master
+
+# make branches in xenbits.xen.org qemus
+        ssh xen@xenbits.xen.org
+	cd ~/git/qemu-xen.git
+	git branch staging-$v staging
+	git branch stable-$v master
+	cd ~/git/qemu-xen-traditional.git
+	git branch stable-$v master
+
+# make branch in libvirt
+        ssh xen@xenbits.xen.org
+        cd ~/git/libvirt.git/
+	git branch osstest/frozen/xen-$v-testing   xen-tested-master
+
+# make branches in xenbits.xen.org xen.git
+        ssh xen@xenbits.xen.org
+        cd ~/git/xen.git
+	git branch staging-$v staging
+	git branch stable-$v master
+
+# update xendocs@xenbits docs generator to generate new stable branch
+#  docs too. commit to git.
+* make 13:37 <ijc> http://xenbits.xen.org/docs/4.2-testing/ is now live true
+#14:17 <ijc> HOWTO: login to xenbits. become "xendocs" . cd cronjobs . edit
+#            xenbits-docs-all.sh in the obvious way. git commit
+	ssh root@xenbits.xen.org
+	su - xendocs
+	cd cronjobs
+	ed xenbits-docs-all.sh
+	/for branch
+	s/$/ 4.6-testing
+	# ^ OR SIMILAR
+	w
+	q
+        git add -p
+	git commit -m "Branch for $v"
+
+### * make symlink on mariner for qemu
+###        cd /var/www/git/
+###        ln -s /usr/groups/xencore/HG/qemu-xen-$v-testing.git .
+
+* make branches etc. in osstest
+        ssh osstest@osstest.test-lab
+	cd testing.git
+	OSSTEST_CONFIG=production-config ./mg-branch-setup xen-$v-testing bisect
+	OSSTEST_CONFIG=production-config ./mg-branch-setup qemu-upstream-$v-testing bisect
+
+* add branch to osstest
+        ie add both eg qemu-upstream-4.2-testing and xen-4.2-testing to BRANCHES in cr-for-branches
+
+* add to patchbot
+        on xenbits
+        cd ~/HG/patchbot/
+
+	cp xen--master.patchbot-reported-heads xen--stable-$v.patchbot-reported-heads
+	cp xen--staging.patchbot-reported-heads xen--staging-$v.patchbot-reported-heads
+        cp qemu-xen--master.patchbot-reported-heads  qemu-xen--stable-$v.patchbot-reported-heads
+        cp qemu-xen--staging.patchbot-reported-heads  qemu-xen--staging-$v.patchbot-reported-heads
+        cp qemu-xen-traditional--master.patchbot-reported-heads qemu-xen-traditional--stable-$v.patchbot-reported-heads
+
+        #emacs versions
+	perl -i~ -pe 'next unless m/\b\Q'$ov'\E\b/; $x=$_; $x=~ s/\b\Q'$ov'\E\b/'$v'/g; print $x;' versions
+        git diff
+	git add versions
+	git commit -m "Branch for $v"
+
+#* update xenbits web page
+        ssh root@xenbits.xen.org
+        cd /var/xenbits-www/html
+        emacs index.html
+	# - search for previous version number, and update in each place found
+	# - in general, drop one old release in favour of the new one
+
+Ensure references to qemu trees in xen.git's Config.mk are updated.
+Check this with
+        grep unstable Config.mk 
+which should produce no output.  Replace as necessary.
+
+Update both new branches according to release-checklist.txt section re
+README etc.
+
+Update new stable tree's MAINTAINERS to contain correct info for this stable branch
+
+###* fix new trees' vcs descriptions
+#* make old trees' descriptions "historical"
+#	cd ~/git
+#	perl -i~ -pe "s/unstable/4.6-testing/" qemu-upstream-$v-testing.git/description
+
diff --git a/misc/release-checklist.txt b/misc/release-checklist.txt
index 0fa50c9..4784256 100644
--- a/misc/release-checklist.txt
+++ b/misc/release-checklist.txt
@@ -1,98 +1,3 @@
-v=4.1
-ov=4.0
-
-##* tag branchpoint
-##        hg tag $v.0-branched
-##        hg sign -k 'Xen tree' 4.1.0-branched
-
-* make branch in qemu-iwj.git
-        git-branch $v-testing master
-
-# make branches in xenbits.xen.org qemus
-        ssh xen@xenbits.xen.org
-	cd ~/git/qemu-xen.git
-	git branch staging-$v staging
-	git branch stable-$v master
-	cd ~/git/qemu-xen-traditional.git
-	git branch stable-$v master
-
-# make branch in libvirt
-        ssh xen@xenbits.xen.org
-        cd ~/git/libvirt.git/
-	git branch osstest/frozen/xen-$v-testing   xen-tested-master
-
-# make branches in xenbits.xen.org xen.git
-        ssh xen@xenbits.xen.org
-        cd ~/git/xen.git
-	git branch staging-$v staging
-	git branch stable-$v master
-
-# update xendocs@xenbits docs generator to generate new stable branch
-#  docs too. commit to git.
-* make 13:37 <ijc> http://xenbits.xen.org/docs/4.2-testing/ is now live true
-#14:17 <ijc> HOWTO: login to xenbits. become "xendocs" . cd cronjobs . edit
-#            xenbits-docs-all.sh in the obvious way. git commit
-	ssh root@xenbits.xen.org
-	su - xendocs
-	cd cronjobs
-	ed xenbits-docs-all.sh
-	/for branch
-	s/$/ 4.6-testing
-	# ^ OR SIMILAR
-	w
-	q
-        git add -p
-	git commit -m "Branch for $v"
-
-### * make symlink on mariner for qemu
-###        cd /var/www/git/
-###        ln -s /usr/groups/xencore/HG/qemu-xen-$v-testing.git .
-
-* make branches etc. in osstest
-        ssh osstest@osstest.test-lab
-	cd testing.git
-	OSSTEST_CONFIG=production-config ./mg-branch-setup xen-$v-testing bisect
-	OSSTEST_CONFIG=production-config ./mg-branch-setup qemu-upstream-$v-testing bisect
-
-* add branch to osstest
-        ie add both eg qemu-upstream-4.2-testing and xen-4.2-testing to BRANCHES in cr-for-branches
-
-* add to patchbot
-        on xenbits
-        cd ~/HG/patchbot/
-
-	cp xen--master.patchbot-reported-heads xen--stable-$v.patchbot-reported-heads
-	cp xen--staging.patchbot-reported-heads xen--staging-$v.patchbot-reported-heads
-        cp qemu-xen--master.patchbot-reported-heads  qemu-xen--stable-$v.patchbot-reported-heads
-        cp qemu-xen--staging.patchbot-reported-heads  qemu-xen--staging-$v.patchbot-reported-heads
-        cp qemu-xen-traditional--master.patchbot-reported-heads qemu-xen-traditional--stable-$v.patchbot-reported-heads
-
-        #emacs versions
-	perl -i~ -pe 'next unless m/\b\Q'$ov'\E\b/; $x=$_; $x=~ s/\b\Q'$ov'\E\b/'$v'/g; print $x;' versions
-        git diff
-	git add versions
-	git commit -m "Branch for $v"
-
-#* update xenbits web page
-        ssh root@xenbits.xen.org
-        cd /var/xenbits-www/html
-        emacs index.html
-	# - search for previous version number, and update in each place found
-	# - in general, drop one old release in favour of the new one
-
-Ensure references to qemu trees in xen.git's Config.mk are updated.
-Check this with
-        grep unstable Config.mk 
-which should produce no output.  Replace as necessary.
-
-Update new stable tree's MAINTAINERS to contain correct info for this stable branch
-
-###* fix new trees' vcs descriptions
-#* make old trees' descriptions "historical"
-#	cd ~/git
-#	perl -i~ -pe "s/unstable/4.6-testing/" qemu-upstream-$v-testing.git/description
-
-----
 
 * check, even for point releases
 *  http://logs.test-lab.xenproject.org/osstest/results/all-branch-statuses.txt
-- 
2.1.4


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

  parent reply	other threads:[~2017-03-09 15:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09 15:19 [PATCH 0/4] misc/release-checklist: Updates prompted by recent release Ian Jackson
2017-03-09 15:19 ` [PATCH 1/4] misc/release-checklist: Remove clearly-obsolete stuff Ian Jackson
2017-03-09 15:19 ` [PATCH 2/4] misc/release-checklist: Remove pre-4.3 tarball target instructions Ian Jackson
2017-03-09 15:50   ` Jan Beulich
2017-03-09 15:53     ` Ian Jackson
2017-03-09 15:55       ` Jan Beulich
2017-03-09 15:19 ` Ian Jackson [this message]
2017-03-09 15:52   ` [PATCH 3/4] misc/release-checklist: Split out branching-checklist.txt Jan Beulich
2017-03-09 15:54     ` Ian Jackson
2017-03-09 15:19 ` [PATCH 4/4] misc/branching-checklist: Call mg-branch-setup in Cambridge too Ian Jackson
2017-03-09 15:53 ` [PATCH 0/4] misc/release-checklist: Updates prompted by recent release Jan Beulich

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=1489072767-21441-4-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=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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).