equal
deleted
inserted
replaced
35 --> |
35 --> |
36 </ul> |
36 </ul> |
37 |
37 |
38 <h2>Semantic versioning</h2> |
38 <h2>Semantic versioning</h2> |
39 <ul> |
39 <ul> |
40 <li>strongly recommended</li> |
40 <li><a href="http://semver.org/">Semantic versioning</a> is strongly recommended.</li> |
41 <li>required when the package is suposed to be used as dependency by others</li> |
41 <li>Especially when the software is suposed to be used as dependency by others.</li> |
42 <li>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</li> |
42 <li>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.</li> |
43 <li>once publicly released, the package must not be changed anymore – if a change (even small fix) is needed, new version number must be assigned</li> |
43 <li>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.</li> |
44 <li> |
44 <li> |
45 APIs, file formats and protocols might be semanticly versioned independently from the implementation; |
45 APIs, file formats and protocols might be semanticly versioned independently from the implementation; |
46 in such case, there should be a table documenting which API/format/protocol version matches which implementation version |
46 in such case, there should be a table documenting which API/format/protocol version matches which implementation version. |
47 </li> |
47 </li> |
48 </ul> |
48 </ul> |
49 |
49 |
50 <h2>Compatibilible with itself</h2> |
50 <h2>Compatibilible with itself</h2> |
51 <ul> |
51 <ul> |