On Fri, Jul 25, 2008 at 07:20:20PM +0900, Vladimir Sizikov wrote:

> Also, since RubySpec is always evolving, with the commits daily, there
> is always a chance that all tests passed 5 minutes ago and now there
> are some failures due to new commits.
> 
> In JRuby (and Rubinius) we deal with this fluid situation by
> introducing the notion of "stable" or "frozen" specs, fixing particual
> revision to avoid newly-introduced changes and to reduce instability.
> 
> >From time to time, the "stable/frozen" pointer gets updated to newer
> revision (and the excludes are updated, and bugs are filed if needed)
> so that there are no failures.

Are there  remote branches  that we could  track to follow  the stable
specs?  That way we could easily tell if a failure was due to a recent
spec change.  Or is there a better way to do it?

Regards, 

Jeremy Henty