[cvs] [Wiki] changed: ReleaseManagement

[Chuck Hagenbuch]

chuck  Mon, 20 Oct 2008 16:43:02 -0400

Modified page: http://wiki.horde.org/ReleaseManagement
New Revision:  2.11
Change log:  horde 4 release management notes

@@ -14,8 +14,9 @@
  * Nag 2.3
  * Turba 2.3
  * Hermes 1.0
  * Whups 1.0
+

  +++ Applications to be released following Horde 3.3

  * Ansel 1.0
@@ -25,8 +26,21 @@
  * Passwd 3.1
  * Trean 1.0
  * Vacation 3.1
  * Wicked 1.0
+
+
+++ Horde 4.0
+
+The decisions made for Horde 4 so far are:
+
+* Move to git for future (Horde 4+) version control. Code will be  
pushed to a clean git repository as it is modified for Horde 4 and PHP  
5. Git pushes will generate email to a new list,  
commits at lists.horde.org. Everything currently in CVS will remain  
available, and Horde 3.x will continue to be developed in and released  
from the existing CVS structure.
+* Aim for shorter release cycles of major versions. When backwards  
compatibility is broken we will increment the major version number  
(Horde 3 to Horde 4) as we do now; we'll just do that more often.  
Feedback indicates that being able to do feature upgrades of an  
application but not Horde, or vice versa, is not a big advantage for  
most people.
+* 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
+

  ++ Roadmaps

  +++ Horde