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

Module	Release	Description	Tags	Status
horde	3.3.13	The core Horde libraries and framework	FRAMEWORK_3, RELENG_2, STABLE_1_2	Production
framework		Horde Framework libraries	FRAMEWORK_3	Production
agora		Forum module	FRAMEWORK_3	Beta
ansel	H3 (1.1.2)	Photo Gallery application	FRAMEWORK_3	Production
beatnik		DNS record management user interface		Development
chora	H3 (2.1.1)	VCS (version control system) repository front-end	FRAMEWORK_3, RELENG_1	Production
dimp	H3 (1.1.8)	Dynamic IMP DIMP has been merged into IMP in git.	FRAMEWORK_3	Production
forwards	H3 (3.2.1)	E-Mail forwarding module	FRAMEWORK_3, RELENG_1, RELENG_2	Production
genie		Wishlist application		Beta
gollem	H3 (1.1.2)	Web-based File Manager	FRAMEWORK_3	Production
goops		Meta search engine		Beta
hermes	H3 (1.0.1)	Time-tracking/billing data system	FRAMEWORK_3	Production
hordedoc		Horde documentation project
hordeweb		The horde.org website
imp	H3 (4.3.11)	The IMP Webmail Client	FRAMEWORK_3, RELENG_3, STABLE_2_2	Production
incubator		Projects that are in development - "incubating"		Alpha, Beta, Experimental
ingo	H3 (1.2.6)	Mail filtering administration	FRAMEWORK_3, RELENG_1	Production
jeta	H3 (1.0)	Wrapper around the Java Telnet App	FRAMEWORK_3	Production
jonah		RSS/News module		Beta
juno		Checkbook tracking module		Alpha
klutz	H3 (1.0)	Comics module	FRAMEWORK_3, RELENG_1	Production
kronolith	H3 (2.3.6)	Calendar and scheduling	FRAMEWORK_3, RELENG_1	Production
luxor		LXR Port		Beta
merk		Online shopping system		Beta
midas		Ad/banner serving and management		Beta
mimp	H3 (1.1.4)	A mobile (no graphics/javascript) version of IMP MIMP has been merged into IMP in git.	FRAMEWORK_3	Production
mnemo	H3 (2.2.5)	A Memo/Notepad application	FRAMEWORK_3, RELENG_1	Production
mottle		MOTD tool		Alpha
nag	H3 (2.3.7)	Task Manager	FRAMEWORK_3, RELENG_1	Production
nic		Basic network service monitoring		Beta
passwd	H3 (3.1.3)	Password changing module	FRAMEWORK_3, RELENG_1, RELENG_2	Production
presentations		Horde-related presentations
sam		A Spam Assassin module	FRAMEWORK_3	Beta
scry		Polls application	FRAMEWORK_3	Beta
sesha		Inventory manager		Beta
skeleton		A template for new Horde applications	FRAMEWORK_3
sork		Alias for accounts, forwards, passwd, and vacation
swoosh		SMS messenger		Beta
trean		Bookmarks manager		Beta
turba	H3 (2.3.6)	Contacts/Addressbook system	FRAMEWORK_3, RELENG_1	Production
ulaform		A form generation/processing tool		Beta
vacation	H3 (3.2.1)	E-Mail vacation notice module	FRAMEWORK_3, RELENG_1, RELENG_2	Production
vilma		Virtual email domain administrator		Alpha
volos		Guestbook application		Beta
whups	H3 (1.0.1)	A project management system	FRAMEWORK_3	Production
wicked		A Wiki	FRAMEWORK_3	Production

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.