The Horde CVS Repository

How Horde CVS is organized

All of the code in our repository is split into a set of modules. However, sometimes there are multiple branches available of a module. A CVS branch is a mechanism for keeping multiple versions of a module; for instance, a stable branch and a development branch.

Our branches and release engineering can seem a little convoluted at first, but follows some pretty simple rules. When you check something out of CVS, by default, you get the HEAD branch. HEAD is always the latest development code. It may be undocumented, it may be broken, it may cause tofu to turn purple. You never know.

The branches that hold release versions of applications - code that is documented, tested, and recommended for production use - are named FRAMEWORK_3, where _3 means that this includes Horde 3.x and any applications that are compatible to Horde 3. So, the release branch for IMP 4.x and Horde 3.x is both FRAMEWORK_3. Note that this doesn't give you a way to distinguish between IMP 4.0 and IMP 4.1 - they live in the same CVS branch, because one supercedes the other. However, we do tag releases, so you can check out IMP 4.0 with the IMP_4_0 tag.

There are some old branches available that hold old release versions of applications, named RELENG_*, where * is the major version of the application in question. So, the release branch for IMP 3.x is RELENG_3. The release branch for Horde 2.x is RELENG_2. Note that this doesn't give you a way to distinguish between IMP 3.0 and IMP 3.1 - they live in the same CVS branch, because one supercedes the other. However, we do tag releases, so you can check out IMP 3.0 with the IMP_3_0 tag.