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] xen.git branches

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] xen.git branches
From: Fantu <fantonifabio@xxxxxxxxxx>
Date: Wed, 3 Mar 2010 23:18:14 -0800 (PST)
Delivery-date: Wed, 03 Mar 2010 23:18:38 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B8EA4BE.5050402@xxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4B8EA4BE.5050402@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Now i start to use xen/stable, what are the feature missing?

Jeremy Fitzhardinge wrote:
> Another month, another branch shuffle to confuse everyone ;)
> I've added a couple of new branches:
>     * xen/stable-2.6.31.x - This is currently identical to xen/master. 
>       As its name suggests, it is going to track the 2.6.31.x stable
>       tree.  I don't think there'll be any more 2.6.31.x kernels
>       released, so this will just have Xen-related bugfixes.  Required
>       for pre-Xen 4/3.4.3.
>     * xen/stable-2.6.32.x - This is currently an alias of xen/stable. 
>       2.6.32 is going to be a long-term maintained kernel, so this
>       branch will likely be active for a long time.  It will get both
>       Linux updates and Xen bugfixes+features.  Requires Xen 4 or 3.4.3.
> So what about the other branches?
>     * xen/stable - will always be the most recent "stable" kernel.  For
>       now it will track stable-2.6.32.x, but when we move the main
>       development focus to 2.6.33 and beyond, it will track that stable
>       kernel.  It will be the default branch for xen.git.
>     * xen/master - I haven't quite worked out what to do with this in
>       the medium term.  I'm thinking that I'll make xen/master an alias
>       for xen/stable, since people are already using it as a default
>       branch.  At the moment its still stable-2.6.31.x.
>     * xen/next - Active development branch.  Generally bleeding-edge.
> I'm not quite ready to move xen/next into bleeding-edge phase yet.  The 
> 2.6.32 tree is still missing a few things and needs more testing before 
> I'm happy with it.
>      J
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

View this message in context: 
Sent from the Xen - Dev mailing list archive at Nabble.com.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>