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.

Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
Acked-by: George Dunlap <george.dunlap@citrix.com>
This commit is contained in:
Ian Jackson authored and Ian Jackson committed 2018-04-27 15:27:09 +01:00
1 parent 729960f085
commit eff2fbe4dd
1 file changed
+1
@@ -68,6 +68,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>
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.