Merge branch 'release-1.0.1' into develop
Bumped version to v1.1.0-1

This is in preparation for modifications to vmlib based on SemVer
v2.0.0-rc.2. The primary changes to this version are to fix ordering
to ignore build metadata unless explicitly specified.
Add a gem_version function

bundler/gem_tasks complains when having prerelease or build identifiers
in the version string. As a result, I've added a gem_version function
that simply captures the major, minor and patch releases while ignoring
the rest. Since this file is (mostly) updated by the vmlib gem update
function, and the gem_version function is only acting on the constant
VERSION at build time, there's no need for any error checking
functionality.
Split update and commit steps

This creates two separate commands - one update step which simply
modifies the source files with the new version, and an additional commit
step which will commit all modified files to the repository. This is
done in order to acheive continuous integration builds and nightly
builds without having to create a new commit everytime.

Also, the update step takes an optional format argument so the user can
specify the version format to be saved in the source files. This is
useful in cases where the build framework expects the version string to
be in a certain format.
Add test case for build information

This needs to be expanded and verified.
Expand basic test cases for build metadata
Add bump test cases
Change references to SemVer v2.0.0
Fix build metadata comparision per SemVer v2.0.0

SemVer 2.0.0 recommends ignoring build metadata for comparision. This is
now the default behaviour for vmlib. However, it is possible to enable
comparing the build metadata as well by setting the compare_build
attribute to true.
Add comparision test cases
Add format test cases
Add testcases for build metadata set and compare

This should identify testcases that exhibit the bug behaviour as
described in issue #2.
Add additional test cases for format
First commit to move instance attributes to class

This mainly addresses the compare_build attribute, so you can set it at
the class level in your application and decide at one level whether to
use the comparator or not.

Similarly, this adds a new enable_prerelease_parser to decide whether to
use the prerelease parser in your application or disable it to use your
own custom strings. Support for these class attributes is not yet in
place, since this is only an initial commit.

Right now, you can selectively enable or disable the compare_build
option, but it's at an instance level rather than at the class level.
Update class attributes to use build comparator

The code now uses a class level attribute to enable or disable the build
comparator. Consistent with SemVer 2.0.0, this is disabled by default
and must be enabled if the user wishes it.

Build comparisions are to be made lexically, if enabled.
Treat build identifiers as strings - fixes #2
Fix warning in bump code
Add ruby-version file

This indicates the minimum supported ruby version for ruby managers like
rvm, rbenv, rbfu, etc.
Add code to control prerelease parser

If the user elects to disable the prerelease parser by means of setting
the corresponding class variable, then although the parser will run, the
reltype setting will be overwritten with reltype custom and therefore,
it will not clear the array.
Add parser test cases and fix test failures