| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] 2.6.18 kernel status
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> Daniel P. Berrange
> Sent: 06 March 2007 17:20
> To: Keir Fraser
> Cc: John Hannfield; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] 2.6.18 kernel status
>
> On Tue, Mar 06, 2007 at 10:28:38AM +0000, Keir Fraser wrote:
> >
> > On 5/3/07 23:53, "John Hannfield" <hal9020@xxxxxxxxx> wrote:
> >
> > > I am just trying out the 2.6.18 kernel in xen-unstable.hg
> , but on doing a
> > > make linux-2.6-xen0-build I'm getting to the following error.
> >
> > This is fixed but the patch is stuck in our staging tree
> until regression
> > tests pass.
>
> How about making your staging tree publically viewable so
> people get better
> visibility into whether patches sent to xen-devel have been
> picked up and
> integrated into the tree ? Sure, we don't want people to be
> actually working
> against a staging tree, but I think being able to see what's
> coming along
> in the staging tree would be good for transparency /
> communications with
> the non-XenSource people whom are posting patches.
The whole point of the staging tree is to get xen-unstable a bit more
stable. All changes come to the Xen-unstable tree eventually - and
usually within hours of hitting the staging tree.
As you probably are aware, the stability of Xen-unstable isn't always
wonderfull DESPITE going through the "basic test suite" - because it's
just basic automated testing.
Adding a "unstabler-unstable" isn't a great idea for MOST people - so it
would be of fairly limited use.
>
> In this particular instance it would also allow for end-user
> testing of
> the aforementioned kernel patch in parallel with the automated tests,
> rather than serializing the test proces.
In some circumstances this may be to an advantage, but for most cases, I
would say it's not particularly helpful.
--
Mats
>
> Regards,
> Dan.
> --
> |=- Red Hat, Engineering, Emerging Technologies, Boston. +1
> 978 392 2496 -=|
> |=- Perl modules: http://search.cpan.org/~danberr/
> -=|
> |=- Projects: http://freshmeat.net/~danielpb/
> -=|
> |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF
> F742 7D3B 9505 -=|
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home