On Jun 28, 2008, at 12:29 AM, Igal Koshevoy wrote:

> M. Edward (Ed) Borasky wrote:
>> Well ... I don't think it's so much a lack of manpower as a lack of  
>> hardware for the insane amount of testing and SCM automation that  
>> needs to be done. So ... suppose we limit this to everybody that  
>> can run Rails. That way, we get more test suites. So that's MRI  
>> 1.8.6/1.8.7, IronRuby, jRuby, and Rubinius, right? Or does KRI run  
>> Rails now?
>>
>> What's the hardware/OS collection required? At least MacOS, Linux,  
>> Windows, Solaris and one of the server-grade BSD variants. How many  
>> different versions of GCC need to be tested? There's only one  
>> platform that needs to be available for jRuby testing -- the latest  
>> JVM. Would we need to test on anything besides x86, x86_64, and  
>> SPARC?
> I think this is easier than you think.
>
> For instance, I test AutomateIt releases against a single machine  
> with 10 VMs on it, ranging from XP to OS X, Ubuntu to OpenBSD.

Is Charles talking about bugs in specific architectures? I got the  
impression he was instead talking about features that  should or  
should not be included in each release. Whether or not those features  
actually work on a particular machine would then be a QA-type issue.


Dave