From e01b28e4c36d2505555bfd969fa225715c20dbbb Mon Sep 17 00:00:00 2001 From: Robert Collins Date: Mon, 17 Mar 2014 10:12:46 +1300 Subject: Permit pre-release versions with git metadata This is implied by the example and seems necessary for doing automated generation of pre-release versions. Change-Id: I8d4ceec200fac7982f2dafa7f8f1a8abfd4b0f83 --- doc/source/semver.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/semver.rst b/doc/source/semver.rst index b22242d..9d287fb 100644 --- a/doc/source/semver.rst +++ b/doc/source/semver.rst @@ -131,7 +131,7 @@ document are to be interpreted as described in `RFC communication of not-yet-released ideas. Example: 1.0.0.dev1. #. git version metadata MAY be denoted by appending a dot separated - identifier immediately following a development version. + identifier immediately following a development or pre-release version. The identifier MUST comprise the character g followed by a seven character git short-sha. The sha MUST NOT be empty. git version metadata MUST be ignored when determining version precedence. Thus -- cgit v1.2.1