[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-changelog] [xen master] misc/release-checklist.txt: Preemptive updates



commit cd8b69c2bd1a33b99fc0cdf780e84fde603bb490
Author:     Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
AuthorDate: Wed Apr 12 16:31:40 2017 +0100
Commit:     Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
CommitDate: Wed Apr 12 16:33:53 2017 +0100

    misc/release-checklist.txt: Preemptive updates
    
    These are things I noticed should be fixed, while trying to make
    4.9.0-rc1.
    
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
---
 misc/release-checklist.txt | 43 ++++++++++++++++++-------------------------
 1 file changed, 18 insertions(+), 25 deletions(-)

diff --git a/misc/release-checklist.txt b/misc/release-checklist.txt
index 4784256..f9e7e06 100644
--- a/misc/release-checklist.txt
+++ b/misc/release-checklist.txt
@@ -1,14 +1,4 @@
 
-* check, even for point releases
-*  http://logs.test-lab.xenproject.org/osstest/results/all-branch-statuses.txt
-
-* check, even for point releases, advisory patch application status (Lars)
-
-* make tag in qemu-iwj.git
-
-* push qemu tag in xenbits.xen.org             git-update-server-info
-* push qemu tag in xenbits.xen.org staging     git-update-server-info
-
 s=master
 #b=unstable
 v=$v-rc1
@@ -28,8 +18,13 @@ t=$r$rc
 OR
 t=RELEASE-$r
 
+
 # FIRSTLY
-#  - check all XSAs have been applied
+#  - check (for point releases, but not RCs) all XSAs have been applied (Lars)
+#
+* check, even for point releases
+*  http://logs.test-lab.xenproject.org/osstest/results/all-branch-statuses.txt
+
 
 # QEMU
 
@@ -43,8 +38,8 @@ t=RELEASE-$r
   git push xen@xxxxxxxxxxxxxxx:/home/xen/git/mini-os.git xen-$t
 
 * Also tag upstream qemu tree (Stefano)
-    git tag -u 'xen tree' -s -m "Xen $r$rc" qemu-xen-$r SOMETHING
-    git push osstest@xxxxxxxxxxxxxxx:/home/xen/git/qemu-xen.git qemu-xen-$r
+    git tag -u 'xen tree' -s -m "Xen $r$rc" qemu-xen-$v SOMETHING
+    git push osstest@xxxxxxxxxxxxxxx:/home/xen/git/qemu-xen.git qemu-xen-$v
 
 * consider bumping sonames of shlibs
 
@@ -82,6 +77,7 @@ HANDLING TAG GENERATED BY RELEASE MANAGER
 
 
 
+
 RELEASE TARBALL
 
    for 4.5 and later, use tarball target
@@ -95,9 +91,8 @@ RELEASE TARBALL
        mkdir /volatile/iwj/website-thing/xen.org/oss-xen/release/$v
        mv dist/xen-$v.tar.gz 
/volatile/iwj/website-thing/xen.org/oss-xen/release/$v/.
 
-        # website-thing is cvs -d 
hg.uk.xensource.com:/usr/groups/sources/cvs/akamai co xen.org
+       # website-thing/xen.org is cvs -d 
mail.xenproject.org:/home/downloads-cvs/cvs-repos co xen.org
        cd /volatile/iwj/website-thing/xen.org
-       mkdir oss-xen/release/$v
 
 # test build
                 cd /volatile/iwj/d
@@ -114,21 +109,19 @@ RELEASE TARBALL
        cvs add -kb oss-xen/release/$v/
 
         cd oss-xen/release/$v
-        gpg --detach-sign -u 'xen tree' xen-$v.tar.gz
+        gpg --digest-algo=SHA256 --detach-sign -u 'xen tree' xen-$v.tar.gz
        cvs add -kb xen-$v.tar.gz
         cvs add -kb xen-$v.tar.gz.sig
         cd ../../..
 
        cvs ci -m $v
-       ./upload.sh
-
-        AND (can be done in parallel with ./upload.sh)
-           ssh downloads-cvs@xxxxxxxxxxxxxxxxxxx
-          cd /data/downloads.xenproject.org/xen.org
-          cvs -q up -d
-          # should show something like
-          #   U oss-xen/release/4.8.0-rc2/xen-4.8.0-rc2.tar.gz
-          #   U oss-xen/release/4.8.0-rc2/xen-4.8.0-rc2.tar.gz.sig
+
+        ssh downloads-cvs@xxxxxxxxxxxxxxxxxxx
+       cd /data/downloads.xenproject.org/xen.org
+       cvs -q up -d
+       # should show something like
+       #   U oss-xen/release/4.8.0-rc2/xen-4.8.0-rc2.tar.gz
+       #   U oss-xen/release/4.8.0-rc2/xen-4.8.0-rc2.tar.gz.sig
 
 
 update xenbits front page to change references to old stable branch
--
generated by git-patchbot for /home/xen/git/xen.git#master

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxx
https://lists.xenproject.org/xen-changelog

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.