|
|
Horde CVS ModulesThe following modules are in the Horde CVS Repository, with the listed
production level code tags available. If no tags are listed, then there has
not yet been a stable release of that module.
All modules have the HEAD tag available, which contains the current bleeding-edge code.
| Module |
Release |
Description |
Tags |
Status |
| horde | 3.3 | 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 | | Photo Gallery application | | Beta |
| beatnik | | DNS record management user interface | | Beta |
| chora | H3 (2.0.2) | CVS repository front-end | FRAMEWORK_3, RELENG_1 | Production |
| dimp | H3 (1.1) | Dynamic IMP | FRAMEWORK_3 | Production |
| forwards | H3 (3.0.1) | E-Mail forwarding module | RELENG_1, RELENG_2 | Production |
| genie | | Wishlist application | | Production |
| gollem | H3 (1.0.4) | Web-based File Manager | FRAMEWORK_3 | Production |
| goops | | Meta search engine | | Beta |
| hermes | H3 (1.0) | Time-tracking/billing data system | FRAMEWORK_3 | Production |
| hordedoc | | Horde documentation project | | |
| hordeweb | | The horde.org website | | |
| imp | H3 (4.3) | 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.1) | 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 | | Comics module | RELENG_1 | Production |
| kronolith | H3 (2.3) | 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.1) | A Mobile (WAP, etc.) version of IMP | FRAMEWORK_3 | Production |
| mnemo | H3 (2.2.1) | A Memo/Notepad application | FRAMEWORK_3, RELENG_1 | Production |
| mottle | | MOTD tool | | Alpha |
| nag | H3 (2.3.1) | Task Manager | FRAMEWORK_3, RELENG_1 | Production |
| nic | | Basic network service monitoring | | Beta |
| passwd | H3 (3.0.1) | Password changing module | FRAMEWORK_3, RELENG_1, RELENG_2 | Production |
| presentations | | Horde-related presentations | | |
| sam | | A Spam Assassin module | | Beta |
| scry | | Polls application | FRAMEWORK_3 | Beta |
| sesha | | Inventory manager | | Beta |
| skeleton | | A template for new Horde applications | | |
| sork | | Alias for accounts, forwards, passwd, and vacation | | |
| swoosh | | SMS messenger | | Beta |
| trean | | Bookmarks manager | | Beta |
| turba | H3 (2.3) | Contacts/Addressbook system | FRAMEWORK_3, RELENG_1 | Production |
| ulaform | | A form generation/processing tool | | Beta |
| vacation | H3 (3.0.1) | E-Mail vacation notice module | RELENG_1, RELENG_2 | Production |
| vilma | | Virtual email domain administrator | | Alpha |
| volos | | Guestbook application | | Beta |
| whups | H3 (1.0) | A project management system | FRAMEWORK_3 | Production |
| wicked | | A Wiki | | Beta |
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 stabilityThe 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. ;)
The tags generally take one of three formats:
- 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.
- 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.
- 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.
- There are other tags available, but there use is not generally
needed or recommended, or have been obsoleted, and hence they are not
discussed here.
|
