mirror of
https://github.com/semver/semver.git
synced 2025-08-22 13:58:33 +00:00
Update: Provide more clarity about the term ANY time for initial development releases
## Description The text `Anything MAY change at any time` can lead the idea that no rules are required and that PATCH releases can also introduces breaking changes or new functionalities when I understand that the whole idea here is clarifies that no compatible changes will be addressed in MINOR releases since the project has no MAJOR bumps at all. So, could we please try to clarifies this one?
This commit is contained in:
parent
a4f21e1a6f
commit
4a00a820c8
@ -68,7 +68,9 @@ Each element MUST increase numerically. For instance: 1.9.0 -> 1.10.0 -> 1.11.0.
|
||||
MUST NOT be modified. Any modifications MUST be released as a new version.
|
||||
|
||||
1. Major version zero (0.y.z) is for initial development. Anything MAY change
|
||||
at any time. The public API SHOULD NOT be considered stable.
|
||||
at any time. The public API SHOULD NOT be considered stable. Incompatible API changes and
|
||||
new functionality might be introcuded in MINOR releases. PATCH releases still reserved
|
||||
to backwards compatible bug fixes.
|
||||
|
||||
1. 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
|
||||
|
Loading…
Reference in New Issue
Block a user