'Helps us to avoid long, winding threads in our mailing lists' was what I wanted to bring across.
Best regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Tue, Mar 24, 2015 at 12:43 PM, Pierre Smits <pierre.sm...@gmail.com> wrote: > +1 for statement of Jacques. And it should also be stated on our 'release > policy' page. > > Clear, unambiguous messages ensure that we tell a consistent story. Not > only to potential adopters but they also remind of what we do, for whom and > how. Having those up front helps us to have long, winding threads in our > mailing lists. > > Best regards, > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Tue, Mar 24, 2015 at 12:33 PM, Jacques Le Roux < > jacques.le.r...@les7arts.com> wrote: > >> Le 24/03/2015 11:41, Jacopo Cappellato a écrit : >> >>> In the download page we should also strive to have a more formal >>> language: maybe Sharan, Adrian or others that are fluent with English can >>> help here. >>> But apart from the above comment: do we really need this sentence in the >>> download page? What is the goal you are trying to achieve? >>> As we discussed in the list, the community does its best to backport >>> bugs; if a bug is not backported and a ticket is created for it with a >>> backported patch then a committer will pick it up and commit. Why should we >>> tell the users to backport themselves? >>> >> >> Because we don't backport all bug fixes to all living release branches, >> how can I say it otherwise? >> It seems to me our users should be aware of that >> >> Jacques >> >> >> >>> Jacopo >>> >>> On Mar 24, 2015, at 11:18 AM, jler...@apache.org wrote: >>> >>> Author: jleroux >>>> Date: Tue Mar 24 10:18:18 2015 >>>> New Revision: 1668834 >>>> >>>> URL: http://svn.apache.org/r1668834 >>>> Log: >>>> Adds a note about "not all bug fixes are backported to all living >>>> release branches" >>>> >>>> Modified: >>>> ofbiz/site/download.html >>>> >>>> Modified: ofbiz/site/download.html >>>> URL: http://svn.apache.org/viewvc/ofbiz/site/download.html?rev= >>>> 1668834&r1=1668833&r2=1668834&view=diff >>>> ============================================================ >>>> ================== >>>> --- ofbiz/site/download.html (original) >>>> +++ ofbiz/site/download.html Tue Mar 24 10:18:18 2015 >>>> @@ -61,12 +61,17 @@ >>>> </ul> >>>> </div> >>>> <p> >>>> -Apache OFBiz™ is an open source product for the automation of >>>> enterprise >>>> +Apache OFBiz™ is an open source product for the automation of >>>> enterprise >>>> processes that includes framework components and business applications. >>>> </p> >>>> <p> >>>> Use the links below to download Apache OFBiz releases from the "Apache >>>> Download Mirrors" page; in that page you'll also >>>> find instructions on how to verify the integrity of the release file >>>> using the signature and hashes (PGP, MD5, SHA512) available for each >>>> release. >>>> +<p>Just as a note: despite our best efforts, not all bug fixes are >>>> backported to all living release branches. But using >>>> +<a href="https://issues.apache.org/jira/browse/OFBIZ/? >>>> selectedTab=com.atlassian.jira.jira-projects-plugin:changelog-panel" >>>> target="_blank">releases logs </a> or >>>> +<a href="http://svn.apache.org/viewvc/ofbiz/"; >>>> target="_blank">commits logs </a>you should always be able to backport >>>> yourself. >>>> +</p> >>>> + >>>> </p> >>>> <h3>Apache OFBiz 13.07.01</h3> >>>> <p>Released in October 2014, is the first release of the 13.07 series, >>>> that has been stabilized with bug fixes since July 2013. It is the OFBiz >>>> current stable release and users of the previous releases are encouraged to >>>> migrate to it in order to get all the new features.</p> >>>> >>>> >>>> >>> >>> >
