[Wiki] changed: ReleaseManagement

jan  Mon, 30 Mar 2009 05:51:24 -0400

Modified page: http://wiki.horde.org/ReleaseManagement
New Revision:  2.30
Change log:  We don't need a copy of the previous section, just  
reworded. Make this really a step-by-step instruction

@@ -59,9 +59,9 @@
  hordedoc is an open question.

  Also, just a reminder that git push messages are going to  
[email protected], not [email protected].

-+++ Mini-FAQ for Horde 4 development:
++++ 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. We'll figure this out as we work on Horde 4, to some  
extent, but my expectation is that we will all push commits 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.
@@ -90,38 +90,25 @@
  * For the actual Horde applications that have been moved to Git,  
there are a few options.  You could either copy the application  
directory back and forth from your /horde directory, you could try to  
use a joint CVS/Git source tree, or you can symlink the application  
into your horde/ directory.  Both methods have drawbacks. Issues with  
the first are obvious - you need to pull, copy, code, copy, push  
etc... The issue with second method is that you will either get lots  
of warnings about files that aren't tracked, or you could try to  
manage an ignore list for both CVS and Git. If you use a symlink, you  
will need to create a file base.local.php in the application's lib/  
directory - and define your HORDE_BASE in that file.

  **Q:** How do I start from scratch with a git/cvs head install

-**A:**
-# [http://www.horde.org/source/using.php checkout the horde cvs  
head], the [http://www.horde.org/source/git.php horde git head and the  
horde-hatchery head]
-# Make a directory that holds your horde pear related files - make  
sure to add this to your php path
-# Make sure you have met all of the  
[http://www.horde.org/horde/docs/?f=INSTALL.html prerequisites for a  
normal horde install]
-# Create symlinks from your three repository clones to the horde pear  
related file location
-# Copy the config/*.php.dist files and edit them as appropriate
-# Fix the javascript folder
-# Run your database install script
-
-One possible setup:
-<code>
-/var/www/horde <- horde cvs head
-/var/www/git/horde <- horde git head
-/var/www/git/horde-hatchery <- horde-hatchery head
-/var/www/pear <- horde pear related files
-</code>
+**A:**
+These steps only work on case sensitive file systems, see above:

-Create the symlinks using one of the two methods above  
(horde-fw-symlinks.php), using /var/www/pear as your destination and  
the appropriate source from just above.
-
-Fix the Javascript folder by: (there's probably a better way to do this)
  <code>
-cd horde/js
-cp src/*.js .
+cvs -d:pserver:cvs.horde.org:/repository checkout horde framework
+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
+pear install framework/devtools/package.xml
+cd horde
+mkdir libs
+horde-fw-symlinks.php
+horde-fw-symlinks.php --src ../horde-git/framework
+horde-fw-symlinks.php --src ../horde-hatchery/framework
+echo "<?php ini_set('include_path', dirname(__FILE__) . '/../libs' .  
PATH_SEPARATOR . ini_get('include_path'));" > lib/core.local.php
  </code>

-Run the database install script
-<code>
-cd horde/scripts/sql/
-mysql -u root -p < create.mysql.sql
-</code>
+Then continue with the installation steps in docs/INSTALL.

  ++ Roadmaps

  +++ Horde


--
To unsubscribe, mail: [email protected]