[cosmo-dev] Cosmo .10 testing status

[Mikeal Rogers]

>> I think adam uses a version of Windmill that is custom or hasn't  
>> been pushed as a release - the tinderboxes are running now for two  
>> browsers and showing test failures.  I upgrade them when I get  
>> notified of new windmill versions and right now that is when I see  
>> the announcement either on the windmill list or via cheeseshop.

Our policy _should_ be to have the tests in the cosmo/test/functional/ 
windmill be supported by the latest release of windmill. Tests should  
not be checked in to the cosmo repo that depend on pre-release  
windmill code.

 From now on let's assume that any failures of latest release windmill  
testing the latest tests in the cosmo repo are valid failures and  
refrain from checking in any tests that rely on pre-release code. It's  
very easy to push a windmill bugfix release to the cheeseshop and  
announce so the *release* bit shouldn't be a bottleneck for anyone. If  
the issue is that we're writing tests that rely on code that doesn't  
work in windmill yet then we shouldn't be checking those tests in to  
the cosmo repository.

Bear, would you like a feed or something more automated to notify you  
when windmill updates release? I know the windmill blog has a feed but  
we could stick up something smarter if you like.

-Mikeal