This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] FW: [Xen-changelog] Added tag3.0.2-branchedforchangesetd

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] FW: [Xen-changelog] Added tag3.0.2-branchedforchangesetd0d3fef37685be264a7f52201f8ef44c030daad3
From: "Michael Paesold" <mpaesold@xxxxxx>
Date: Wed, 5 Apr 2006 15:51:24 +0200
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 05 Apr 2006 06:52:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D4BA101@xxxxxxxxxxxxxxxxxxxxxxxxxxx><03e401c658b4$18a630a0$7801a8c0@zaphod> <d76566958ed57d4bf2951fbf86442031@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Keir Fraser wrote:
On 5 Apr 2006, at 14:23, Michael Paesold wrote:

I have noticed that the 3.0.2 release candidate tree/repository is obviously not the one available as 3.0-testing on the XenSource website. Is it available for public consumption anywhere? Guessing from some emails, I think that you are applying bugfixes to that -testing repo, no? I would like to test this rc before release, but without access to it, I am limited to what is available in xen-unstable.

We have a 'rolling' release process in which bugfixes will be applied to the 3.0.2 branch even after an initial release is declared. So even after we have pushed '3.0.2' out to the public tree, public testing, bug reports and bug fixes will be very welcome.

I have already learned about the general release process here, now I have a name for it, too. ;-)

Currently I would estimate we'll make the tree public tomorrow: we want to do one more full regression-testing run, and also do a full workout of older domU kernels (3.0.0 and 3.0.1) on 3.0.2 to ensure we have maintained full backward compatibility.

Ah, thanks for the quick heads up. Btw. I appreciate your extensive testing, thanks!

Best Regards,
Michael Paesold

Xen-devel mailing list