Chad Fowler wrote:

> I'm sure that any help on Rubicon would be welcome, but it's Dave's baby 
> (he's out of town, I believe).

Rubicon was an attempt to give the Ruby committees a way to test 
changes, and to document differences between versions (using the 
versioning tests).

I'm really not in a position to be able to reverse engineers every CVS 
commit into a set of tests: in an ideal world, the tests would be 
updated by the author of every functional change.

I view Rubicon as a totally shared resource. If folks have fixes or new 
tests to apply, I'd welcome them.


Cheers



Dave