On Saturday, August 4, 2012 9:41:54 PM UTC+9:30, Jon Leighton wrote: > On 04/08/12 12:48, Alexey wrote: > > > > > > On Friday, August 3, 2012 4:29:57 PM UTC+2, Santiago Pastorino wrote: > > > > > > We are removing all the deprecation warnings that we introduced in > > > 3.2.x. > > > We have decided to stop introducing API deprecations in all point > > > releases going forward. From now on, it'll only happen in > > > majors/minors. > > > > > > > > > Does this mean that all deprecation warnings will appear in releases > > > X.Y.0 and disappear in X.Y.1 ? I like this idea. > > > > No. New deprecation warnings will only be added in X.Y.0, but the > > deprecated feature itself will not be removed until X.Z.0. > > > > -- > > http://jonathanleighton.com/
I know I might be being a bit pedantic, but is Z > Y? is Z = Y+1? I read it as: There may be deprecation warnings added in X.Y.0 which will stay 'frozen' until X.Y+1.0 , so any X.Y.a release will not have deprecation warnings added (a!=0). Although I'm not sure if they will get removed in version X.Y+1.0 or some X.Y+N.0 release. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/PC-Tefs8rr4J. 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.
