Eike Rathke <[EMAIL PROTECTED]> writes: > With tests that need 3 days to complete you can be sure that almost no > CWS owner from outside Sun will run these tests. If the tests would be > mandatory you would end up with a situation where Sun engineers would > mirror community CWSs and create install sets and run the tests just to > have it accepted by QA. We'd become regression test drone slaves. No, > thanks. > > If there was some infrastructure where anyone could drop a CWS in that > built install sets and ran the tests things might differ. I just doubt > we'll get that in a foreseeable future. >
and Mathias Bauer wrote: > We shouldn't raise even more barriers to contribution. > This basically circles around the same problem. Tinderbox & BuildBot2 in principle are capable of doing just that. But yeah, having a build in two hours and a test only after two days appears a bit misbalanced to me as well. I don't think that, given a solution as outlined above, this additional CWS exit criterion adds noticeable process overhead - whether the CWS process in itself could be made more light-weight is another question (a development code line comes to mind here, from which the stable branch could cherry-pick features that are sufficiently mature...) Cheers, -- Thorsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
