On 3/10/06 17:39, "Aron Griffis" <[EMAIL PROTECTED]> 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-ppc-devel mailing list [email protected] http://lists.xensource.com/xen-ppc-devel
