# Identifying Rails versions related to deprecation warnings **URL:** \ **Category:** Rails\ **Created:** [March 20, 2007, 7:15am UTC](https://www.ruby-forum.com/t/identifying-rails-versions-related-to-deprecation-warnings/89405 "2007-03-20T07:15:52Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![weyus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/7ab992/32.png) [@weyus](https://www.ruby-forum.com/u/weyus)\ **Post date:** [March 20, 2007, 7:15am UTC](https://www.ruby-forum.com/t/identifying-rails-versions-related-to-deprecation-warnings/89405/1 "2007-03-20T07:15:52Z")
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 ---
**Author:** ![weyus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/7ab992/32.png) [@weyus](https://www.ruby-forum.com/u/weyus)\ **Post date:** [March 20, 2007, 7:26am UTC](https://www.ruby-forum.com/t/identifying-rails-versions-related-to-deprecation-warnings/89405/2 "2007-03-20T07:26:52Z")
Is this: > **[Ruby on Rails](https://rubyonrails.org)** > > A web-app framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern. 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 ---
**Author:** ![weyus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/7ab992/32.png) [@weyus](https://www.ruby-forum.com/u/weyus)\ **Post date:** [March 20, 2007, 7:46am UTC](https://www.ruby-forum.com/t/identifying-rails-versions-related-to-deprecation-warnings/89405/3 "2007-03-20T07:46:12Z")
Is there a comprehensive resource for all of the deprecations anywhere? ---
**Author:** ![weyus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/7ab992/32.png) [@weyus](https://www.ruby-forum.com/u/weyus)\ **Post date:** [February 19, 2009, 7:07pm UTC](https://www.ruby-forum.com/t/identifying-rails-versions-related-to-deprecation-warnings/89405/4 "2009-02-19T19:07:48Z")
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 ---
**Author:** ![weyus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/7ab992/32.png) [@weyus](https://www.ruby-forum.com/u/weyus)\ **Post date:** [February 20, 2009, 12:10pm UTC](https://www.ruby-forum.com/t/identifying-rails-versions-related-to-deprecation-warnings/89405/5 "2009-02-20T12:10:19Z")
Wes G. 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. ---
**Author:** ![weyus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/7ab992/32.png) [@weyus](https://www.ruby-forum.com/u/weyus)\ **Post date:** [February 19, 2009, 6:15pm UTC](https://www.ruby-forum.com/t/identifying-rails-versions-related-to-deprecation-warnings/89405/6 "2009-02-19T18:15:07Z")
Wes G. 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. [Ruby on Rails — A web-app framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.](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.