> But how do we get ruby-core to release 1.9.2 w/ our change? I've been asking > for weeks and heard nothing to approve of or deny such a release. Suggestions?
Just read your and Yusuke's latest...a few comments: 1) Show time ./ruby -ve '' on ruby 1.9.2p136 (2010-12-25 revision 30363) in addition to trunk...hopefully these numbers will be larger than his ruby 1.9.3dev (2011-01-14 trunk 30544) [i686-linux] results showing the patches incrementally improve startup performance as well. 2) Summarize your positive cross-platform testing results. FWIW I upgraded to 1.4.2 on ruby 1.8.7 (2010-12-23 patchlevel 330) [i386-mingw32] and haven't yet had a problem, but I've not really stressed it. Luis probably has some good Windows data you could include. Maybe summarize how well the new patch works for some well known users and well known gems? 3) Rerereresummarize the critical mods (high level) addressed by 1.4.x patch. 4) Reiterate your plan (and timeline) to first fix the 1.9.x upgrade issue and then incrementally address any performance issues. Hopefully this in combo with (1) will show that at least things are no worse off performance wise than what exists on 1.9.2p136. Jon --- blog: http://jonforums.github.com/ _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
