History - Versionomy 0.5.0 Documentation

The gemspec no longer includes the timestamp in the version, so that bundler can pull from github. (Reported by corneverbruggen)
Updated the Rakefile, tests, and general infrastructure to play better with modern Rubies.
Dropped support for Ruby 1.8, because who still uses 1.8???

Included Semantic Version (semver.org/) format called “semver”.
Parsing conversions can now prescreen or premodify the original format value.
Conversion algorithm tries to convert through the standard format if a direct conversion isn't found. For example, there is currently no direct conversion between semver and rubygems formats, but the converter can nevertheless convert the two because both can convert to and from standard.
Expanded the module version detection to include VERSION submodules.
Some Rakefile fixes to match RDoc and Ruby 1.9 changes.

Alpha release, opened for public feedback
Autoloading of format definitions using a load path.
Format and conversion registry/lookup is now thread-safe.
Implemented resetting a particular field in the value.
Implemented aliases for field names.
Changed the canonical YAML tag to its permanent value. The old one will continue to be recognized, but only the permanent one will be written from now on.
Documentation updates

Preserve minimum width of a field, if the field has leading zeros. For example, “2.01”.

Fixed a regression introduced in 0.2.2 where “1.0a” was being recognized as an alpha version rather than a patchlevel of 1, and similar for “1.0b” and “1.0d”.

Recognize “_” and “u” as patchlevel delimiters, to support Sun's Java version numbers (e.g. “1.6.0_17”, “6u17”).
Recognize “v” prefix found on some version numbers (e.g. “v1.2”)

Standard format now supports certain kinds of prereleases without a prerelease number. e.g. “1.9.2dev” is interpreted as the same number as “1.9.2dev0”.
Added Versionomy#ruby_version.
A field can specify a default_value for parsing, distinct from the one specified by the schema.
A field can specify requires_next_field to control whether the following field is required or optional.

Added Versionomy#version_of.
Now lets Blockenspiel set its own VERSION instead of reaching into Blockenspiel's namespace.

API CHANGE: Slight change to value comparison semantics. Value#eql? returns true only if the schemas are the same, whereas Value#== and the greater than and less than comparisons attempt to compare the semantic value, and thus may perform automatic schema conversion on the RHS.
API CHANGE: Merged Formats namespace into Format. Versionomy::Formats is now a (deprecated) alias for Versionomy::Format.
API CHANGE: The delimiter parsing algorithm now defaults :extra_characters to :error instead of :ignore.
Added a mechanism for converting from one format/schema to another.
Added Rubygems format, along with conversions to and from the standard format.
Values now include Comparable.
Values can now be serialized using Marshal and YAML.
Schemas can now add custom methods to value objects. Added “prerelease?” and “release” methods to rubygems and standard format values.
Added default field settings to schema DSL.
Implemented === for schemas and formats.
Many minor bug fixes and documentation updates.

Fixed an issue with parsing the “-p” patchlevel delimiter, e.g. “1.9.1-p243”. (Reported by Luis Lavena.)

General rearchitecture. Better distinction between format and schema. Schema split into schema and field objects so the API makes more sense. Values are tighter and easier to use. Formats can now be built using a DSL. A bunch of API changes and bug fixes accompanied this– too many to list.
In the standard schema, renamed release type “release” to “final”. Also renamed release type “prerelease” to “preview”, now sorted between “release candidate” and “final”.
Documentation is much more complete.
Now tested and confirmed compatible with Matz Ruby 1.9.1 and JRuby 1.4.
Now uses blockenspiel 0.2; thus longer requires the mixology gem.
Building no longer requires hoe.