For me it is ok, we miss nothing. But I have no right yet to decide ;-)
On 15.02.2014 13:44, Cristiano Costantini wrote:
Anyhow, for me in the end it is the same,
What is it missing now to start?
Should we make a vote about migration to git?
Il sabato 15 febbraio 2014, Krzysztof Sobkowiak <[email protected]>
ha scritto:
I'm not sure if we should change the version to 4.9.0-SNAPSHOT but it
would be an option for the solution proposed by Jean-Baptiste: 4.9.x with
Karaf 2.3.x and 5.x with Karaf 3.x instead of 5.x with Karaf 2.3.x and 6.x
with Karaf 3.x. The both ideas have advantages and disadvantages. I think
here starts again a discussion about semantic versioning.
I don't think we should create a new repository for ServiceMix. I propose
to rename the current servicemix5 repository in servicemix or
servicemix-assembly and make a branch for ServiceMix 5 (or 4.9 as proposed
by Cristiano). The development of ServiceMix 6 (or 5 as proposed by
Cristiano) could start in master branch - 1 repository, 1 branch for the
major release (like in Karaf)
We could eventually fully migrate to git development (without svn like
Karaf) with this repository.
Regards
Krzysztof
On 15.02.2014 12:02, Cristiano Costantini wrote:
I try to summarize. If I'm wrong pleas correct me.
Good summary and I agree with you.
It's true that a ServiceMix based on Karaf 3.0.0 may need some more
testing, so it would be good to release a new ServiceMix based on Karaf
2.3.3 asap, but already without NMR and JBI.
The plan (at least one of the possible scenarios) for the Karaf 3.x line
of SMX was to completely remove the code base of SMX and start again
with a
new custom Karaf 3.x distribution which only assembles the Camel,
ActiveMQ, CXF features
I think we should do that: let's create a new repository (move to GIT?)
and
start assembling the new ServiceMix based on Karaf 3.0.
Because SMX 5 is almost stable, it would be wrong idea to remove its code
base and start SMX5 from the scratch.
My proposal is to change the version to 4.9.0-SNAPSHOT (so it address
also
concerns like those of Raul about the minor/major versions upgrade) then
remove the other dependencies from it leaving it to be only a Karaf 2.3.3
plus Camel, CXF and AcvtiveMQ, and release it as soon as possible.
the jump in version from 4.5.x to 4.9.x should alert user that it is a
transitory release that lead to ServiceMix 5.0 that it is Karaf 3.0.0
based.
My 2 cents :-)
Cristiano
--
Krzysztof Sobkowiak
JEE & OSS Architect | Technical Architect @ Capgemini
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center <
http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: [email protected] <mailto:[email protected]> |
Twitter: @KSobkowiak
--
Krzysztof Sobkowiak
JEE & OSS Architect | Technical Architect @ Capgemini
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: [email protected] <mailto:[email protected]> |
Twitter: @KSobkowiak
