Skip to content

Commit

Permalink
Updated README.
Browse files Browse the repository at this point in the history
  • Loading branch information
Gerjan Stokkink committed May 4, 2012
1 parent 0a0d6b2 commit d675199
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions README.rdoc
View file
Expand Up @@ -238,6 +238,9 @@ 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 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
- Version 1.2.5 (2012-03-15)
- Fixed warnings: "parenthesize argument(s) for future version"
- Fixed a bug in the restore_ancestry_integrity! method (thx Arthur Holstvoogd)
Expand Down

1 comment on commit d675199

@dmitry
Copy link

@dmitry dmitry commented on d675199 May 14, 2012

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to update next version, like 1.4 to support Rails 3.2 without backward compatibility? In my fork there are a lot of fixes that I've cherry-picked from other sources.

Please sign in to comment.