This is an update to my 1.9 status report from 3 weeks ago. The short story is: we're set to release 1.5 at the end of the month and we're going to import our code into ruby trunk shortly. This release has workarounds for the 1.9.2 upgrade problems we've been seeing.
Luis: heads up. See last paragraph. On Dec 21, 2010, at 17:00 , Ryan Davis wrote: > I just pulled the rubygems in ruby-core's trunk into our 1.9 branch and > tweaked it enough to make it pass under 1.8.7. The changes were minimal to > lib and mostly just annoying in test. I've pushed this back up so that others > can review. > > Moving forward: > > + I'm prolly gonna move everything from test/* to test/rubygems/* to match > ruby-core. They switched us to require_relative on everything (ugh). done > + We need to selectively pull additions and changes from the 1.9 branch to > master. > + I don't have a handle on what (or why) changes have happened on ruby trunk. > + Input is welcome. > + It is about 3k line o' diff. Help is welcome too. done - I think... Eric and I reviewed the diffs and we brought over a minimum of changes. See 36e6afff7bb3c14e03a71c1cf1a61c03a7da685c for specifics. > + Once we reconcile differences between the 1.9 branch and master, we nuke > the 1.9 branch and push all our changes to ruby trunk. This will be done when we release... I'm ready and prepping my push back to ruby trunk. > + ruby trunk pushes will be automated and include a warning header in every > file. done > + Any changes that occur in ruby trunk will be reverted immediately. > + I'd rather push every single day to ruby trunk than to ever do this > reconciliation again. And we already had to do one. :/ Nobu made a 1.8-incompatible change w/o a test so I reverted it today. > Raggi says that he's close to a rack release, which is the big blocker for > rails, which is our big blocker. He estimates the dam will break sometime > this week and we'll be free to release after that. The dam was broken for our 1.4 release on our side. It seems to have gone well (enough). Eric's changes are in that make this work against 1.9.2 (w/ rubygems 1.3.7 installed). Luis, if you have any platform showstoppers, we need to know about them soon. Manual testing seems to show that this thing works and we'll get the 1.9.2 problems flushed out when we release 1.5.0. _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
