public-mirrors
/
composer
mirror of https://github.com/composer/composer
1
0
Fork 0
Code

Describe tag names more consistently, fixes #2170

pull/2175/head
Jordi Boggiano 2013-08-13 14:46:43 +02:00
parent 051d219438
commit eb331cbcbe
2 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/02-libraries.md
View File

@ -69,8 +69,9 @@ you can just add a `version` field:
### Tags ### Tags
For every tag that looks like a version, a package version of that tag will be For every tag that looks like a version, a package version of that tag will be
created. It should match 'X.Y.Z' or 'vX.Y.Z', with an optional suffix for RC, created. It should match 'X.Y.Z' or 'vX.Y.Z', with an optional suffix
beta, alpha or patch. of `-dev`, `-patch`, `-alpha`, `-beta` or `-RC`. The patch, alpha, beta and
RC suffixes can also be followed by a number.
Here are a few examples of valid tag names: Here are a few examples of valid tag names:

8
doc/04-schema.md
View File

@ -50,10 +50,12 @@ Required for published packages (libraries).
### version ### version
The version of the package. The version of the package. In most cases this is not required and should
be omitted (see below).
This must follow the format of `X.Y.Z` with an optional suffix of `-dev`, This must follow the format of `X.Y.Z` or `vX.Y.Z` with an optional suffix
`-alphaN`, `-betaN` or `-RCN`. of `-dev`, `-patch`, `-alpha`, `-beta` or `-RC`. The patch, alpha, beta and
RC suffixes can also be followed by a number.
Examples: Examples: