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-ppc-devel

Re: [XenPPC] Re: [Xen-devel] [PATCH 0/6][TOOLS][XM-TEST] [v2] Update xm-

To: Aron Griffis <aron@xxxxxx>
Subject: Re: [XenPPC] Re: [Xen-devel] [PATCH 0/6][TOOLS][XM-TEST] [v2] Update xm-test to support new architectures
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 03 Oct 2006 17:53:45 +0100
Cc: Xen-Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Hollis Blanchard <hollisb@xxxxxxxxxx>, Tony Breeds <tony@xxxxxxxxxxxxxxxxxx>, Ewan Mellor <ewan@xxxxxxxxxxxxx>, XenPPC-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>, Dan Smith <danms@xxxxxxxxxx>
Delivery-date: Tue, 03 Oct 2006 09:52:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061003163945.GC9217@xxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbnDH0Iu94aRFL/EdunNAAX8io7RQ==
Thread-topic: [XenPPC] Re: [Xen-devel] [PATCH 0/6][TOOLS][XM-TEST] [v2] Update xm-test to support new architectures
User-agent: Microsoft-Entourage/11.2.5.060620
On 3/10/06 17:39, "Aron Griffis" <aron@xxxxxx> wrote:

> Keir Fraser wrote:  [Tue Oct 03 2006, 11:59:28AM EDT]
>> Xen-unstable is currently a staging tree for xen-3.0.3-testing. Development
>> is frozen until 3.0.3-0 is released.
> 
> Hi Keir,
> 
> Why are you doing it this way?  I thought a staging tree was somewhere
> you could test builds prior to moving changesets to the live tree, so
> you could yank the changesets, reset the staging tree, etc. without
> affecting anybody.  Shouldn't there be a separate staging tree for
> xen-3.0.3-testing?  Plus if xen-unstable is staging for
> xen-3.0.3-testing, then it seems like branching was pointless.

Since development is frozen to concentrate on bug fixing, we may as well use
xen-unstable as the staging point for candidate patches rather than creating
an entirely new tree. Creating an explicit xen-3.0.3-testing tree and
announcing official release candidates encourages a broader range of people
to test the code (many will not touch xen-unstable at all).

Development is not frozen because we are using xen-unstable as a staging
tree. It is frozen simply because we are at the bug-fixing stage in the
release cycle.

 -- Keir



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