Re: [DISCUSS] Camel release cycle

[Willem Jiang <wi...@gmail.com>]

Current we just do the 1.6.x release on 1.x branch, I think it's fine 
for us. If we are moving to Camel 3.0 after camel 2.6.0, we can do the 
same thing for the camel 2.6.x release.

FYI, Freeman Fixed the issue on the ServiceMix side[1], we don't need do 
Camel 2.5.1 release any more.

[1]https://issues.apache.org/jira/browse/SMX4-711

On 12/16/10 2:33 AM, Hadrian Zbarcea wrote:
> Hi Willem,
>
> Personally I am in favor it and I could start the release builds immediately. However:
> 1. There is no camel-2.5.1 branch so one would have to be created. We could create a camel-2.5 branch off of the 2.5.0 tag.
> 2. There is no precedent for having patch releases in Camel (3rd digit). It doesn't mean we cannot start it (I would like that actually) but we need to discuss it and agree on something
> 3. If we do that it would make sense to have more formal support cycle for a version. Camel imho got a maturity level that almost requires it.
>
> My preference would be a 6 weeks release cycle, meaning 2 releases per quarter. Patch releases should be 100% backwards compatible (including dsl), no version upgrades for dependencies and should only include bug fixes. Minor releases (2nd digit) could bring new features, components, dependency upgrades (as we do it now). Major releases will be rare, but 3.0 is coming up.
>
> Thoughts/ideas/preferences?
> Hadrian
>
> On Dec 15, 2010, at 9:30 AM, Willem Jiang wrote:
>
>> Hi,
>>
>> I just found some issues[1][2] of camel-cxf in Camel 2.5.0 which cause the camel-nmr component tests[3] failed. I didn't find a way to work round the camel issues without changing the code camel.
>>
>> As you know ServiceMix 4.3.0 releasing is on the way, if we let ServiceMix pick up the latest Camel 2.6.0, there will be not just waiting for the Camel 2.6.0 release issue. ServiceMix also need to upgrade it's CXF version to 2.3.x and prepare the bunch of new JAXWS, JAXRS bundle release.
>>
>> Now I propose to do Camel 2.5.1 release myself by merging the upper camel fix into 2.5 branch, In this way, we can fix the camel-nmr issue without blocking the ServiceMix 4.3.0 release.
>>
>> Any thoughts ?
>>
>> [1]https://issues.apache.org/jira/browse/CAMEL-3426
>> [2]https://issues.apache.org/jira/browse/CAMEL-3431
>> [3]https://issues.apache.org/jira/browse/SMX4-707
>>
>> --
>> Willem
>> ----------------------------------
>> FuseSource
>> Web: http://www.fusesource.com
>> Blog:    http://willemjiang.blogspot.com (English)
>>          http://jnn.javaeye.com (Chinese)
>> Twitter: willemjiang
>
>


-- 
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog:    http://willemjiang.blogspot.com (English)
          http://jnn.javaeye.com (Chinese)
Twitter: willemjiang