Release, RC5, and branching

Release, RC5, and branching

[George Dunlap]

So it's now been several days, and no one has reported any major issues 
with RC4.  There are a handful of ARM-related fixes in the tree.

I propose that we tag RC5 today, and make that the official release 
(whenever we're ready to with the Linux Foundation PR process).

After tagging RC5 this afternoon, I don't see much reason not to branch 
-- I don't think at this point we're going to get much more testing in.

Thoughts?

  -George

Re: Release, RC5, and branching

[Jan Beulich]

>>> On 21.02.14 at 15:03, George Dunlap <george.dunlap@eu.citrix.com> wrote:
> So it's now been several days, and no one has reported any major issues 
> with RC4.  There are a handful of ARM-related fixes in the tree.
> 
> I propose that we tag RC5 today, and make that the official release 
> (whenever we're ready to with the Linux Foundation PR process).
> 
> After tagging RC5 this afternoon, I don't see much reason not to branch 
> -- I don't think at this point we're going to get much more testing in.
> 
> Thoughts?

Fine with me, albeit it seems a bit pointless to me to have another
RC, in particular if we expect this to become the release.

Jan

Re: Release, RC5, and branching

[George Dunlap]

On 02/21/2014 02:18 PM, Jan Beulich wrote:
>>>> On 21.02.14 at 15:03, George Dunlap <george.dunlap@eu.citrix.com> wrote:
>> So it's now been several days, and no one has reported any major issues
>> with RC4.  There are a handful of ARM-related fixes in the tree.
>>
>> I propose that we tag RC5 today, and make that the official release
>> (whenever we're ready to with the Linux Foundation PR process).
>>
>> After tagging RC5 this afternoon, I don't see much reason not to branch
>> -- I don't think at this point we're going to get much more testing in.
>>
>> Thoughts?
> Fine with me, albeit it seems a bit pointless to me to have another
> RC, in particular if we expect this to become the release.

Isn't that what RC stands for -- release candidate? :-)

  -George

Re: Release, RC5, and branching

[Ian Jackson]

George Dunlap writes ("Release, RC5, and branching"):
> So it's now been several days, and no one has reported any major issues 
> with RC4.  There are a handful of ARM-related fixes in the tree.
> 
> I propose that we tag RC5 today, and make that the official release 
> (whenever we're ready to with the Linux Foundation PR process).
> 
> After tagging RC5 this afternoon, I don't see much reason not to branch 
> -- I don't think at this point we're going to get much more testing in.

OK.  I'll do the branch after the RC5 tarball is made.

Also we should do the checklist items that involve changes to the
xen.git tree, ASAP after RC5 and branching, so that ideally we get a
test push from the new staging-4.4 branch onto stable-4.4 before the
release.

How sure are we that the qemu trees we will be releasing with are the
ones in RC5 ?  If we're sure then we could make the release tags now.

Ian.

Re: Release, RC5, and branching

[Ian Jackson]

Ian Jackson writes ("Re: Release, RC5, and branching"):
> George Dunlap writes ("Release, RC5, and branching"):
> > After tagging RC5 this afternoon, I don't see much reason not to branch 
> > -- I don't think at this point we're going to get much more testing in.
> 
> OK.  I'll do the branch after the RC5 tarball is made.

The RC5 tags and tarball are in the usual places.  George, do you want
to send an RC announcement ?

Ian.

Re: Release, RC5, and branching

[Andrew Cooper]

On 21/02/14 16:30, Ian Jackson wrote:
> Ian Jackson writes ("Re: Release, RC5, and branching"):
>> George Dunlap writes ("Release, RC5, and branching"):
>>> After tagging RC5 this afternoon, I don't see much reason not to branch 
>>> -- I don't think at this point we're going to get much more testing in.
>> OK.  I'll do the branch after the RC5 tarball is made.
> The RC5 tags and tarball are in the usual places.  George, do you want
> to send an RC announcement ?
>
> Ian.

What about changing the build to not be debug by default, and the main
Xen version?  They will need to be done before the release.

~Andrew

Re: Release, RC5, and branching

[George Dunlap]

On 02/21/2014 04:52 PM, Andrew Cooper wrote:
> On 21/02/14 16:30, Ian Jackson wrote:
>> Ian Jackson writes ("Re: Release, RC5, and branching"):
>>> George Dunlap writes ("Release, RC5, and branching"):
>>>> After tagging RC5 this afternoon, I don't see much reason not to branch
>>>> -- I don't think at this point we're going to get much more testing in.
>>> OK.  I'll do the branch after the RC5 tarball is made.
>> The RC5 tags and tarball are in the usual places.  George, do you want
>> to send an RC announcement ?
>>
>> Ian.
> What about changing the build to not be debug by default, and the main
> Xen version?  They will need to be done before the release.

Hmm, arguably that should be done once we start RCs, I would have 
thought, so we're actually testing the codepaths we plan on releasing.

  -George

Re: Release, RC5, and branching

[Jan Beulich]

>>> On 21.02.14 at 17:54, George Dunlap <george.dunlap@eu.citrix.com> wrote:
> On 02/21/2014 04:52 PM, Andrew Cooper wrote:
>> On 21/02/14 16:30, Ian Jackson wrote:
>>> Ian Jackson writes ("Re: Release, RC5, and branching"):
>>>> George Dunlap writes ("Release, RC5, and branching"):
>>>>> After tagging RC5 this afternoon, I don't see much reason not to branch
>>>>> -- I don't think at this point we're going to get much more testing in.
>>>> OK.  I'll do the branch after the RC5 tarball is made.
>>> The RC5 tags and tarball are in the usual places.  George, do you want
>>> to send an RC announcement ?
>>>
>>> Ian.
>> What about changing the build to not be debug by default, and the main
>> Xen version?  They will need to be done before the release.
> 
> Hmm, arguably that should be done once we start RCs, I would have 
> thought, so we're actually testing the codepaths we plan on releasing.

I think we changed to non-debug builds pretty late in the process
of all earlier releases.

Jan

Re: Release, RC5, and branching

[Dario Faggioli]

[-- Attachment #1.1: Type: text/plain, Size: 967 bytes --]

On ven, 2014-02-21 at 16:54 +0000, George Dunlap wrote:
> On 02/21/2014 04:52 PM, Andrew Cooper wrote:
> > What about changing the build to not be debug by default, and the main
> > Xen version?  They will need to be done before the release.
> 
> Hmm, arguably that should be done once we start RCs, I would have 
> thought, so we're actually testing the codepaths we plan on releasing.
> 
On one hand, that makes a lot of sense. On the other hand, perhaps,
having debug=y makes it easier to look at bugs reported by people
actually testing the RCs?

Perhaps, for next time of course, switch to debug=n when we feel like
we're ~ in the middle of the RC process?

just my 2 cents,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Release, RC5, and branching

[George Dunlap]

On 02/21/2014 04:16 PM, Ian Jackson wrote:
> George Dunlap writes ("Release, RC5, and branching"):
>> So it's now been several days, and no one has reported any major issues
>> with RC4.  There are a handful of ARM-related fixes in the tree.
>>
>> I propose that we tag RC5 today, and make that the official release
>> (whenever we're ready to with the Linux Foundation PR process).
>>
>> After tagging RC5 this afternoon, I don't see much reason not to branch
>> -- I don't think at this point we're going to get much more testing in.
> OK.  I'll do the branch after the RC5 tarball is made.
>
> Also we should do the checklist items that involve changes to the
> xen.git tree, ASAP after RC5 and branching, so that ideally we get a
> test push from the new staging-4.4 branch onto stable-4.4 before the
> release.

Yes, please do the branch.

>
> How sure are we that the qemu trees we will be releasing with are the
> ones in RC5 ?  If we're sure then we could make the release tags now.

Is there a cost to waiting for the release tags?  I don't know exactly 
how we want to arrange the timing of the release with the press 
announcement, but if it wouldn't cause too much hassle / risk of missing 
something, it might be better to wait until the day of our official 
announcement, probably a week monday.

  -George

Re: Release, RC5, and branching

[Ian Jackson]

George Dunlap writes ("Re: Release, RC5, and branching"):
> On 02/21/2014 04:16 PM, Ian Jackson wrote:
> > How sure are we that the qemu trees we will be releasing with are the
> > ones in RC5 ?  If we're sure then we could make the release tags now.
> 
> Is there a cost to waiting for the release tags?  I don't know exactly 
> how we want to arrange the timing of the release with the press 
> announcement, but if it wouldn't cause too much hassle / risk of missing 
> something, it might be better to wait until the day of our official 
> announcement, probably a week monday.

If we wait then we have to either (a) have old tags in Config.mk (eg
references to -rc5) or (b) release something that is still in
staging-4.4 and not in stable-4.4 yet.

If you're thinking about a release in a bit over a week we can
probably expect a test pass if we do the Config.mk etc. changes early
next week, but I'm not sure I see a reason to wait.

Ian.

Re: Release, RC5, and branching

[Ian Jackson]

Jan, I have made the {staging,stable}-4.4 branches in xen.git.

My release checklist says:

  Update new stable tree's MAINTAINERS to contain correct info for this
  stable branch

Will you take care of this ?  I'm not sure if it's just as simple as
copying the file from staging-4.3.  Please push the update to
staging-4.4.

thanks,
Ian.

Re: Release, RC5, and branching

[Jan Beulich]

>>> On 21.02.14 at 17:51, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote:
> Jan, I have made the {staging,stable}-4.4 branches in xen.git.
> 
> My release checklist says:
> 
>   Update new stable tree's MAINTAINERS to contain correct info for this
>   stable branch
> 
> Will you take care of this ?  I'm not sure if it's just as simple as
> copying the file from staging-4.3.  Please push the update to
> staging-4.4.

Sure, I'll take care of this (but I'm wonder whether I rather
should do this after the release).

Jan