From f02976c5ea094316ac3f987519b33e2fc2d001a0 Mon Sep 17 00:00:00 2001 From: Allan Bogh Date: Fri, 17 Jan 2020 00:13:02 -0800 Subject: [PATCH] Update semver.md Clarified points 4 and 5. --- semver.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/semver.md b/semver.md index be210b3..5802a5d 100644 --- a/semver.md +++ b/semver.md @@ -68,12 +68,13 @@ Each element MUST increase numerically. For instance: 1.9.0 -> 1.10.0 -> 1.11.0. 1. Once a versioned package has been released, the contents of that version 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. +1. Major version zero (0.y.z) is for initial development. Anything MAY change +at any time. It is not recommended for the public to use 0.y.z version numbers. +The project should release a 1.0.0 version when it is ready for the public to use. -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 -changes. +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 +changes as defined in the PATCH, MINOR, and MAJOR sections. 1. Patch version Z (x.y.Z | x > 0) MUST be incremented if only backwards compatible bug fixes are introduced. A bug fix is defined as an internal