WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] RE: New Release Process

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] RE: New Release Process
From: Paul Larson <pl@xxxxxxxxxx>
Date: Fri, 27 Jan 2006 15:45:31 -0600
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 27 Jan 2006 21:54:45 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D40A3A3@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <A95E2296287EAD4EB592B5DEEFCE0E9D40A3A3@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5 (Windows/20051201)
Ian Pratt wrote:
What do you think? Should we stick with 2.6.15 or go to 2.6.16-rc1 ?
I agree that skipping 2.6.15 and going straight to the 2.6.16 latest rc kernels would be a good thing, however I'm confused about one thing (or more likely I'm just dense). Are you looking at pulling in one of the alternate kernel hg trees on xenbits, or just manually updating the sparse tree to 2.6.16-rc1. We have the 2.6.16 subarch merge tree, the 2.6.16 merge tree under ext, and the hvm tree under ext also. Is one of these going to become the new basis for the sparse tree?

Another question this brings up: what is the process for syncing relevant changes and fixes between sparse, 2.6 merge, 2.6 subarch, and the hvm tree? Is there any plan to consolidate these?

Thanks,
Paul Larson


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel