For the most current code you MUST use the Git repositories. CVS HEAD is no longer maintained and will NOT work. This page still has to be updated to reflect the current state of modules in Git

When checking out applications, you should probably check out horde first, then cd horde, and then check out any additional modules that you want. hordeweb, hordedoc, and presentations are the exceptions to this; the documentation and presentations can live wherever you like, and the website should probably live elsewhere in your web tree.

A note on stability

The HEAD branch of a module will almost always be development code, and may be unstable. The stability listed for each module is the general state of that module. However, just because that IMP and Horde are listed as Production quality software, doesn't mean that HEAD will always work, be documented, compile, or not cause frogs to dive-bomb you from tall trees. You've been warned. ;)

A note on tags

The tags generally take one of three formats:

1. HEAD -- This is always the current development branch, and may be unstable and undocumented. Any code that has not yet been released will have only a HEAD branch. All other branches will be branches off the HEAD branch.CVS HEAD is no longer maintained.
2. FRAMEWORK_* -- These branches are created for major stable releases. Modules with a FRAMEWORK_* tag are compatible with each other. For example, IMP FRAMEWORK_3 is compatible with Horde FRAMEWORK_3.
3. RELENG_* -- These are the RELease ENGineering branches. These branches are the code for the next releases. Each RELENG branch is identified by a number which indicates the version of the software. So RELENG_1 corresponds to the 1.x releases, RELENG_2 to the 2.x releases, RELENG_3 to the 3.x releases, and so on. These tags are obsolete. Use the FRAMEWORK_* tags instead.