[Wiki] changed: ReleaseManagement

chuck  Mon, 20 Oct 2008 23:04:50 -0400

Modified page: http://wiki.horde.org/ReleaseManagement
New Revision:  2.12
Change log:  start a mini-faq on horde 4

@@ -39,8 +39,13 @@
  * 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

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

  ++ Roadmaps

  +++ Horde

--
To unsubscribe, mail: [email protected]