Author: jacopoc
Date: Wed Feb 29 13:57:01 2012
New Revision: 1295109
URL:
http://svn.apache.org/viewvc?rev=1295109&view=revLog:
Fixed some grammar errors; thanks to Anne Jessel for the corrections.
Modified:
ofbiz/site/download.html
Modified: ofbiz/site/download.html
URL:
http://svn.apache.org/viewvc/ofbiz/site/download.html?rev=1295109&r1=1295108&r2=1295109&view=diff==============================================================================
--- ofbiz/site/download.html (original)
+++ ofbiz/site/download.html Wed Feb 29 13:57:01 2012
@@ -86,9 +86,9 @@ Use the links below to download Apache O
find instructions on how to verify the integrity of the release file using the signature and hashes (PGP, MD5, SHA512) available for each release.
<ul>The current naming convention for OFBiz releases is <b><Major Release Number>.<Minor Release Number></b> where:
-<li><Major Release Number> is in the format of <YY.MM> where YY and MM are the year and month of when the release branch was created (i.e. date of the feature freeze);
- a new Major Release Number is created every year on April (09.04, 10.04, 11.04 etc...)</li>
-<li><Minor Release Number> is a two digits sequential number: 01 (if specified) is the first release from the <Major Release Number> branch; 02 is the second etc...;
+<li><Major Release Number> is in the format of <YY.MM> 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 created every year in April (09.04, 10.04, 11.04 etc...)</li>
+<li><Minor Release Number> 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>
</p>
Locked
