Tiny fix to show that the code in github is for the next release. Associated with issue #60.
Updated .rvmrc file to create gemset.
See https://rvm.io/workflow/rvmrc/ for more info
Tiny change to README.
it wasn't clear that :with isn't a named option
Updated README to match style of rails docs.
Ensuring bundle is in RVM gemset
Updating version number to next release being worked on.
Crap, meant for this to not include the code from my other pull-request. Please just look at the last commit. It's such a nothing change that it could very easily be made manually without accepting the pull.
You can view the code for a specific version via the tagged releases. You can find them here and browse the code as of any release version: https://github.com/jkrall/analytical/tags
It's SOP in the Ruby community to bump gem versions immediately before a release. Personally I don't think it matters whether you do it immediately before or immediately after, but I do think it's best not to do it in the middle because it implies a release point when none exists.
Fair enough. I've generally incremented versions just after a release, but I see your point about incrementing in the middle of a dev cycle.