text/ssm.en.xml
branchv_0
changeset 40 bc2043705ec5
parent 38 8d0d0afb75f3
child 41 5ccfbf077da4
equal deleted inserted replaced
39:07858e00622b 40:bc2043705ec5
    57 			<!-- TODO: provide exact wording of the exception e.g. XYZ is „Sane software (with GPLv2 license exception)“ -->
    57 			<!-- TODO: provide exact wording of the exception e.g. XYZ is „Sane software (with GPLv2 license exception)“ -->
    58 			<note>Software versioned under GPLv2+ or GPLv3+ is compatible with GPLv3.</note>
    58 			<note>Software versioned under GPLv2+ or GPLv3+ is compatible with GPLv3.</note>
    59 		</item>
    59 		</item>
    60 		<item>
    60 		<item>
    61 			<id>f39b90ae-0054-467e-a9e2-43379b7c2331</id>
    61 			<id>f39b90ae-0054-467e-a9e2-43379b7c2331</id>
    62 			<text>If the software is distributed with a hardware, the hardware must support instalation of independently built software without any restrictions or requirements (e.g. digital signature from the original author).</text>
    62 			<text>If the software is distributed with a hardware, the hardware must support installation of independently built software without any restrictions or requirements (e.g. digital signature from the original author).</text>
    63 		</item>
    63 		</item>
    64 	</chapter>
    64 	</chapter>
    65 	
    65 	
    66 	<chapter>
    66 	<chapter>
    67 		<name>Documented</name>
    67 		<name>Documented</name>
   111 			<id>cf557a11-b307-4c2f-a7b5-5d2485d23258</id>
   111 			<id>cf557a11-b307-4c2f-a7b5-5d2485d23258</id>
   112 			<text>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.</text>
   112 			<text>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.</text>
   113 		</item>
   113 		</item>
   114 		<item>
   114 		<item>
   115 			<id>dd013325-bf22-43d3-9579-0e272e2ac344</id>
   115 			<id>dd013325-bf22-43d3-9579-0e272e2ac344</id>
   116 			<text>APIs, file formats and protocols might (and usually should) be semanticly versioned independently from the implementation.</text>
   116 			<text>APIs, file formats and protocols might (and usually should) be semantically versioned independently from the implementation.</text>
   117 			<note>In such case, there should be a table documenting which API/format/protocol version matches which implementation version.</note>
   117 			<note>In such case, there should be a table documenting which API/format/protocol version matches which implementation version.</note>
   118 		</item>
   118 		</item>
   119 		<item>
   119 		<item>
   120 			<id>dacb98cc-b558-4f0e-942d-e12004e45606</id>
   120 			<id>dacb98cc-b558-4f0e-942d-e12004e45606</id>
   121 			<text>The branching model in the version control system should reflect the semantic versioning.</text>
   121 			<text>The branching model in the version control system should reflect the semantic versioning.</text>
   122 			<text>The released version e.g. 2.3.1 should be tagged as v2.3.1 and be placed in the v_2.3 branch.</text>
   122 			<text>The released version e.g. 2.3.1 should be tagged as v2.3.1 and be placed in the v_2.3 branch.</text>
   123 			<text>Where the v_2.3 branch was forked from the v_2 branch – from the v2.3 tag.</text>
   123 			<text>Where the v_2.3 branch was forked from the v_2 branch – from the v2.3 tag.</text>
   124 		</item>
   124 		</item>
   125 		<item>
   125 		<item>
   126 			<id>ae33d206-4988-44ec-b8e2-3120019fcf2f</id>
   126 			<id>ae33d206-4988-44ec-b8e2-3120019fcf2f</id>
   127 			<text>Do not remove features unless they are really obsolete, unused or unrepairably broken.</text>
   127 			<text>Do not remove features unless they are really obsolete, unused or irreparably broken.</text>
   128 		</item>
   128 		</item>
   129 		<item>
   129 		<item>
   130 			<id>c542336a-fce8-412c-a8dd-1328c1a884ec</id>
   130 			<id>c542336a-fce8-412c-a8dd-1328c1a884ec</id>
   131 			<text>The user interface might be simplified or redesigned while preserving the features under the hood.</text>
   131 			<text>The user interface might be simplified or redesigned while preserving the features under the hood.</text>
   132 		</item>
   132 		</item>
   331 			<id>e5154815-eeae-4664-8883-a29a64eea325</id>
   331 			<id>e5154815-eeae-4664-8883-a29a64eea325</id>
   332 			<text>builds should be reproducible: same code/version → same binary package</text>
   332 			<text>builds should be reproducible: same code/version → same binary package</text>
   333 		</item>
   333 		</item>
   334 		<item>
   334 		<item>
   335 			<id>a3b0c164-4dde-4e33-b3be-5478d2a187e2</id>
   335 			<id>a3b0c164-4dde-4e33-b3be-5478d2a187e2</id>
   336 			<text>if not, it should be documented, why and how build products mihgt differ, and there should be plan/task to make it reproducible</text>
   336 			<text>if not, it should be documented, why and how build products might differ, and there should be plan/task to make it reproducible</text>
   337 		</item>
   337 		</item>
   338 	</chapter>
   338 	</chapter>
   339 	
   339 	
   340 	<chapter>
   340 	<chapter>
   341 		<name>Trustworthy packages and sources</name>
   341 		<name>Trustworthy packages and sources</name>
   433 				<id>abd48eae-d287-4729-80ee-52dd018b0ba7</id>
   433 				<id>abd48eae-d287-4729-80ee-52dd018b0ba7</id>
   434 				<text>If given software/format/protocol has some default encoding, it must be clearly defined in its specification and this default must not be changed without changing the major version number.</text>
   434 				<text>If given software/format/protocol has some default encoding, it must be clearly defined in its specification and this default must not be changed without changing the major version number.</text>
   435 			</item>
   435 			</item>
   436 			<item>
   436 			<item>
   437 				<id>c9f4d9f4-f959-48ad-bc68-6720dd4596e3</id>
   437 				<id>c9f4d9f4-f959-48ad-bc68-6720dd4596e3</id>
   438 				<text>If there is no default, the encoding must be specified in the metadata attached (e.g. protocol headers, extended attributes on filesystem) to the actual data or at least at the begining of the data (like declaration in XML format).</text>
   438 				<text>If there is no default, the encoding must be specified in the metadata attached (e.g. protocol headers, extended attributes on filesystem) to the actual data or at least at the beginning of the data (like declaration in XML format).</text>
   439 			</item>
   439 			</item>
   440 		</item>
   440 		</item>
   441 		<item>
   441 		<item>
   442 			<id>ce45c382-6ec5-41e8-869a-a0e758621b13</id>
   442 			<id>ce45c382-6ec5-41e8-869a-a0e758621b13</id>
   443 			<text>The metric system should be used as default.</text>
   443 			<text>The metric system should be used as default.</text>