All, I'm starting to work no migrating an app. from 1.1.6 to 1.2.3 and the deprecation warnings are very helpful and detailed enough, I think. However, it would be really nice to know the earliest version for which a given solution may be used, so that I know how many fixes I can backport to 1.1.6. For example, if I see this: "DEPRECATION WARNING: The :exclusively_dependent option is deprecated and will be removed from Rails 2.0. Please use :dependent => :delete_all instead.", my question would be, is it possible to make the appropriate changes under 1.1.6 or not? In the absence of such information, I assume that none of these changes will work under 1.1.6. It seems very possible that changes to certain things may make it into the core distribution before any associated deprecation warnings. Are there any plans to either a) identify the earliest version for the new idiom as part of the deprecation warning, or b) simply identify the first version that a particular API call made it into Rails (for the Java folk among you, this may sound something like the @since directive in Javadoc). Or is it guaranteed that deprecation warnings go into Rails on the same version as new features (in which case, we can just assume that all of the changes must occur simultaneously with a Rails version update). Thanks, Wes
on 2007-03-20 07:15
on 2007-03-20 07:26
Is this: http://www.rubyonrails.org/deprecation going to be updated with all of the deprecation information at some point? All of the warnings point here, and most of the warnings are not mentioned or explained on this page. Wes
on 2007-03-20 07:46
Is there a comprehensive resource for all of the deprecations anywhere?
on 2009-02-19 18:15
Wes Gamble wrote: > Is there a comprehensive resource for all of the deprecations anywhere? I'd like to ask the same question. Well actually, I don't think I need a comprehensive resource. I'm failing just to find a list. http://www.rubyonrails.org/deprecation just results in a page not found. Google searching "Rails deprecation" doesn't seem to get me anywhere: just information on particular deprecations. I can get deprecations warnings regarding on code I have written - especially during the process of upgrading Rails. However, it would be nice to be able to keep track of what is about likely to be deprecated before coding where possible.
on 2009-02-19 19:07
Rob, Sadly, my impression is that the state of this world has not much improved since I wrote this post so long ago. I am resigned to doing upgrades on my Rails apps. more or less one point release at a time since there doesn't appear to be any more reliable way to get deprecation information. I've definitely seen cases where significant deprecations occurred in the framework between point releases and the only way I could find out about them was to dig into the Rails source itself. Sad, but true. There may be other resources out there, but I am ignorant of them if so. Anyone? Wes
on 2009-02-20 12:10
Wes Gamble wrote: > Sadly, my impression is that the state of this world has not much > improved since I wrote this post so long ago. Thanks for the reply Wes. I was prompted to ask the question on trying to find out why the use of the ActiveSupport::CoreExtensions::Float::Time method 'years' is being deprecated. Searching for deprecation and years gets too many hits, as 'years' is such a common real word. I thought it would be easier if I could look up a central repository of deprecation notices and this could be a useful place look up similar instances, but sadly it appears not.