On 09/03/12 18:05, Steve Klabnik wrote:
This is not backwards compatible. Therefore, a major version should be
increased when it changes.
I feel like this is going round in circles a bit, but...
Introducing backwards incompatible changes without an upgrade path is
not something that Rails currently does.
I guess you are saying that you think Rails should just do that, coupled
with adopting SemVer. Which is fair enough.
Personally I think this would lead to people become more, not less,
frustrated with the upgrade process though. Which would not be good, IMO.
Hence I was trying to explore alternatives.
--
http://jonathanleighton.com/
--
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.
