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

[Xen-devel] [PATCH] docs/process/release-checklist.txt: Say to push staging branch



Preparing a real release, not just an RC, involves making commits.
Typically, those will be on staging-$x.  The tag will refer to them,
and the checklist already says to push them to xenbits.

But if the *branch* is not pushed, then people who just "git fetch"
won't get the tag because it refers to commits they don't have.
(Because of the strange rules git has about tag fetching.)
Worse, the same may be true of people who "git clone".

And anyway, those commits *should* be fed to staging-$x.

CC: George Dunlap <george.dunlap@xxxxxxxxxx>
Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
---
 docs/process/release-checklist.txt | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/process/release-checklist.txt 
b/docs/process/release-checklist.txt
index c83ff7f..7018629 100644
--- a/docs/process/release-checklist.txt
+++ b/docs/process/release-checklist.txt
@@ -66,6 +66,7 @@ t=RELEASE-$r
   git-show # should show commit updating version to right version
   git-tag -u 'xen tree' -s -m "Xen $r$rc" $t
   git-push origin $t
+  git-push origin staging-$x
 ##  hg tag <tag_name> ; hg sign -k "Xen tree" <tag_name>
 
 
-- 
2.1.4


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

 


Rackspace

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