Codegroup Version Branching

Codegroup Version Branching

Codgroup, when it reaches a stable form should and must be branched into different versions for different user groups. It is optimal for everyone if there are at least 32 different flavours of Codgeroup in current use. Other branched versions may use higher levels (and more levels) of cryptography.

Version Branching Principals

All versions must be readily distinguishable via their headers.

Header information differentiating different encoder-decoder pairs must be standardized.

Generally, this should be interpreted to mean

-- The header text should read "PRAGMA ENCODER"
-- For this branch "AA"
-- For year of branch "2012"
-- For subversion "Z99" (decriment to A00), when the encoding state machine changes.
-- For "Minor tweaks" in subversions, use A, B, C, D ... appended. Thus : "PRAGMA ENCODER AA2012Z99A" (example only)
-- So the current version is "PRAGMA ENCODER AA2012Z99"

Versions should have "Friendly names" (separate from the core state encoder-decoder machine version)

Generally, this should be interpreted to mean

-- "PRAGMA FRIENDLY NAME EQUALS" in the header, support for non English headers should be considered.
-- ALWAYS KEEP "PRAGMA" IN TRANSLATION : Also use EGAL, EQU, IST, EST, HERE ...
-- Place names and River names should be next ...
-- So output should be "PRAGMA FRIENDLY NAME EQUALS VANCOUVER"