On Aug 16, 2011, at 5:20 PM, John Clements wrote:

>> 
>> I think it's been mentioned before, but automated testing of PLaneT packages 
>> by the PLaneT server/repository would be nice.  For starters, just see 
>> whether they can be compiled and "require"d without error (in a sandbox).  
>> Would be nice to test multiple Racket versions.  Later, as we get 
>> standardized entry point for running test suites, the repository could even 
>> detect regressions with new Racket versions and with combinations of 
>> different versions of PLaneT packages on which a package depends.  
>> Regressions in a supposedly backward-compatible version, or even any test 
>> failure at all, could even trigger suspension of the version from new use 
>> until a human approves it.  This is something doable on the repository side, 
>> and something that simply won't get done if we're expecting individual 
>> package authors to do it for their packages.
> 
> +1.
> 
> Also, I think it would be very helpful to try to compute the dependencies of 
> a given planet package, and also a relative measure of its compile time.


We (Jay, Robby, Matthew, Eli, and I) have been thinking along these lines for a 
few weeks. Robby is slowly putting the infrastructure into place for these 
things to happen eventually. -- Matthias


_________________________________________________
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/users

Reply via email to