[Xen-devel] Stable and unstable trees

[Paul Dorman <pauld@xxxxxxxxx>]

Hi all,

thanks for the update for automatic binding of loop devices Mark. Until now 
I've been using the stable tree (xen-2.0bk). I've just cloned the unstable 
tree, and would *like* to work with this if I can (better for you guys too in 
terms of bug reports maybe). May I ask how the stable and unstable trees are 
managed? Do you commit everything to the unstable tree as you work, or do you 
only commit new code after some reasonable degree of testing? Historically, 
how often have things become badly broken in the unstable tree?

Also, how frequently have you been updating the stable tree up until now? Is 
it very close to the unstable tree, or is there quite a lot of new code 
there?

I've been experiencing some unstability in the 2.0bk code, particularly when I 
use ReiserFS formatted LVM partitions with the 2.6 kernel. I have yet to get 
the serial console working (ttyS0) yet, so I have nothing for you as of yet, 
but I am working on that as time permits.

Another thing I've been wondering is whether you have a more fine-grained 
to-do list somewhere, so I can make calls on whether to experiment with the 
unstable tree according to the seriousness of any unresolved issues.

I'm not a developer, but I am willing to submit bug reports, so in your 
opinion should I work with just the stable, or the unstable? What is most 
useful to you?

Thanks as always for your time. I really appreciate the great feedback I've 
had from you guys.

Regards,
Paul


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel