In my opinion, the Rails version number should reflect the changes to
the Rails API. The user-facing API did not see major changes due to
the ARel rewrite.

As the author of two gems (MetaWhere and MetaSearch) that are heavily
dependent on ARel for their functionality, I released updated gems an
hour after 3.0.2 released, having been tracking the changes since
Aaron started the rewrite.

I didn't find the changes to be too troublesome to track, and the
payoff was certainly worthwhile. Where I encountered missing or
changed functionality I submitted patches to ARel to reduce/limit
breakage. See  
http://metautonomo.us/2010/10/15/converting-your-code-to-arel-2-0/
for a writeup about some of the stuff I encountered, if you're
curious. Aaron has been great about merging pull requests in a timely
manner, in my opinion.

I think anyone who maintains code that integrates with a lower-level
API like ARel owes it to themselves to track major version changes in
those dependencies, not just Rails.

On Nov 15, 2010, at 5:19 PM, Ken Collins <k...@metaskills.net> wrote:

>
> All,
>
> I really do think the latest 3.0.2 version was poorly chosen.
>
> A "major" version of 1.x to 2.x of Arel should have at least affected the 
> "minor" version of rails/activerecord, not "tiny". As an author of an 
> external adapter, I set my gemspec expecting such to give me time to account 
> for the rewrite. A version change of 3.0.1 to 3.0.2 should not break my code. 
> Thoughts about this for future versioning?
>
>
> - Thanks,
>    Ken
>
>
> --
> 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 rubyonrails-c...@googlegroups.com.
> To unsubscribe from this group, send email to 
> rubyonrails-core+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/rubyonrails-core?hl=en.
>

-- 
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 rubyonrails-c...@googlegroups.com.
To unsubscribe from this group, send email to 
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core?hl=en.

Reply via email to