For companies adopting an ERP, this is a big decision and the Apache name generates certain expectations.

I think that writing up an honest statement about what the PMC defines as a "stable release" would be helpful. It should describe the EOL condition/date and what the commitment is to fixing bugs in the "current stable release".
If 12.x.x is no longer supported, the PMC should say so.

If 11.x.x is no longer going to be maintained, that should be clearly stated as well.

If only certain types of bugs are going to be fixed, this should be stated.

If 13.07.x is actually the "Current Stable Release", this should be stated and the release finished. I am not sure what the customer reaction will be for a product that defines EOL of one release to be the day when the next major version is release.
One month prior to the release date is clearly not acceptable for an ERP.

The PMC has to make some management decisions that it believes in and can defend as reasonable for a project of this type and that it can live up to.


Ron



On 20/09/2014 1:23 PM, Jacques Le Roux wrote:
I understand your point of view and I even tend to agree with.

For the moment I still personally try to backport on all maintained branches (those having releases pending). Most of the time it's straightforward, but I got bitten once or two by wrong backports which created new bugs that I had to fix.

Still, though it's better now with Jira changes logs reports, the problem is not everybody is aware of bug fixes backported or not. The official download page http://ofbiz.apache.org/download.html, says that we stabilize releases with bug fixes. It's not quite clear if we are backporting all or only some bug fixes.

I wonder if we should not face the reality. Even during large efforts like HWM Bugs Crush, we don't/can't backport all bug fixes. I think we should make that clear and expose a way to users for them to more "easily" maintain the releases they use. I feel that with the help of the Jira changes logs reports (thanks Jacopo) this should be possible. I don't think at an automated way, just a process for users to follow.

Jacques

Le 20/09/2014 18:47, Adrian Crum a écrit :
I don't have time to maintain 4 code bases (trunk + 3 branches). I will fix things in the trunk, and I will backport those fixes to the most recent branch. I have no interest in older branches. If someone else is using them, then they can create a patch for them. So, I have no issues with releasing old branches with missing fixes - because if anyone really cared about them they would work harder to maintain them.

Adrian Crum
Sandglass Software
www.sandglass-software.com

On 9/20/2014 5:29 PM, Jacques Le Roux wrote:
It seems a bit weird to me to officially release code with bugs when we
have already bug fixes in trunk

Jacques

Le 20/09/2014 17:17, Adrian Crum a écrit :
From my perspective, anyone wanting to use older versions can backport
the changes themselves - either locally, or in the release branches by
providing a patch.

Adrian Crum
Sandglass Software
www.sandglass-software.com

On 9/20/2014 4:07 PM, Ashish Vijaywargiya wrote:
Hello Jacques,

Thanks for your kind words. We started this event considering the fact to provide fixes for trunk and latest release branch which is 13.07. It will be of great help if someone from community could pick and back port the required changes to Release Branch 12.04. In future if we get time
we will also be taking care of back porting to R12.04.

We didn't back port changes in R11.04 just because it is very old branch
and very soon will not be maintained. Thanks.

--
Kind Regards
Ashish Vijaywargiya
HotWax Media - est. 1997
ApacheCon US 2014 Silver Sponsor
http://na.apachecon.com/sponsor/our-sponsors

On Saturday 20 September 2014 05:01 PM, Jacques Le Roux wrote:

Le 20/09/2014 13:28, Jacques Le Roux a écrit :
Hi,

It's great to see a second Bug Crush effort!

I have though a question, I see that you (HotWax Media team) only
backport bug fixes to the R13 branch.
I guess it's intended, so why?
I ask this because I already found myself trying to fix issues in R12
and R11 branches (I know will be soon no longer maintained R11 ) and
found they were already backported in R13
Jacques










--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102

Reply via email to