+1

streamline and increase the frequency of releases sound good for me

Regards

--Filippo

2013/2/4 Jean-Baptiste Onofré <[email protected]>:
> +1
>
> It sounds like a good plan, and provide a good message to the community.
>
> Regards
> JB
>
>
> On 02/03/2013 09:54 PM, Gert Vanthienen wrote:
>>
>> L.S.,
>>
>>
>> About a year and a half ago, we had some discussions on the mailing list
>> about a plan for Apache ServiceMix 5.0 and had some initial commits to
>> build the additional services and functionality.  Since then however, none
>> of us have actually had the time to work on that code or move things
>> forward.
>>
>> In the meanwhile, we are also struggling constantly to get our releases
>> done in timely fashion.  The latest 4.5.0 release took almost 9 months
>> since the first mention of it on the dev@ list.  Doing a ServiceMix
>> release
>> now is quite a task: it usually involves doing releases in 5 or 6
>> subprojects.
>>
>> I would like to propose a new plan for Apache ServiceMix 5.0.  Instead of
>> doing a lot of new development, how about we start with the current 4.x
>> features codebase and remove everything that's related to JBI and the NMR.
>>   That will give us a nice and simple integration container build (based
>> on
>> Karaf, Camel, CXF, ActiveMQ, ...) and everything is living in a single
>> project that's quick and easy to release.
>>
>> If we start doing this now, we could get a build out with Karaf 2.3.0,
>> ActiveMQ 5.8.0, Camel 2.11.0 (which will bring in Scala 2.10 and opens up
>> the possibility to include the Akka OSGi examples I built a few months
>> ago)
>> pretty soon after those versions are available.   With only one project to
>> maintain the versions of all those dependencies, we should be able to
>> follow up more regularly as our sibling projects do (new) fix releases as
>> well.
>>
>> We don't have to throw away the existing ServiceMix 5.0 code by the way,
>> we
>> can always move that into a separate branch and then cherry-pick the
>> useful
>> bits afterwards, but I think our first goal now should be to get ourselves
>> in a position that we can actually build and release stuff more easily
>> again.
>>
>>
>> Wdyt?
>>
>> Gert Vanthienen
>>
>
> --
> Jean-Baptiste Onofré
> [email protected]
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Reply via email to