Make version format consistent

Elsewhere in this section we use `0.y.z`. In this place, we use `0.x.x`
This commit fixes that.

Closes #18
This commit is contained in:
Phil Haack
2012-12-19 17:08:45 -08:00
parent b40e67824e
commit 8606a7f8b9

View File

@@ -149,7 +149,7 @@ probably already be 1.0.0.
### Doesn't this discourage rapid development and fast iteration?
Major version zero is all about rapid development. If you're changing the API
every day you should either still be in version 0.x.x or on a separate
every day you should either still be in version 0.y.z or on a separate
development branch working on the next major version.
### If even the tiniest backwards incompatible changes to the public API require a major version bump, won't I end up at version 42.0.0 very rapidly?