On Sun, Jan 9, 2011 at 6:34 AM, Ryan Davis <ryand-r...@zenspider.com> wrote: > > On Jan 9, 2011, at 02:56 , Chad Woolley wrote: > >> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p430 > > This isn't reproducible on my side. I've got a clean run using rvm. Ah... rvm > installed ruby 1.9.1p378. It is clean. 1.9.1p430 apparently has some > regression in it on its side. > > Please back up to 378 for the time-being. > > I just installed using "1.9.1" as my specifier. You might want to do the same > for all of them so you're not constantly maintaining the versions. > >> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_2-p0 > > This isn't up to date anymore.
OK, so to be clear, we want to try to commit to trying to keep the latest (according to RVM) ruby releases green for 1.8.7, 1.9.1, and 1.9.2? Pretty sure that is always the latest patch release, but sometimes Wayne overrides the default to not be the latest if there are problems (e.g. when there were segfaults in some of the < 1.8.7p299 releases). Thanks, -- Chad _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
