You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Jacopo Cappellato <ja...@hotwaxsystems.com> on 2015/03/24 11:41:33 UTC
Re: svn commit: r1668834 - /ofbiz/site/download.html
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?
Jacopo
On Mar 24, 2015, at 11:18 AM, jleroux@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>
>
>
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Jacques Le Roux <ja...@les7arts.com>.
Done
Jacques
Le 01/04/2015 15:42, Jacopo Cappellato a écrit :
> On Apr 1, 2015, at 3:30 PM, Jacques Le Roux <ja...@les7arts.com> wrote:
>
>> That sounds good to me, I agree it's more complete and less disturbing than my proposition, not sure about "strongly"
>>
>> Jacques
> I agree with Jacques: maybe we can drop the "strongly" word: "recommend" is already clear enough.
>
> Jacopo
>
>
>
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Jacopo Cappellato <ja...@hotwaxsystems.com>.
On Apr 1, 2015, at 3:30 PM, Jacques Le Roux <ja...@les7arts.com> wrote:
> That sounds good to me, I agree it's more complete and less disturbing than my proposition, not sure about "strongly"
>
> Jacques
I agree with Jacques: maybe we can drop the "strongly" word: "recommend" is already clear enough.
Jacopo
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Jacques Le Roux <ja...@les7arts.com>.
That sounds good to me, I agree it's more complete and less disturbing than my proposition, not sure about "strongly"
Jacques
Le 01/04/2015 15:01, Sharan Foga a écrit :
> Hi All
>
> My suggestion would be:
>
> "Despite our best efforts to maintain up to three active release branches, support for older branches can decrease because our project volunteers
> may be focussed on other issues. We strongly recommend using releases from the most recent branch wherever possible"
>
>
> I think the phrase "because volunteers tend to focus their efforts on issues that hold their interest more" could be seen as a bit negative (i.e
> meaning we are not interested enough to fix your problem) which isn't the message we want to send.
>
> Also the word "strongly" is optional so you can remove it if you think it's a bit too strong - (no pun intended!).
>
> Thanks
> Sharan
>
>
> On 1.4.2015 14:30, Jacopo Cappellato wrote:
>> On Apr 1, 2015, at 2:17 PM, Jacques Le Roux <ja...@les7arts.com> wrote:
>>
>>> Le 01/04/2015 14:15, Jacques Le Roux a écrit :
>>>> So you suggest we say anything?
>>> I meant nothing
>> Yeah.
>> Or, if you really want to add something, I would rather use a text similar to what Adrian and Pierre suggested:
>>
>> "Despite the effort of the community to maintain up to three active release branches, the support for older release branches can decrease - because
>> volunteers tend to focus their efforts on issues that hold their interest more. Whenever possible, we recommend to use the releases from the most
>> recent branch."
>>
>> However even the above paragraph should be reviewed by a committer (e.g. Sharan, Adrian, Scott) that speaks English as the first language.
>>
>> Jacopo
>>
>
>
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Adrian Crum <ad...@sandglass-software.com>.
+1
I agree the original version sounded a bit negative.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 4/1/2015 2:01 PM, Sharan Foga wrote:
> Hi All
>
> My suggestion would be:
>
> "Despite our best efforts to maintain up to three active release
> branches, support for older branches can decrease because our project
> volunteers may be focussed on other issues. We strongly recommend using
> releases from the most recent branch wherever possible"
>
>
> I think the phrase "because volunteers tend to focus their efforts on
> issues that hold their interest more" could be seen as a bit negative
> (i.e meaning we are not interested enough to fix your problem) which
> isn't the message we want to send.
>
> Also the word "strongly" is optional so you can remove it if you think
> it's a bit too strong - (no pun intended!).
>
> Thanks
> Sharan
>
>
> On 1.4.2015 14:30, Jacopo Cappellato wrote:
>> On Apr 1, 2015, at 2:17 PM, Jacques Le Roux
>> <ja...@les7arts.com> wrote:
>>
>>> Le 01/04/2015 14:15, Jacques Le Roux a écrit :
>>>> So you suggest we say anything?
>>> I meant nothing
>> Yeah.
>> Or, if you really want to add something, I would rather use a text
>> similar to what Adrian and Pierre suggested:
>>
>> "Despite the effort of the community to maintain up to three active
>> release branches, the support for older release branches can decrease
>> - because volunteers tend to focus their efforts on issues that hold
>> their interest more. Whenever possible, we recommend to use the
>> releases from the most recent branch."
>>
>> However even the above paragraph should be reviewed by a committer
>> (e.g. Sharan, Adrian, Scott) that speaks English as the first language.
>>
>> Jacopo
>>
>
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Jacopo Cappellato <ja...@hotwaxsystems.com>.
+1
thank you Sharan.
Jacopo
On Apr 1, 2015, at 3:01 PM, Sharan Foga <sh...@gmail.com> wrote:
> Hi All
>
> My suggestion would be:
>
> "Despite our best efforts to maintain up to three active release branches, support for older branches can decrease because our project volunteers may be focussed on other issues. We strongly recommend using releases from the most recent branch wherever possible"
>
>
> I think the phrase "because volunteers tend to focus their efforts on issues that hold their interest more" could be seen as a bit negative (i.e meaning we are not interested enough to fix your problem) which isn't the message we want to send.
>
> Also the word "strongly" is optional so you can remove it if you think it's a bit too strong - (no pun intended!).
>
> Thanks
> Sharan
>
>
> On 1.4.2015 14:30, Jacopo Cappellato wrote:
>> On Apr 1, 2015, at 2:17 PM, Jacques Le Roux <ja...@les7arts.com> wrote:
>>
>>> Le 01/04/2015 14:15, Jacques Le Roux a écrit :
>>>> So you suggest we say anything?
>>> I meant nothing
>> Yeah.
>> Or, if you really want to add something, I would rather use a text similar to what Adrian and Pierre suggested:
>>
>> "Despite the effort of the community to maintain up to three active release branches, the support for older release branches can decrease - because volunteers tend to focus their efforts on issues that hold their interest more. Whenever possible, we recommend to use the releases from the most recent branch."
>>
>> However even the above paragraph should be reviewed by a committer (e.g. Sharan, Adrian, Scott) that speaks English as the first language.
>>
>> Jacopo
>>
>
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Sharan Foga <sh...@gmail.com>.
Hi All
My suggestion would be:
"Despite our best efforts to maintain up to three active release
branches, support for older branches can decrease because our project
volunteers may be focussed on other issues. We strongly recommend using
releases from the most recent branch wherever possible"
I think the phrase "because volunteers tend to focus their efforts on
issues that hold their interest more" could be seen as a bit negative
(i.e meaning we are not interested enough to fix your problem) which
isn't the message we want to send.
Also the word "strongly" is optional so you can remove it if you think
it's a bit too strong - (no pun intended!).
Thanks
Sharan
On 1.4.2015 14:30, Jacopo Cappellato wrote:
> On Apr 1, 2015, at 2:17 PM, Jacques Le Roux <ja...@les7arts.com> wrote:
>
>> Le 01/04/2015 14:15, Jacques Le Roux a écrit :
>>> So you suggest we say anything?
>> I meant nothing
> Yeah.
> Or, if you really want to add something, I would rather use a text similar to what Adrian and Pierre suggested:
>
> "Despite the effort of the community to maintain up to three active release branches, the support for older release branches can decrease - because volunteers tend to focus their efforts on issues that hold their interest more. Whenever possible, we recommend to use the releases from the most recent branch."
>
> However even the above paragraph should be reviewed by a committer (e.g. Sharan, Adrian, Scott) that speaks English as the first language.
>
> Jacopo
>
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Jacopo Cappellato <ja...@hotwaxsystems.com>.
On Apr 1, 2015, at 2:17 PM, Jacques Le Roux <ja...@les7arts.com> wrote:
> Le 01/04/2015 14:15, Jacques Le Roux a écrit :
>> So you suggest we say anything?
>
> I meant nothing
Yeah.
Or, if you really want to add something, I would rather use a text similar to what Adrian and Pierre suggested:
"Despite the effort of the community to maintain up to three active release branches, the support for older release branches can decrease - because volunteers tend to focus their efforts on issues that hold their interest more. Whenever possible, we recommend to use the releases from the most recent branch."
However even the above paragraph should be reviewed by a committer (e.g. Sharan, Adrian, Scott) that speaks English as the first language.
Jacopo
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Jacques Le Roux <ja...@les7arts.com>.
Le 01/04/2015 14:15, Jacques Le Roux a écrit :
> So you suggest we say anything?
I meant nothing
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Jacques Le Roux <ja...@les7arts.com>.
So you suggest we say anything?
Jacques
Le 01/04/2015 14:09, Scott Gray a écrit :
> It adds unnecessary uncertainty. How do we even know if a particular bug
> exists in older releases? Users can find known unresolved bugs for their
> version in jira.
>
> Regards
> Scott
> On 31 Mar 2015 00:38, "Jacques Le Roux" <ja...@les7arts.com>
> wrote:
>
>> So what would you suggest? To put one more sentence in the download page
>> to explain what you mentioned below?
>>
>> jacques
>>
>> Le 30/03/2015 13:22, Jacopo Cappellato a écrit :
>>
>>> My preference is to have a download the page clean and well written
>>> without links to external wiki, unless really required.
>>>
>>> Jacopo
>>>
>>> On Mar 30, 2015, at 11:42 AM, Jacques Le Roux <
>>> jacques.le.roux@les7arts.com> wrote:
>>>
>>> I propose to use the last sentence I suggested and to add a link to the
>>>> wiki where we explain that, OK?
>>>>
>>>> Jacques
>>>>
>>>> Le 24/03/2015 18:08, Jacopo Cappellato a écrit :
>>>>
>>>>> On Mar 24, 2015, at 2:28 PM, Jacques Le Roux <
>>>>> jacques.le.roux@les7arts.com> wrote:
>>>>>
>>>>> I did not meant to ask our users to backport bug fixes themselves,
>>>>>> only when a bug miss in a release and they need it.
>>>>>>
>>>>> If they need it, and they have the ability to create a backport, then
>>>>> they should be encouraged to file a Jira ticket and provide a patch that
>>>>> our committer can commit to the branch; even if they do not have the
>>>>> ability to provide the patch, they could still file the ticket for the
>>>>> release branch, possibly referring to the revision number (or Jira ticket)
>>>>> where the bug was fixed for the trunk.
>>>>>
>>>>> Jacopo
>>>>>
>>>>>
>>>
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Scott Gray <sc...@hotwaxsystems.com>.
It adds unnecessary uncertainty. How do we even know if a particular bug
exists in older releases? Users can find known unresolved bugs for their
version in jira.
Regards
Scott
On 31 Mar 2015 00:38, "Jacques Le Roux" <ja...@les7arts.com>
wrote:
> So what would you suggest? To put one more sentence in the download page
> to explain what you mentioned below?
>
> jacques
>
> Le 30/03/2015 13:22, Jacopo Cappellato a écrit :
>
>> My preference is to have a download the page clean and well written
>> without links to external wiki, unless really required.
>>
>> Jacopo
>>
>> On Mar 30, 2015, at 11:42 AM, Jacques Le Roux <
>> jacques.le.roux@les7arts.com> wrote:
>>
>> I propose to use the last sentence I suggested and to add a link to the
>>> wiki where we explain that, OK?
>>>
>>> Jacques
>>>
>>> Le 24/03/2015 18:08, Jacopo Cappellato a écrit :
>>>
>>>> On Mar 24, 2015, at 2:28 PM, Jacques Le Roux <
>>>> jacques.le.roux@les7arts.com> wrote:
>>>>
>>>> I did not meant to ask our users to backport bug fixes themselves,
>>>>> only when a bug miss in a release and they need it.
>>>>>
>>>> If they need it, and they have the ability to create a backport, then
>>>> they should be encouraged to file a Jira ticket and provide a patch that
>>>> our committer can commit to the branch; even if they do not have the
>>>> ability to provide the patch, they could still file the ticket for the
>>>> release branch, possibly referring to the revision number (or Jira ticket)
>>>> where the bug was fixed for the trunk.
>>>>
>>>> Jacopo
>>>>
>>>>
>>
>>
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Jacques Le Roux <ja...@les7arts.com>.
So what would you suggest? To put one more sentence in the download page to explain what you mentioned below?
jacques
Le 30/03/2015 13:22, Jacopo Cappellato a écrit :
> My preference is to have a download the page clean and well written without links to external wiki, unless really required.
>
> Jacopo
>
> On Mar 30, 2015, at 11:42 AM, Jacques Le Roux <ja...@les7arts.com> wrote:
>
>> I propose to use the last sentence I suggested and to add a link to the wiki where we explain that, OK?
>>
>> Jacques
>>
>> Le 24/03/2015 18:08, Jacopo Cappellato a écrit :
>>> On Mar 24, 2015, at 2:28 PM, Jacques Le Roux <ja...@les7arts.com> wrote:
>>>
>>>> I did not meant to ask our users to backport bug fixes themselves, only when a bug miss in a release and they need it.
>>> If they need it, and they have the ability to create a backport, then they should be encouraged to file a Jira ticket and provide a patch that our committer can commit to the branch; even if they do not have the ability to provide the patch, they could still file the ticket for the release branch, possibly referring to the revision number (or Jira ticket) where the bug was fixed for the trunk.
>>>
>>> Jacopo
>>>
>
>
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Jacopo Cappellato <ja...@hotwaxsystems.com>.
My preference is to have a download the page clean and well written without links to external wiki, unless really required.
Jacopo
On Mar 30, 2015, at 11:42 AM, Jacques Le Roux <ja...@les7arts.com> wrote:
> I propose to use the last sentence I suggested and to add a link to the wiki where we explain that, OK?
>
> Jacques
>
> Le 24/03/2015 18:08, Jacopo Cappellato a écrit :
>> On Mar 24, 2015, at 2:28 PM, Jacques Le Roux <ja...@les7arts.com> wrote:
>>
>>> I did not meant to ask our users to backport bug fixes themselves, only when a bug miss in a release and they need it.
>> If they need it, and they have the ability to create a backport, then they should be encouraged to file a Jira ticket and provide a patch that our committer can commit to the branch; even if they do not have the ability to provide the patch, they could still file the ticket for the release branch, possibly referring to the revision number (or Jira ticket) where the bug was fixed for the trunk.
>>
>> Jacopo
>>
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Jacques Le Roux <ja...@les7arts.com>.
I propose to use the last sentence I suggested and to add a link to the wiki where we explain that, OK?
Jacques
Le 24/03/2015 18:08, Jacopo Cappellato a écrit :
> On Mar 24, 2015, at 2:28 PM, Jacques Le Roux <ja...@les7arts.com> wrote:
>
>> I did not meant to ask our users to backport bug fixes themselves, only when a bug miss in a release and they need it.
> If they need it, and they have the ability to create a backport, then they should be encouraged to file a Jira ticket and provide a patch that our committer can commit to the branch; even if they do not have the ability to provide the patch, they could still file the ticket for the release branch, possibly referring to the revision number (or Jira ticket) where the bug was fixed for the trunk.
>
> Jacopo
>
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Jacopo Cappellato <ja...@hotwaxsystems.com>.
On Mar 24, 2015, at 2:28 PM, Jacques Le Roux <ja...@les7arts.com> wrote:
> I did not meant to ask our users to backport bug fixes themselves, only when a bug miss in a release and they need it.
If they need it, and they have the ability to create a backport, then they should be encouraged to file a Jira ticket and provide a patch that our committer can commit to the branch; even if they do not have the ability to provide the patch, they could still file the ticket for the release branch, possibly referring to the revision number (or Jira ticket) where the bug was fixed for the trunk.
Jacopo
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Jacques Le Roux <ja...@les7arts.com>.
Jacopo, Adrian,
Why do you see a problem with this sentence there? It seems the best place to inform our users, no? There are more chances to be seen than somewhere
in the wiki.
Maybe I did not write it right because I tried to be brief?
I did not meant to ask our users to backport bug fixes themselves, only when a bug miss in a release and they need it.
Maybe using
<<If ever you miss a bug fix in a release you use, you should always be able to backport it yourself using releases logs
<https://issues.apache.org/jira/browse/OFBIZ/?selectedTab=com.atlassian.jira.jira-projects-plugin:changelog-panel> or commits logs.
<http://svn.apache.org/viewvc/ofbiz/> >>
instead of
<<But using releases logs <https://issues.apache.org/jira/browse/OFBIZ/?selectedTab=com.atlassian.jira.jira-projects-plugin:changelog-panel> or
commits logs <http://svn.apache.org/viewvc/ofbiz/>you should always be able to backport yourself. >>
would be better?
Jacques
Le 24/03/2015 11:46, Adrian Crum a écrit :
> I agree. Something like that belongs on the wiki.
>
> Adrian Crum
> Sandglass Software
> www.sandglass-software.com
>
> On 3/24/2015 10:41 AM, Jacopo Cappellato wrote:
>> 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?
>>
>> Jacopo
>>
>> On Mar 24, 2015, at 11:18 AM, jleroux@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>
>>>
>>>
>>
>
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Adrian Crum <ad...@sandglass-software.com>.
I agree. Something like that belongs on the wiki.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 3/24/2015 10:41 AM, Jacopo Cappellato wrote:
> 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?
>
> Jacopo
>
> On Mar 24, 2015, at 11:18 AM, jleroux@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>
>>
>>
>
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Pierre Smits <pi...@gmail.com>.
'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 <pi...@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.roux@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, jleroux@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>
>>>>
>>>>
>>>>
>>>
>>>
>
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Pierre Smits <pi...@gmail.com>.
+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.roux@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, jleroux@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>
>>>
>>>
>>>
>>
>>
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Pierre Smits <pi...@gmail.com>.
My advise is somewhat similar: 'Once a release branch is created, support
for older releases can decrease - because volunteers tend to focus their
efforts on issues that hold their interest more.'
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:38 PM, Adrian Crum <
adrian.crum@sandglass-software.com> wrote:
> I usually give my clients this advice:
>
> "Once a release branch is created, support for previous releases decreases
> - because volunteers tend to focus their efforts on more recent releases."
>
> Maybe that will help.
>
> Adrian Crum
> Sandglass Software
> www.sandglass-software.com
>
> On 3/24/2015 11:33 AM, Jacques Le Roux 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, jleroux@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>
>>>>
>>>>
>>>>
>>>
>>>
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Adrian Crum <ad...@sandglass-software.com>.
I usually give my clients this advice:
"Once a release branch is created, support for previous releases
decreases - because volunteers tend to focus their efforts on more
recent releases."
Maybe that will help.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 3/24/2015 11:33 AM, Jacques Le Roux 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, jleroux@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>
>>>
>>>
>>
>>
Re: svn commit: r1668834 - /ofbiz/site/download.html
Posted by Jacques Le Roux <ja...@les7arts.com>.
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, jleroux@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>
>>
>>
>
>