Browse code
fix the bare url and the Summary of http://semver.org
Signed-off-by: yupengzte <yupeng36@zte.com.cn>
yupengzte authored on 2017/01/17 17:15:51Showing 1 changed files
| ... | ... |
@@ -26,13 +26,14 @@ dependency on a package of a specific version or greater up to the next major |
| 26 | 26 |
release, without encountering breaking changes. |
| 27 | 27 |
|
| 28 | 28 |
## Semantic Versioning |
| 29 |
-Annotated version tags should follow Schema Versioning policies. |
|
| 30 |
-According to http://semver.org: |
|
| 29 |
+Annotated version tags should follow [Semantic Versioning](http://semver.org) policies: |
|
| 31 | 30 |
|
| 32 | 31 |
"Given a version number MAJOR.MINOR.PATCH, increment the: |
| 33 |
- MAJOR version when you make incompatible API changes, |
|
| 34 |
- MINOR version when you add functionality in a backwards-compatible manner, and |
|
| 35 |
- PATCH version when you make backwards-compatible bug fixes. |
|
| 32 |
+ |
|
| 33 |
+ 1. MAJOR version when you make incompatible API changes, |
|
| 34 |
+ 2. MINOR version when you add functionality in a backwards-compatible manner, and |
|
| 35 |
+ 3. PATCH version when you make backwards-compatible bug fixes. |
|
| 36 |
+ |
|
| 36 | 37 |
Additional labels for pre-release and build metadata are available as extensions |
| 37 | 38 |
to the MAJOR.MINOR.PATCH format." |
| 38 | 39 |
|