[xen master] docs/process/release-checklist.txt: Say to push staging branch

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[xen master] docs/process/release-checklist.txt: Say to push staging branch

patchbot
commit eff2fbe4dd71b3e4fe2dbb2696882252c1cc7897
Author:     Ian Jackson <[hidden email]>
AuthorDate: Wed Dec 13 12:14:28 2017 +0000
Commit:     Ian Jackson <[hidden email]>
CommitDate: Fri Apr 27 15:27:09 2018 +0100

    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 <[hidden email]>
    Acked-by: George Dunlap <[hidden email]>
---
 docs/process/release-technician-checklist.txt | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/process/release-technician-checklist.txt b/docs/process/release-technician-checklist.txt
index 3c7a305b72..c228e1088a 100644
--- a/docs/process/release-technician-checklist.txt
+++ b/docs/process/release-technician-checklist.txt
@@ -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>
 
 
--
generated by git-patchbot for /home/xen/git/xen.git#master

_______________________________________________
Xen-changelog mailing list
[hidden email]
https://lists.xenproject.org/xen-changelog