[cvs] [Wiki] changed: ReleaseManagement

[Michael Slusarz]

slusarz  Mon, 05 Apr 2010 23:52:26 -0400

Modified page: http://wiki.horde.org/ReleaseManagement
New Revision:  2.36
Change log:  Updated documentation

@@ -58,40 +58,19 @@
  Full minutes of the board meeting where this was discussed:  
http://lists.horde.org/archives/board/2008-October/000085.html

  +++ Git layout

-We have three git repositories:
-
-* horde
-* horde-hatchery
-* horde-support
-
-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  
commits at lists.horde.org, not cvs at lists.horde.org.
-
+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-hatchery, etc.), and we'll  
use branches to do local dev or to coordinate non-mainline work.
+**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:** You will need to download the two Git repositories:
-<code>
-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
-</code>
-
-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.
+**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.