This section describes the release process of the stable Horde releases.
The decisions made for Horde 4 so far are:
Full minutes of the board meeting where this was discussed: http://lists.horde.org/archives/board/2008-October/000085.html
We have three git repositories:
The horde respository has stable code in it.
The horde-hatchery respository is a playground for new code and refactoring old code. Once a module a stabilized here, it's being moved to the horde repository.
The horde-support repository has maintainer and relase tools, and the git and svn hooks in it. Once we have update mechanisms in place, we'll add hordeweb there.
hordedoc is an open question.
Also, just a reminder that git push messages are going to firstname.lastname@example.org, not email@example.com.
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-hatchery, 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: You will need to download the two Git repositories:
git clone --depth 1 git://dev.horde.org/horde/git/horde horde-git git clone --depth 1 git://dev.horde.org/horde/git/horde-hatchery
Creating a web-accessible installation can be done simply by running the install_dev PHP script (located at horde-git/framework/bin in the repository checked out above). To run this script, copy horde-git/framework/bin/install_dev.conf.dist to horde-git/framework/bin/install_dev.conf and edit that file to match the setup of your server. Running that script will symlink the entire horde package into the web-accessible directory you specify, symlink all other horde applications within that directory, and will properly set up the necessary include/horde path definitions. Note that all edits should take place within the repository, as the horde directory will be deleted every time the install_dev script is run. Additionally, full directory paths will be needed in the horde/config/registry.php file due to the symlinks.
Q: Why does the sidebar not collapse/Why can't I switch tabs on the config screen/Why do certain links not work?
Please see Horde 4 Conversion for more details on porting Horde 3 libraries to Horde 4.