All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] docs/process/release-checklist.txt: Say to push staging branch
@ 2017-12-13 12:17 Ian Jackson
  2017-12-13 12:19 ` George Dunlap
  0 siblings, 1 reply; 2+ messages in thread
From: Ian Jackson @ 2017-12-13 12:17 UTC (permalink / raw)
  To: xen-devel; +Cc: Ian Jackson, George Dunlap

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@citrix.com>
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
---
 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@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] docs/process/release-checklist.txt: Say to push staging branch
  2017-12-13 12:17 [PATCH] docs/process/release-checklist.txt: Say to push staging branch Ian Jackson
@ 2017-12-13 12:19 ` George Dunlap
  0 siblings, 0 replies; 2+ messages in thread
From: George Dunlap @ 2017-12-13 12:19 UTC (permalink / raw)
  To: Ian Jackson, xen-devel

On 12/13/2017 12:17 PM, Ian Jackson wrote:
> 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@citrix.com>
> Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>

Acked-by: George Dunlap <george.dunlap@citrix.com>

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-12-13 12:19 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-12-13 12:17 [PATCH] docs/process/release-checklist.txt: Say to push staging branch Ian Jackson
2017-12-13 12:19 ` George Dunlap

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.