On Nov 12, 2007, at 7:53 PM, Michael Koziarski wrote:
> I can't help with a specific definition or a URL to point you at, but > in practice code which used documented apis on 1.2.x should work on > 1.2.y for all y > x. It's intended to be a drop in replacement, and > when we introduce regressions we tend to fix them with a follow up > release. > > The choice between calling something 1.5 or 2.0 is a little more > vague, but basically don't expect a drop in upgrade if the major > number changes. The most important thing is to pay attention to the > deprecation warnings you receive, the next major release will have > that code removed. fair enough - that's enough info to know which upgrades are ok to do on a friday night and which are not ;-) thx a @ http://codeforpeople.com/ -- we can deny everything, except that we have the possibility of being better. simply reflect on that. h.h. the 14th dalai lama --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
