Re: OFBIZ-3100 patches

[Adrian Crum]

Thank you for the update. I will have time this weekend to review and
commit the patches.

-Adrian

Marc Morin wrote:

> Adrian,
>
> I have put patches for many of the framework areas, most notably, framework/entity has NOT been done yet.  It is more "difficult" and will tackle that tonight.
>
> Maybe mark yourself interested in the OFBIZ-3100 and sub-tasks so you can get automatically notified of activity on this issue.
>
> Marc Morin
> Emforium Group Inc.
> ALL-IN Software™
> 519-772-6824 ext 201
> [hidden email]
>
>
>

[Adam Heath-2]

Adrian Crum wrote:
> Thank you for the update. I will have time this weekend to review and
> commit the patches.

Actually, be *VERY* careful with these things.  If you apply them now,
making backports from trunk to any previous release will become much
more difficult.

I would say to hold off on these, until trunk is closer to being released.

[Adrian Crum]

That's a good point, but at the same time, is it prudent to stop
development on the trunk just because it might interfere with a prior
release?

I will wait to hear from others.

-Adrian

Adam Heath wrote:

> Adrian Crum wrote:
>> Thank you for the update. I will have time this weekend to review and
>> commit the patches.
>
> Actually, be *VERY* careful with these things.  If you apply them now,
> making backports from trunk to any previous release will become much
> more difficult.
>
> I would say to hold off on these, until trunk is closer to being released.
>
>

[Tim Ruppert]

Agreed - let's keep moving the trunk forward.

Cheers,
Ruppert

On Oct 29, 2009, at 4:30 PM, Adrian Crum wrote:

> That's a good point, but at the same time, is it prudent to stop  
> development on the trunk just because it might interfere with a  
> prior release?
>
> I will wait to hear from others.
>
> -Adrian
>
> Adam Heath wrote:
>> Adrian Crum wrote:
>>> Thank you for the update. I will have time this weekend to review  
>>> and
>>> commit the patches.
>> Actually, be *VERY* careful with these things.  If you apply them  
>> now,
>> making backports from trunk to any previous release will become much
>> more difficult.
>> I would say to hold off on these, until trunk is closer to being  
>> released.

[David E. Jones-2]

I agree too with Adrian and Tim. All changes affect backporting  
changes. Some more than others for sure... but maybe if we're lucky  
some of these changes will get back into the release branch(es) along  
with a bug fix later on.

About the next release... we're about six months past our last release  
branch. If we do one in another 2 years we're 18 months away from the  
next release. If we shorten that to 1 year between release branches  
we're still 6 months away from the next one.

-David


On Oct 29, 2009, at 4:36 PM, Tim Ruppert wrote:

> Agreed - let's keep moving the trunk forward.
>
> Cheers,
> Ruppert
>
> On Oct 29, 2009, at 4:30 PM, Adrian Crum wrote:
>
>> That's a good point, but at the same time, is it prudent to stop  
>> development on the trunk just because it might interfere with a  
>> prior release?
>>
>> I will wait to hear from others.
>>
>> -Adrian
>>
>> Adam Heath wrote:
>>> Adrian Crum wrote:
>>>> Thank you for the update. I will have time this weekend to review  
>>>> and
>>>> commit the patches.
>>> Actually, be *VERY* careful with these things.  If you apply them  
>>> now,
>>> making backports from trunk to any previous release will become much
>>> more difficult.
>>> I would say to hold off on these, until trunk is closer to being  
>>> released.
>