You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ofbiz.apache.org by ja...@apache.org on 2014/08/07 17:21:41 UTC

svn commit: r1616507 - /ofbiz/site/download.html

Author: jacopoc
Date: Thu Aug  7 15:21:41 2014
New Revision: 1616507

URL: http://svn.apache.org/r1616507
Log:
Improved the description of the naming convention for releases; based on feedback from Ron Wheeler

Modified:
    ofbiz/site/download.html

Modified: ofbiz/site/download.html
URL: http://svn.apache.org/viewvc/ofbiz/site/download.html?rev=1616507&r1=1616506&r2=1616507&view=diff
==============================================================================
--- ofbiz/site/download.html (original)
+++ ofbiz/site/download.html Thu Aug  7 15:21:41 2014
@@ -87,26 +87,25 @@ find instructions on how to verify the i
 <li>Nightly snapshots can be found <a href="http://ci.apache.org/projects/ofbiz/snapshots/" target="_blank">here</a></li>
 </ul>
 <h3>Release Information</h3>
-<ul>The naming convention for OFBiz releases is <b>&lt;Major Release Number&gt;.&lt;Minor Release Number&gt;</b> where:
-<li>&lt;Major Release Number&gt; is in the format of &lt;YY.MM&gt; where YY and MM are the year and month the release branch was created (i.e. date of the feature freeze);
-   a new Major Release Number is normally created every year in April (09.04, 10.04, 11.04 etc...)</li>
-<li>&lt;Minor Release Number&gt; is a two digit sequential number: 01 (if specified) is the first release from the <Major Release Number> branch; 02 is the second etc...;
-    for a given Major Release Number you should always use the release with the highest Minor Release Number because it represents the latest bug fix release for the Major Release Number you are using.</li>
+<ul>The naming convention for OFBiz releases is <b>&lt;Release Freeze Date&gt;.&lt;Minor Release Number&gt;</b> for example &lt;13.07&gt;.&lt;04&gt; where:
+<li>&lt;Release Freeze Date&gt; is in the format of &lt;YY.MM&gt; where YY and MM are the year and month of the date of the feature freeze;</li>
+<li>&lt;Minor Release Number&gt; is a two digit sequential number: 01 is the first release from the branch; 02 is the second etc...;
+    for a given Release Freeze Date you should always use the release with the highest Minor Release Number because it represents the latest bug fix release for the Release Freeze Date you are using.</li>
 </ul>
 
 <ul>Tentative release schedule for the 11.04 series:
-<li>July 2014 - Apache OFBiz 11.04.05 (last release of the 11.04 series)</li>
+<li>August 2014 - Apache OFBiz 11.04.05 (last release of the 11.04 series)</li>
 </ul>
 <ul>Tentative release schedule for the 12.04 series:
-<li>September 2014 - Apache OFBiz 12.04.04</li>
+<li>August 2014 - Apache OFBiz 12.04.04</li>
 <li>April 2015 - Apache OFBiz 12.04.05 (last release of the 12.04 series)</li>
 </ul>
 <ul>Tentative release schedule for the 13.07 series:
-  <li>June 2014 - Apache OFBiz 13.07.01</li>
-  <li>August  2014 - Apache OFBiz 13.07.02</li>
-  <li>March  2015 - Apache OFBiz 13.07.03</li>
-  <li>September  2015 - Apache OFBiz 13.07.04</li>
-  <li>April 2016 - Apache OFBiz 13.07.05 (last release of the 13.07 series)</li>
+  <li>August 2014 - Apache OFBiz 13.07.01</li>
+  <li>March  2014 - Apache OFBiz 13.07.02</li>
+  <li>September  2015 - Apache OFBiz 13.07.03</li>
+  <li>April  2015 - Apache OFBiz 13.07.04</li>
+  <li>February 2016 - Apache OFBiz 13.07.05 (last release of the 13.07 series)</li>
 </ul>
 <a name="vulnerabilities"></a>
 <h3>Security Vulnerabilities</h3>