equal
deleted
inserted
replaced
165 <id>aa8bd952-842b-4391-aefe-d9b3750e432d</id> |
165 <id>aa8bd952-842b-4391-aefe-d9b3750e432d</id> |
166 <item> |
166 <item> |
167 <id>a8beddfc-11e3-4012-9f88-f79dc88eee16</id> |
167 <id>a8beddfc-11e3-4012-9f88-f79dc88eee16</id> |
168 <type>requirement</type> |
168 <type>requirement</type> |
169 <text>Semantic versioning is required.</text> |
169 <text>Semantic versioning is required.</text> |
170 <text>The version number consists of three numbers: major.minor.pach.</text> |
170 <text>The version number consists of three numbers: major.minor.patch.</text> |
171 <text>Major version is incremented if there is an incompatible change.</text> |
171 <text>Major version is incremented if there is an incompatible change.</text> |
172 <text>Minor version is incremented if a feature is added in a compatible way.</text> |
172 <text>Minor version is incremented if a feature is added in a compatible way.</text> |
173 <text>Patch version is incremented if a bug is fixed in a compatible way.</text> |
173 <text>Patch version is incremented if a bug is fixed in a compatible way.</text> |
174 <note>If authors are unable to distinguish between compatible and incompatible changes, they must always increment the major version. However this approach is not recommeded</note> |
174 <note>If authors are unable to distinguish between compatible and incompatible changes, they must always increment the major version. However this approach is not recommeded</note> |
175 <note>Propper Semantic versioning is especially important if the software is suposed to be used as dependency by others.</note> |
175 <note>Propper Semantic versioning is especially important if the software is suposed to be used as dependency by others.</note> |