guard/guard — Issue #222: Version Bump (0.10.0 -> 1.0.0)
Author: krainboltgreene
Created: 2012-01-09 03:11:47+00:00
State: open

Right now Guard is currently at version `0.10.0`. I assume based on the notation that Guard is using [Semantic Versioning](http://semver.org/) which is great! With that said I'd like to point out a few things from Semantic Versioning:

> 5\. Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.

> 6\. Version 1.0.0 defines the public API. The way in which the version number is incremented after this release is dependent on this public API and how it changes.

And finally:

> ## How do I know when to release 1.0.0?
>
> If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you're worrying a lot about backwards compatibility, you should probably already be 1.0.0.

Currently there are **89** guard gems, based on the `guard-` prefix naming convention, on Rubygems. If any public API changed in guard at this point all of them would likely break. Considering the amount of libraries depending on Guard's current public API, the number of forks, watchers, and downloads per day along with the statistic that [18% of surveyed Gemfile's have guard-rspec](https://twitter.com/#!/GemStats/status/120909697460088833) I believe I have a strong case for bumping up Guard's version number to 1.0.0.

Thoughts?