camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hadrian Zbarcea <hzbar...@gmail.com>
Subject Re: [Camel 3 discussion] Components releases
Date Tue, 19 Feb 2013 22:59:31 GMT
Except this is not a vote and hence not a veto :).
Claus expressed that his views are different, no biggie.

Cheers,
Hadrian

On 02/19/2013 02:51 PM, James Carman wrote:
> A veto must be accompanied by a justification in order for it to stand:
>
> http://www.apache.org/foundation/voting.html
>
> On Feb 19, 2013, at 1:13 PM, Claus Ibsen <claus.ibsen@gmail.com> wrote:
>
>> I am -1 on this.
>>
>> On Tue, Feb 19, 2013 at 8:16 AM, Henryk Konsek <hekonsek@gmail.com> wrote:
>>> Hi,
>>>
>>> Unfortunately I won't be able to join the IRC session today as I need
>>> to hire myself as a babysitter this evening. However I would like to
>>> discuss some subject that come up recently [1]. One on the issues
>>> discussed during the previous IRC session was the question whether is
>>> it possible to release components more frequently than core.
>>>
>>> I was wondering if we could introduce additional versioning for the
>>> components based on the Maven version qualifiers [2] starting from
>>> Camel 3. Qualifiers are fully supported by Maven. Versions comparison
>>> and ranges work with qualifiers as well [3]. As far as I googled
>>> Release Plugin can handle them correctly too (as well as
>>> submodule-only release).
>>>
>>> The versioning of the core would stay the same. Whenever we release
>>> core, we release all the components as well - this doesn't change as
>>> we want to guarantee the users that we have tested all components
>>> against the latest core. However we could change the versioning of the
>>> components to be qualified as follows - camel-cxf-3.0.0-CR-01 (where
>>> CR qualifier stands for "Component Release").
>>>
>>> What camel-cxf-3.0.0-CR-03 version would state is - this is the 3rd
>>> version of the CXF component tested against the Camel 3.0.0 core.
>>>
>>> This approach will require us to decouple "components" module from the
>>> core the same was as camel-extra is. To be exact components should be
>>> dependent on the release version of camel-core instead of SNAPSHOT.
>>> And we should perform core release separately before the components
>>> release.
>>>
>>> I have never worked with qualified releases so I'm not sure if this
>>> approach won't be the release hell, but I think we could consider this
>>> option as Maven offers qualifiers out of the box. This may be a nice
>>> option to reduce time needed to deliver the latest artifacts to the
>>> end users.
>>>
>>> What do you think?
>>>
>>> Best regards.
>>>
>>> [1] http://camel.465427.n5.nabble.com/DISCUSS-CAMEL-3-0-weekly-IRC-chat-at-02-12-2013-7-00PM-8-00PM-CET-td5727462.html
>>> [2] http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-pom-syntax.html
>>> [3] http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution
>>>
>>> --
>>> Henryk Konsek
>>> http://henryk-konsek.blogspot.com
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: cibsen@redhat.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>
>

Mime
View raw message