I'm fairly sure I saw something from Matz saying that post-1.8.0 he
wanted to take some time to bring Rubicon up to date and to use in a
test-first way for future releases. I can't find it now, and there's
always the chance I'm simply putting words in his mouth :)

-- George

> _ I don't think rubicon has kept up to date with the latest
>   changes in ruby. I've been running it about once a week 
>   against whatever's in CVS and have been noticing an increasing
>   number of errors, however I've been using this same ruby in
>   day to day use and have not seen any new bugs. 
> 
> _ I've been meaning to take a closer look at this, but lack of
>   time has been the problem. Rubicon is a great tool, but it 
>   needs to carefully track the language. At this point, I don't
>   think it's useable.