On Jun 6, 2009, at 12:10 AM, Michael Koziarski wrote: > The best way to help right now is to go through tickets and if they > look like they should be a blocker, reply to this thread with the > message. The criteria for blocking this point release should be: > > * Breaks something which worked in 2.3.2 (automatically a blocker) > * Fixes something broken from 2.2.2 (probably a blocker)
I just posted a rollup ticket (#2773) for a bunch of small fixes to the config.gem stuff. https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2773 Most of what that patch covers were regressions in 2.3.2 from previous behavior. On a related note, it would be nice to get in #2682 (makes a better error message when dependencies are missing) and #1757 (loads generators correctly from vendor/gems). The latter isn't a regression, as it hasn't ever worked right before... :) Finally, on a thoroughly *unrelated* note, the patch from #1703 would be nice, if only to stop it being reported over and over. There have been quite a few duplicates of that ticket. --Matt Jones --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
