Release tagging Releases are only based on checkpoint tree code. Maintenance fixes to releases are also maintained within the checkpoint tree. Files within a release must have accompanying documentation. The form of this documentation depends on the file type. Branches Branches are a useful tool for making changes prior to checkpoints without breaking other working versions but it must be understood that branches are short-lived and that releases and checkpoints not be made from a branch.
Branches are especially useful for adding totally new features.
The only historical code maintenance that s employed is for fixes and patches to formal releases - not checkpoints. Complain that the quality of work is too low and then do nothing to fix the code. We advise you to only use the third option if you are confident that your own contributions to the code are bug-free, well written, documented and fool proof. If you think the policies are not appropriate then let us know and we can discuss changing them. It looks cool, but policies are still important.