[cvs] [Wiki] changed: ReleaseManagement

[Jan Schneider]

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

Modified page: http://wiki.horde.org/ReleaseManagement
New Revision:  2.29
Change log:  Updates on git layout

@@ -49,19 +49,19 @@
  * horde
  * horde-hatchery
  * horde-support

-We've imported framework/Support into the horde repository to have  
something there. More code will move there a bit slowly, faster as we  
sort out git support for Chora, etc.
+The horde respository has stable code in it.

-All of the separate projects (hippo, hydra, crumb, Horde_Date_Parser)  
that were being stored in git or hg as tests have been moved into the  
hatchery repository.
+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 support repository has the git and svn hooks in it. Once we have  
update mechanisms in place, we'll add hordeweb there.
+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.

-+++ 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.