[commits] [Wiki] changed: ReleaseManagement

Mon Mar 7 23:07:45 UTC 2011

jan  Mon, 07 Mar 2011 23:07:45 +0000

Modified page: http://wiki.horde.org/ReleaseManagement
New Revision:  2.39
Change log:  Move Horde 4 up

@@ -2,8 +2,45 @@

  + Horde Release Management

  This section describes the release process of the stable Horde releases.
+
+++ Horde 4.0
+
+**[ShowStoppersFourOh Showstoppers for H4 Release]**
+
+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
+
++++ Git layout
+
+See http://www.horde.org/source/git.php
+
++++ 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. All HEAD commits are pushed to  
dev.horde.org:/horde/git/horde (or horde-support, etc.), and we'll use  
branches to do local dev or to coordinate non-mainline work.
+
+**Q:** How do I start from scratch with a Git install
+
+**A:** See http://www.horde.org/source/git.php
+
+**Q:** Why does the sidebar not collapse/Why can't I switch tabs on  
the config screen/Why do certain links not work?
+
+**A:** Make sure your 'jsfs' and 'jsuri' entries in  
horde/config/registry.php are correct. They are actually no needed  
anymore at all, unless you really know what you are doing.  
Applications no longer come shipped with javascript source files in  
js/src - they all live directly under js/ now.
+
+
++++ Conversion from Horde 3
+
+Please see ((Doc/Horde4Conversion|Horde 4 Conversion)) for more  
details on porting Horde 3 libraries to Horde 4.
+

  ++ Horde 3.3 Release

  +++ Applications that were released along with Horde 3.3
@@ -43,45 +80,8 @@

  * Trean 1.0 (http://bugs.horde.org/ticket/4969,  
http://bugs.horde.org/ticket/7812)

  * Wicked 1.0 (http://bugs.horde.org/queue/wicked)
-
-
-++ 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
-
-**[ShowStoppersFourOh Showstoppers for H4 Release]**
-
-+++ Git layout
-
-See http://www.horde.org/source/git.php
-
-+++ 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. All HEAD commits are pushed to  
dev.horde.org:/horde/git/horde (or horde-support, etc.), and we'll use  
branches to do local dev or to coordinate non-mainline work.
-
-**Q:** How do I start from scratch with a Git install
-
-**A:** See http://www.horde.org/source/git.php
-
-**Q:** Why does the sidebar not collapse/Why can't I switch tabs on  
the config screen/Why do certain links not work?
-
-**A:** Make sure your 'jsfs' and 'jsuri' entries in  
horde/config/registry.php are correct. They are actually no needed  
anymore at all, unless you really know what you are doing.  
Applications no longer come shipped with javascript source files in  
js/src - they all live directly under js/ now.
-
-
-+++ Conversion from Horde 3
-
-Please see ((Doc/Horde4Conversion|Horde 4 Conversion)) for more  
details on porting Horde 3 libraries to Horde 4.


  ++ Roadmaps


