Ok, we can also postpone it to point when we start ServiceMix 6
somewhere in the future (assumed ServiceMix 5 as Karaf 3 line). I have
proposed it now, because I think there are not too many developers
working on servicemix5 repository now and it should have less side
effects now.
On 16.02.2014 16:35, Cristiano Costantini wrote:
I'm ok with this name change as long as it has no side effects with the
developments.
Else, I think it is acceptable to have a servicemix 4.9 developed under a
repository named servicemix 5; consider it as when you start a new project
and you give it the version 0.0.1-SNAPSHOT with the meaning of a "version
that is not yet 1.0.0"
Il domenica 16 febbraio 2014, Krzysztof Sobkowiak <[email protected]>
ha scritto:
Hi all
Apart from the result of the vote about releasing ServiceMix based on Karf
3.x or not, I'd like to propose to rename the current repository
servicemix5 to servicemix, as this repository should contain next
ServiceMix releases (we can move the current code base in a new branch
servicemix-4.9.x and start the new codebase for ServiceMix 5 on trunk). It
means we should also rename the git repository in Apache and Github.
Regards
Krzysztof
--
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
