diff -r 60e67a0c8b61 -r bd140638915f ssm-en.xhtml
--- a/ssm-en.xhtml Wed Aug 24 00:05:10 2016 +0200
+++ b/ssm-en.xhtml Wed Aug 24 00:11:41 2016 +0200
@@ -37,13 +37,13 @@
Semantic versioning
- - strongly recommended
- - required when the package is suposed to be used as dependency by others
- - if there is need of some marketing or cool versioning/codenames like Ultrasonic Umbrella or 2016, they should be used in addition to semantic versioning, not instead it
- - once publicly released, the package must not be changed anymore – if a change (even small fix) is needed, new version number must be assigned
+ - Semantic versioning is strongly recommended.
+ - Especially when the software is suposed to be used as dependency by others.
+ - If there is a need of some marketing or cool versioning/codenames like Ultrasonic Umbrella or 2016, they should be used in addition to semantic versioning, not instead of it.
+ - Once publicly released, the package must not be changed anymore – if a change (even a small fix) is needed, new version number must be assigned.
-
APIs, file formats and protocols might be semanticly versioned independently from the implementation;
- in such case, there should be a table documenting which API/format/protocol version matches which implementation version
+ in such case, there should be a table documenting which API/format/protocol version matches which implementation version.