openstack
/
pbr
Code Issues Proposed changes

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
This commit is contained in:
Robert Collins 2014-03-17 10:12:46 +13:00
parent adb0d20ec7
commit e01b28e4c3
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/semver.rst
View File

@ -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