|
|
От: | Sinix | |
| Дата: | 19.08.15 07:07 | ||
| Оценка: | +1 | ||
4.Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.
5.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.
...
FAQ
>How should I deal with revisions in the 0.y.z initial development phase?
The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.
>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.
определение "ломающим изменениям" даёт сам автор. Собственно, вся суть semver — уложить в три цифры публичный контракт софта. Грубо говоря,Given a version number MAJOR.MINOR.PATCH, increment the:
1.MAJOR version when you make incompatible API changes,
2.MINOR version when you add functionality in a backwards-compatible manner, and
3.PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.