> > what is the rails' versioning number policy? > > If you remember, Rails 1.2.x releases where tagged from the "1.2 stable" > branch. The name itself implies that there should be no breaking API > changes. What happened here, IMO, is an overlook while applying bugfixes. > Deprecated methods were meant to disappear in 2.0, not 1.2.x ...
The intention with the stable releases is that no part of our public api (the stuff documented in the api docs) breaks. If there are changes which have broken that, let us know by opening a ticket or mailing this list, we're already intending on another 1.2.x release to fix an associations regression introduced when fixing a performance issue with unsaved associations. Plugins *will* break if they're messing with private methods, there's no way we can guess what private / implementation methods are being overridden. In the event that we keep busting a non-intrusive plugin, we can look at providing a stable API which will remain unbroken during a point release. The changes like render_action disappearing only happened in trunk, so you're obviously running the 'fake' 1.2.x releases which are now labeled more clearly. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
