README.markdown in acts_as_votable-0.8.0 vs README.markdown in acts_as_votable-0.9.0

@@ -11,16 +11,23 @@
   they can come from any model (such as a Group or Team).
 - Provide an easy to write/read syntax.
 
 ## Installation
 
-### Rails 3.0, 3.1, 3.2, and 4.0+
+### Supported Ruby and Rails versions
 
+* Ruby 1.8.7, 1.9.2, 1.9.3
+* Ruby 2.0.0, 2.1.0
+* Rails 3.0, 3.1, 3.2
+* Rails 4.0, 4.1+
+
+### Install
+
 Just add the following to your Gemfile.
 
 ```ruby
-gem 'acts_as_votable', '~> 0.7.1'
+gem 'acts_as_votable', '~> 0.9.0'
 ```
 
 And follow that up with a ``bundle install``.
 
 ### Database Migrations
@@ -46,24 +53,24 @@
 
 @post = Post.new(:name => 'my post!')
 @post.save
 
 @post.liked_by @user
[e-mail] # => 1
[e-mail]_for.size # => 1
 ```
 
 ### Like/Dislike Yes/No Up/Down
 
 Here are some voting examples.  All of these calls are valid and acceptable.  The
 more natural calls are the first few examples.
 
 ```ruby
 @post.liked_by @user1
 @post.downvote_from @user2
[e-mail] :voter => @user3
[e-mail] :voter => @user4, :vote => 'bad'
[e-mail] :voter => @user5, :vote => 'like'
[e-mail]_by :voter => @user3
[e-mail]_by :voter => @user4, :vote => 'bad'
[e-mail]_by :voter => @user5, :vote => 'like'
 ```
 
 By default all votes are positive, so `@user3` has cast a 'good' vote for `@post`.
 
 `@user1`, `@user3`, and `@user5` all voted in favor of `@post`.
@@ -78,41 +85,41 @@
 Revisiting the previous example of code.
 
 ```ruby
 # positive votes
 @post.liked_by @user1
[e-mail] :voter => @user3
[e-mail] :voter => @user5, :vote => 'like'
[e-mail]_by :voter => @user3
[e-mail]_by :voter => @user5, :vote => 'like'
 
 # negative votes
 @post.downvote_from @user2
[e-mail] :voter => @user2, :vote => 'bad'
[e-mail]_by :voter => @user2, :vote => 'bad'
 
 # tally them up!
[e-mail] # => 5
[e-mail] # => 3
[e-mail] # => 3
[e-mail] # => 2
[e-mail] # => 2
[e-mail]_for.size # => 5
[e-mail]_likes.size # => 3
[e-mail]_upvotes.size # => 3
[e-mail]_dislikes.size # => 2
[e-mail]_downvotes.size # => 2
 ```
 
 Active Record scopes are provided to make life easier.
 
 ```ruby
[e-mail]_type(User)
[e-mail]
[e-mail]_for.up.by_type(User)
[e-mail]_for.down
 @user1.votes.up
 @user1.votes.down
 @user1.votes.up.by_type(Post)
 ```
 
 Once scoping is complete, you can also trigger a get for the
 voter/votable
 
 ```ruby
[e-mail]_type(User).voters
[e-mail]_type(User).voters
[e-mail]_for.up.by_type(User).voters
[e-mail]_for.down.by_type(User).voters
 
 @user.votes.up.for_type(Post).votables
 @user.votes.up.votables
 ```
 
@@ -133,53 +140,53 @@
 You can add an scope to your vote
 
 ```ruby
 # positive votes
 @post.liked_by @user1, :vote_scope => 'rank'
[e-mail] :voter => @user3, :vote_scope => 'rank'
[e-mail] :voter => @user5, :vote => 'like', :vote_scope => 'rank'
[e-mail]_by :voter => @user3, :vote_scope => 'rank'
[e-mail]_by :voter => @user5, :vote => 'like', :vote_scope => 'rank'
 
 # negative votes
 @post.downvote_from @user2, :vote_scope => 'rank'
[e-mail] :voter => @user2, :vote => 'bad', :vote_scope => 'rank'
[e-mail]_by :voter => @user2, :vote => 'bad', :vote_scope => 'rank'
 
 # tally them up!
[e-mail]_votes(:vote_scope => 'rank').size # => 5
[e-mail](:vote_scope => 'rank').size # => 3
[e-mail](:vote_scope => 'rank').size # => 3
[e-mail](:vote_scope => 'rank').size # => 2
[e-mail](:vote_scope => 'rank').size # => 2
[e-mail]_votes_for(:vote_scope => 'rank').size # => 5
[e-mail]_likes(:vote_scope => 'rank').size # => 3
[e-mail]_upvotes(:vote_scope => 'rank').size # => 3
[e-mail]_dislikes(:vote_scope => 'rank').size # => 2
[e-mail]_downvotes(:vote_scope => 'rank').size # => 2
 
 # votable model can be voted under different scopes
 # by the same user
[e-mail] :voter => @user1, :vote_scope => 'week'
[e-mail] :voter => @user1, :vote_scope => 'month'
[e-mail]_by :voter => @user1, :vote_scope => 'week'
[e-mail]_by :voter => @user1, :vote_scope => 'month'
 
[e-mail] # => 2
[e-mail]_votes(:vote_scope => 'week').size # => 1
[e-mail]_votes(:vote_scope => 'month').size # => 1
[e-mail]_for.size # => 2
[e-mail]_votes_for(:vote_scope => 'week').size # => 1
[e-mail]_votes_for(:vote_scope => 'month').size # => 1
 ```
 ### Adding weights to your votes
 
 You can add weight to your vote. The default value is 1.
 
 ```ruby
 # positive votes
 @post.liked_by @user1, :vote_weight => 1
[e-mail] :voter => @user3, :vote_weight => 2
[e-mail] :voter => @user5, :vote => 'like', :vote_scope => 'rank', :vote_weight => 3
[e-mail]_by :voter => @user3, :vote_weight => 2
[e-mail]_by :voter => @user5, :vote => 'like', :vote_scope => 'rank', :vote_weight => 3
 
 # negative votes
 @post.downvote_from @user2, :vote_scope => 'rank', :vote_weight => 1
[e-mail] :voter => @user2, :vote => 'bad', :vote_scope => 'rank', :vote_weight => 3
[e-mail]_by :voter => @user2, :vote => 'bad', :vote_scope => 'rank', :vote_weight => 3
 
 # tally them up!
[e-mail]_votes(:vote_scope => 'rank').sum(:vote_weight) # => 6
[e-mail](:vote_scope => 'rank').sum(:vote_weight) # => 6
[e-mail](:vote_scope => 'rank').sum(:vote_weight) # => 6
[e-mail](:vote_scope => 'rank').sum(:vote_weight) # => 4
[e-mail](:vote_scope => 'rank').sum(:vote_weight) # => 4
[e-mail]_votes_for(:vote_scope => 'rank').sum(:vote_weight) # => 6
[e-mail]_likes(:vote_scope => 'rank').sum(:vote_weight) # => 6
[e-mail]_upvotes(:vote_scope => 'rank').sum(:vote_weight) # => 6
[e-mail]_dislikes(:vote_scope => 'rank').sum(:vote_weight) # => 4
[e-mail]_downvotes(:vote_scope => 'rank').sum(:vote_weight) # => 4
 ```
 
 ### The Voter
 
 You can have your voters `acts_as_voter` to provide some reserve functionality.
@@ -290,11 +297,11 @@
 
 To permit duplicates entries of a same voter, use option duplicate. Also notice that this
 will limit some other methods that didn't deal with multiples votes, in this case, the last vote will be considered.
 
 ```ruby
[e-mail] voter: @user, :duplicate => true
[e-mail]_by voter: @user, :duplicate => true
 ```
 
 ## Caching
 
 To speed up perform you can add cache columns to your votable model's table.  These
@@ -336,10 +343,27 @@
 
 ```
 rake spec
 ```
 
+## Changes  
+
+### Fixes for votable voter model  
+
+In version 0.8.0, there is bugs for a model that is both votable and voter.  
+Some name-conflicting methods are renamed:
++ Renamed Votable.votes to votes_for  
++ Renamed Votable.vote to vote_by,
++ Removed Votable.vote_by alias (was an alias for :vote_up)
++ Renamed Votable.unvote_for to unvote_by
++ Renamed Votable.find_votes to find_votes_for
++ Renamed Votable.up_votes to get_upvotes 
+  + and its aliases :get_true_votes, :get_ups, :get_upvotes, :get_likes, :get_positives, :get_for_votes
++ Renamed Votable.down_votes to get_downvotes 
+  + and its aliases :get_false_votes, :get_downs, :get_downvotes, :get_dislikes, :get_negatives
+
+
 ## License
 
 Acts as votable is released under the [MIT
 License](http://www.opensource.org/licenses/MIT).
 
@@ -350,10 +374,9 @@
 
 - Smarter language syntax.  Example: `@user.likes` will return all of the votables
 that the user likes, while `@user.likes @model` will cast a vote for @model by
 @user.
 
-- Need to test a model that is votable as well as a voter
 
 - The aliased methods are referred to by using the terms 'up/down' and/or
 'true/false'.  Need to come up with guidelines for naming these methods.
 
 - Create more aliases. Specifically for counting votes and finding votes.