ancestry 2.0.0.rc1 → 2.0.0

data/README.rdoc

@@ -249,11 +249,17 @@ The materialised path pattern requires Ancestry to use a 'like' condition in ord
 
 The latest version of ancestry is recommended. The three numbers of each version numbers are respectively the major, minor and patch versions. We started with major version 1 because it looks so much better and ancestry was already quite mature and complete when it was published. The major version is only bumped when backwards compatibility is broken. The minor version is bumped when new features are added. The patch version is bumped when bugs are fixed.
 
-- Version 2.0.0.rc1 (2013-05-07)
+- Version 2.0.0 (2013-05-17)
   - Removed rails 2 compatibility
-  - Fixed deprecation warnings for rails 4
-  - New adopt strategy
-  - Many more fixes & minor changes
+  - Added table name to condition constructing methods (thx aflatter)
+  - Fix depth_cache not being updated when moving up to ancestors (thx scottatron)
+  - add alias :root? to existing is_root? (thx divineforest)
+  - Add block to sort_by_ancestry (thx Iliya)
+  - Add attribute query method for parent_id (thx sj26)
+  - Fixed and tested for rails 4 (thx adammck, Nihad, Systho, Philippe, e.a.)
+  - Fixed overwriting ActiveRecord::Base.base_class (thx Rozhnov)
+  - New adopt strategy (thx unknown)
+  - Many more improvements
 - Version 1.3.0 (2012-05-04)
   - Ancestry now ignores default scopes when moving or destroying nodes, ensuring tree consistency
   - Changed ActiveRecord dependency to 2.3.14

data/ancestry.gemspec

@@ -3,7 +3,7 @@ Gem::Specification.new do |s|
   s.description = 'Organise ActiveRecord model into a tree structure'
   s.summary     = 'Ancestry allows the records of a ActiveRecord model to be organised in a tree structure, using a single, intuitively formatted database column. It exposes all the standard tree structure relations (ancestors, parent, root, children, siblings, descendants) and all of them can be fetched in a single sql query. Additional features are named_scopes, integrity checking, integrity restoration, arrangement of (sub)tree into hashes and different strategies for dealing with orphaned records.'
 
-  s.version = '2.0.0.rc1'
+  s.version = '2.0.0'
 
   s.author   = 'Stefan Kroes'
   s.email    = 's.a.kroes@gmail.com'

metadata

@@ -1,15 +1,15 @@
 --- !ruby/object:Gem::Specification
 name: ancestry
 version: !ruby/object:Gem::Version
-  version: 2.0.0.rc1
-  prerelease: 6
+  version: 2.0.0
+  prerelease: 
 platform: ruby
 authors:
 - Stefan Kroes
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-05-07 00:00:00.000000000 Z
+date: 2013-05-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activerecord
@@ -58,9 +58,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
-  - - ! '>'
+  - - ! '>='
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.25