As someone who has a great interest in OfBiz but has unfortunately not
much involvement might I suggest that there maybe be a slight
misunderstanding here.  My understanding was that OfBiz was following a
fairly typical release management strategy.

At some point a Release Branch is created from Trunk (when it's deemed
enough new functionality exists).
This Release Branch is just that a branch... it changes as patches are
applied throughout its life.

But a Release, such as 9.04 for example, is an instance in time of the
Release Branch. A tagged release as they say.

While the Release Branch is not "static", no new functionality is added
just bug fixes.  Now today, it will be an improvement over the tagged
9.04, but unlike trunk it gets more an more "stable" as time goes by as
only patches are applied. I suspect some people are equating static with
stable?

Trunk you would expect to be equally as (un)stable from one moment to
the next... bugs are fixed but equally new functionality and so bugs are
created.

I would think to implement with least problems;
* if you only know how to implement binary (unlikely I think with
something like ofbiz) then implement the binary 9.04,
* if you can compile then implement the latest version of the Release
branch.
* if you are a guru, who can handle the additional "risk" and want the
latest and greatest implement trunk.



With Kind Regards,


Colin Rooney
________________________
mobile: +353 86 046 5976
skype: colin.rooney
web: www.openbiz.ie


Ruth Hoffman wrote:
> Doesn't this contradict previous statements or non-statements about bug
> fixes in Release 9.04?
> Regards,
> Ruth
> 
> David E Jones wrote:
>> One quick thing to note, that seems to be confused here: the release
>> branch is a tool for stabilization. It's great to do testing and
>> fixing in the trunk, but the goal for a release branch is not to be
>> tested and bug-free from day one, but rather to be stable so that real
>> testing and bug fixing can be done in the release branch without
>> worrying about new things possibly breaking something, or any other
>> conflicting priorities.
>>
>> -David
>>
>>
>> On Feb 23, 2010, at 1:22 PM, Anil Patel wrote:
>>
>>  
>>> Makes sense to me. If we are decided on date, we still have a month
>>> to go. Gives plenty of time, may be :)
>>>
>>> Thanks and Regards
>>> Anil Patel
>>> HotWax Media Inc
>>> Find us on the web at www.hotwaxmedia.com or Google Keyword "ofbiz"
>>>
>>> On Feb 23, 2010, at 10:40 AM, Adrian Crum wrote:
>>>
>>>    
>>>> It would be nice to get the new security code included in the branch
>>>> - even if it is disabled. That will give release users an
>>>> introduction to it and give them a chance to work on an upgrade
>>>> strategy.
>>>>
>>>> -Adrian
>>>>
>>>> Anil Patel wrote:
>>>>      
>>>>> So, are we set for next Ofbiz Branch named 10.04 ?
>>>>> If we decide on _date_, I can have a team of developers scheduled
>>>>> to start testing branch code. This will allow to quickly stabilize
>>>>> ofbiz release for common ecommerce use.
>>>>> How about EOD March 31st 10 GMT?
>>>>> Thanks and Regards
>>>>> Anil Patel
>>>>> HotWax Media Inc
>>>>> Find us on the web at www.hotwaxmedia.com or Google Keyword "ofbiz"
>>>>> On Feb 15, 2010, at 6:40 AM, Jacques Le Roux wrote:
>>>>>        
>>>>>> I agree but after Jacopo's message on dev ML about new release
>>>>>> strategy (on which I mostly agree) I will at least delay it...
>>>>>>
>>>>>> Jacques
>>>>>>
>>>>>> From: "Bruno Busco" <bruno.bu...@gmail.com>
>>>>>>          
>>>>>>> In order to have this kind of issue scheduling could you please
>>>>>>> create
>>>>>>> a new OFBIZ version in jira and set the Fix Version of these
>>>>>>> issue on
>>>>>>> that?
>>>>>>> I do not see any clearer way to answer to Ashish question.
>>>>>>>
>>>>>>> -Bruno
>>>>>>>
>>>>>>> 2010/2/15 Jacques Le Roux <jacques.le.r...@les7arts.com>:
>>>>>>>            
>>>>>>>> I expect to fulfill
>>>>>>>> https://issues.apache.org/jira/browse/OFBIZ-3442
>>>>>>>> and maybe
>>>>>>>> https://issues.apache.org/jira/browse/OFBIZ-3445
>>>>>>>>
>>>>>>>> In other word to use layer lookups instead of popup lookups
>>>>>>>> everywhere it's
>>>>>>>> possible in OFBiz.
>>>>>>>> From my 1st serie of tests it seems to work well almost
>>>>>>>> everywhere, WIP...
>>>>>>>>
>>>>>>>> Jacques
>>>>>>>>
>>>>>>>> From: "Ashish Vijaywargiya" <vijaywargiya.ash...@gmail.com>
>>>>>>>>              
>>>>>>>>> I think its time to start thinking on the things that should be
>>>>>>>>> taken
>>>>>>>>> care in / before release branch 10.04.
>>>>>>>>>
>>>>>>>>> Bug fixing should be the major area which should be taken care
>>>>>>>>> extensively in next two months.
>>>>>>>>> What about new features etc. etc.?
>>>>>>>>>
>>>>>>>>> Please comment.
>>>>>>>>> Thanks!
>>>>>>>>>
>>>>>>>>> -- 
>>>>>>>>> Ashish
>>>>>>>>>
>>>>>>>>> On Tue, Dec 15, 2009 at 6:47 AM, David E Jones <d...@me.com>
>>>>>>>>> wrote:
>>>>>>>>>                
>>>>>>>>>> There is no set date yet. The last release was in April 2009
>>>>>>>>>> (hence the
>>>>>>>>>> version number of 09.04 on it), and the one before that was
>>>>>>>>>> about 2 years
>>>>>>>>>> before. Chances are it won't be another 2 years before another
>>>>>>>>>> release, but
>>>>>>>>>> probably at least a year... so perhaps we'll do another
>>>>>>>>>> release branch in
>>>>>>>>>> around 4 months.
>>>>>>>>>>
>>>>>>>>>> -David
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Dec 14, 2009, at 3:37 PM, Juan Pablo wrote:
>>>>>>>>>>
>>>>>>>>>>                  
>>>>>>>>>>> Hello Community.
>>>>>>>>>>>
>>>>>>>>>>> I'm testing the last trunk version and the demo version
>>>>>>>>>>> published in
>>>>>>>>>>> Internet (http://demo.ofbiz.org). They've got new
>>>>>>>>>>> functionality: help on
>>>>>>>>>>> line, new themes, new features in accounting, manufacturing
>>>>>>>>>>> and ordermgr
>>>>>>>>>>> components. The last stable versión is actually 9.04. So,
>>>>>>>>>>> ¿When will
>>>>>>>>>>> Ofbiz
>>>>>>>>>>> try a new stable release version?.
>>>>>>>>>>>
>>>>>>>>>>> Gracias/Thank You.
>>>>>>>>>>>
>>>>>>>>>>> -- 
>>>>>>>>>>> Juan Pablo
>>>>>>>>>>>                     
>>>>>>>>               
>>
>>
>>   
> 

Reply via email to