From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael Paesold" Subject: Re: FW: [Xen-changelog] Added tag3.0.2-branchedforchangesetd0d3fef37685be264a7f52201f8ef44c030daad3 Date: Wed, 5 Apr 2006 15:51:24 +0200 Message-ID: <058d01c658b8$0978db60$7801a8c0@zaphod> References: <03e401c658b4$18a630a0$7801a8c0@zaphod> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Ian Pratt , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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