Horde Release Management
This section describes the release process of the stable Horde releases.
Horde 4.0
Framework packages to be released with Horde 4
Horde 4 release notes
IMP 5 release notes
Ingo 2 release notes
Turba 3 release notes
Kronolith 3 release notes
Nag 3 release notes
Mnemo 3 release notes
Showstoppers for H4 Release
The decisions made for Horde 4 so far are:
- Move to git for future (Horde 4+) version control. Code will be pushed to a clean git repository as it is modified for Horde 4 and PHP 5. Git pushes will generate email to a new list, commits@lists.horde.org. Everything currently in CVS will remain available, and Horde 3.x will continue to be developed in and released from the existing CVS structure.
- Aim for shorter release cycles of major versions. When backwards compatibility is broken we will increment the major version number (Horde 3 to Horde 4) as we do now; we'll just do that more often. Feedback indicates that being able to do feature upgrades of an application but not Horde, or vice versa, is not a big advantage for most people.
- Use individual package versions much more extensively with Horde 4. We want it to be possible to release an application upgrade that relies on new framework functionality without requiring a new major version; instead, many changes will be possible by just requiring a specific package version.
- Finally, and most importantly, we will be focusing on getting the last Horde 3.3 releases out (see above), and then shifting our major focus to Horde 4. Our goal is to have an initial release of Horde 4.0 within 6 months of starting serious development on it; and to aim for major version releases approximately every year thereafter.
Full minutes of the board meeting where this was discussed: http://lists.horde.org/archives/board/2008-October/000085.html
Git layout
See http://www.horde.org/source/git.php
Mini-FAQ for Horde 4 development
Q: Are we going to keep the existing development model where we have a "master" server (i.e. cvs.horde.org) where we will build the releases? For our workflow, that seems to make the most sense - since we don't have a "master" user that checks all commits before integrating.
A: Yes. All HEAD commits are pushed to dev.horde.org:/horde/git/horde (or horde-support, etc.), and we'll use branches to do local dev or to coordinate non-mainline work.
Q: How do I start from scratch with a Git install
A: See http://www.horde.org/source/git.php
Q: Why does the sidebar not collapse/Why can't I switch tabs on the config screen/Why do certain links not work?
A: Make sure your 'jsfs' and 'jsuri' entries in horde/config/registry.php are correct. They are actually no needed anymore at all, unless you really know what you are doing. Applications no longer come shipped with javascript source files in js/src - they all live directly under js/ now.
Conversion from Horde 3
Please see Horde 4 Conversion? for more details on porting Horde 3 libraries to Horde 4.
Horde 3.3 Release
Applications that were released along with Horde 3.3
- Ansel 1.0
- Chora 2.1
- DIMP 1.1
- Forwards 3.1
- Gollem 1.1
- Hermes 1.0
- IMP 4.3
- Klutz 1.0
- Kronolith 2.3
- Nag 2.3
- Passwd 3.1
- Turba 2.3
- Vacation 3.1
- Whups 1.0
Applications to be released following Horde 3.3
Bugs left:
Roadmaps
Horde
http://www.horde.org/horde/roadmap/
IMP
http://www.horde.org/imp/roadmap/
Turba
http://www.horde.org/turba/roadmap/
Ingo
http://www.horde.org/ingo/roadmap/
Kronolith
http://www.horde.org/kronolith/roadmap/
Expanded thoughts on using resources
Nag
http://www.horde.org/nag/roadmap/
Sork
- Merge passwd into framework/Auth library
- Merge vacation and forwards drivers with Ingo and Sam (see Ingo roadmap)
Chora
http://www.horde.org/chora/roadmap/
H4 Marketing Ideas?
Older Releases