On Mon, 2010-08-02 at 12:12 +0530, Rahul Sundaram wrote: > On 08/02/2010 12:04 PM, Adam Williamson wrote: > > We aren't. The automated tests Rui refers to happen prior to branching. > > They were effectively tests of F14, therefore, but the Python 2.7 > > transition happened *since* the last automated test run, so we hadn't > > had any automated tests done with the Python 2.7 stack. > > > > pjones said he made it through a full install with a Python 2.7 tree, > > though, so I'm not sure how that worked out but the TC didn't. Well, I > > guess we'll investigate and push a TC2 ASAP. > > Yeah, I think we shouldn't do a TC release without confirming that the > compose runs through the full set of automated tests we have. If I am > willing to run such tests in my own system, how do I go about doing > that? Is it easy to participate? What is the image called before it passes the tests? A "test compose candidate"? Personally, it doesn't bother me too much if a so-called "test compose" is broken. -- Matt -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
