> Deprecating dynamic scaffolding will give the impression to AWDR2 > readers, just when they are starting to work with Rails against a > database, that Rails is not stable.
Any major changes will be held back till 2.0. There's definitely no intention of breaking people's scaffolds in 1.2.3. While I'm probably the most paranoid core-team member when it comes to backwards compatibility, I'd still rather see the framework continue to evolve, rather than stagnate indefinitely to satisfy some people's fear of change :). Eventually that feature will be pulled out to a plugin, but for this release stream, it's fine where it is. -- 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 -~----------~----~----~----~------~----~------~--~---
