No, but moving versioning into a configuration option is not the way to do this kind of thing. I'm going to pick arbitrary examples based on another thread in Rails core right now:
Rails 3.3: scaffolding considered deprecated. Add deprecation warnings to all scaffolding stuff. Rilas 3.4: yep, still deprecated Rails 4.0: scaffolding removed. I know there will be no rails 3.3 and 3.4, like I said, arbitrary. Deprecation is good. Doesn't mean we should add _another_ way to determine API compatibility on top of the already existing version numbers. -- 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.
