exhaustive testing (was: Kismet and Tiger)

[Jordan K. Hubbard]

On Nov 29, 2010, at 2:09 PM, William Siegrist wrote:

> Of course, "full" run here means it tried all 7000+ ports and built everything it could (somewhere in the 4000's iirc). Anyway, as Josh pointed out, we're doing some backend work on Mac OS Forge still and are trying not to disturb the front end too much. Once that is done, we'll be deploying the MPWA work Joe did. After that, we'll look at building in some build automation, which will probably be a mix of MPAB and Buildbot. Unfortunately, the backend work for Mac OS Forge keeps slipping due to external issues, but we're making progress. 

That's great news, truly!   I'd love to see the back end cranking on building everything in the collection, with new builds being triggered by commits once everything has been verified to either build or not build across the collection as a whole.  Once that is done, we can actually start worrying about the presentation side of things (AKA "front end") and maybe donate some hours (from Apple's side) to create the relevant web interfaces to it.  I know that MacPorts has been in a holding pattern for a long time on this issue, and if there is anything Apple can do to help land the plane here then I'm more than willing to discuss that.

- Jordan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20101129/1a8e2275/attachment.html>