Anthony Liguori wrote:

Is it perhaps wise, nearing 3.0, that we adopt a policy of running the various test suites on code before it gets pushed to the public tree? This seems like requiring passing on xm-test a sane thing to do for the tools related changes. Is there anything that needs to be done to the test suites to make this less painful for the committers? Just to clarify, I'm suggesting that all changes should be checked (external patches or Cambridge pushes) against the testsuites before committing. Just seems like it would be a good way to ensure that we avoid regressing as we near 3.0 release.

Yep, agree. That will be an additional incentive to get tests up to
speed asap before continuing further work.
thanks,
Nivedita
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel