CAcert Code Development list.

[Michael Tänzer <michael.taenzer AT cacert.org>]

Hi guys,

Some incompatibilities between applied bug fixes required that the test
server be reset to the release version and the bug fix feature branches
that are OK are merged on top of it.

I took the opportunity to also rename the branch master to testserver to
better reflect what it is good for. I.e. everywhere you used master now
use testserver and it should be fine.

If you don't know about the git repository yet:
It is available at git://git-cacert.it-sls.de/cacert-devel.git check it
out (you can browse it online via
http://git-cacert.it-sls.de/cgi-bin/gitweb.cgi?p=cacert-devel.git ;)

The branches:
- release: tracks the state of the software as it should be installed on
the critical system, once it is deployed the tarballs from the website
are imported back in to make sure everything went well

- bug-XXX: these are feature branches evolved from release where the fix
for each bug is developed (IMPORTANT: all feature branches should start
from release, _not_ testserver, as they would get all the experimental
clutter from the test system otherwise)

- testserver: this reflects the code as it is on the test server, once a
bug is ready to test it is merged here by an Software Assessor and the
working copy of the test server is updated

- testserver-mods: this contains the changes to the software required by
the test server (e.g. we use a different colour scheme so it can't be
confused with the live system)

- signer: modifications that are required so the signer can run on the
same system as the test server


Have fun,
-- 
Michael Tänzer
CAcert Support Team Leader

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature