[commits] [Wiki] changed: Doc/Dev/ReleaseCycle

[Ralf Lang (B1 Systems GmbH)]

rlang  Thu, 24 Jan 2013 19:22:33 +0100

Modified page: http://wiki.horde.org/Doc/Dev/ReleaseCycle
New Revision:  3
Change log:  add ConversionH5

@@ -7,9 +7,9 @@
    * Adding features or extending APIs will bump the minor version,  
Horde 4.0 becomes Horde 4.1 etc.
  * New versions will be released every half a year. Whether these are  
going to be major or minor version releases (or even just bug fix  
releases) depends on whether the changes since the last release broke  
BC or not.
    * Intermediate releases can be be done for security fixes or bug fixes.
  * We will have sychronized releases of all application and framework  
components. If it's going to be a minor version release, only the  
modules that actually had any changes will be released. For major  
versions, all modules will be relased.
-* Breaking backward compatibility will be documented, so that custom  
applications can be updated easily. See ((Doc/Dev/ConversionH4)) for  
an example.
+* Breaking backward compatibility will be documented, so that custom  
applications can be updated easily. See ((Doc/Dev/ConversionH4)) and  
((Doc/Dev/ConversionH5))for an example.
  * The most recent two major versions will be maintained with  
security fixes, i.e. for at least 12 months.

  *APIs in this context mean PHP APIs of framework components,  
external PHP APIs of applications, and external Horde RPC APIs.