[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Reconciling multiple Xen flavored development streams


  • To: mike.dickson@xxxxxx
  • From: Christian Limpach <christian.limpach@xxxxxxxxx>
  • Date: Wed, 1 Apr 2009 17:55:42 -0700
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 01 Apr 2009 17:56:13 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; b=Hb8tx1CQMCVfXRanaTmTfbW+ooLu/TwmnEqxpp9lXAZ0x3emnsXo8qToH8LGym7Yx5 D8dJkG5haYmpcJg/xeRMQcQFyqWeZlaTfPgNKMJPNPeD5VZVM91qJh3x127mqgqUJjhr saovo3fRqaY76YCR6x99Ct92NwXddDUOnmNqQ=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Wed, Apr 1, 2009 at 7:33 AM, Mike Dickson <mike.dickson@xxxxxx> wrote:
> There are a number of very interesting and obviously active projects
> that seem to be developing different forks of the Xen work. There's the
> mainstream "server" Xen in the form of Xen unstable, XenClient and now
> kXen.  All good stuff but as someone working in the space I'm interested
> how and if any of this gets merged.  There was a comment about kXen
> targeting the 3.4 release as well as unstable. What does that mean? I'd
> have expected that since 3.4 is frozen the only place it could go is
> unstable.

I meant that KXen will be developed on top of 3.4 (to have a stable
base) and that we'll merge it into xen-unstable.

    christian

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.