You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Scott Gray <sc...@hotwaxsystems.com> on 2015/04/01 14:09:16 UTC

Re: svn commit: r1668834 - /ofbiz/site/download.html

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>.
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
>>>>>
>>>>>
>>>