[Wiki] changed: ReleaseManagement

chuck  Tue, 21 Oct 2008 00:15:34 -0400

Modified page: http://wiki.horde.org/ReleaseManagement
New Revision:  2.13
Change log:  more on the git layout

@@ -38,8 +38,26 @@
  * 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
+
+We have three git repositories:
+
+* 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.
+
+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 support repository has 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  
[email protected], not [email protected].

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

--
To unsubscribe, mail: [email protected]