I noticed some projects using Fog are setting very specific versioning constraint. For example, https://github.com/mitchellh/vagrant-rackspace/issues/34 happened because both vagrant-aws and vagrant-rackspace are using 3 digits of precision.
The fog RELEASE.md says that Fog follows semantic versioning. Several other projects have put up notices suggesting to use 2 digits of precision for projects that follow semver. See https://github.com/intridea/multi_json, for example.
I added a similar notice, but softened the language because I don't think there is a clear understanding on what semantic versioning means for a project like Fog, which has multiple providers backed by services that are all evolving at their own pace.
This reverts commit 1bdf61a389.
GFM only works on Gihub so the Yard documentation generated and
available on http://rubydoc.info/gems/fog will be unreadable.
* Mentions changes should support 1.8.7 and 1.9
* Suggests looking at code metrics for possible help
* Updates config file for testing (now `tests/.fog`)
* Updated on fog.io docs as well
I think the docs could be opened up a lot more so this is a first pass
at improvements.
[#1270]
Mark IJbema