Doing a few 6.0.0 early access releases?

[Gert Vanthienen]

L.S.,


With a release plan for the next few 5.x releases in the works, the
only remaining question would be about the ServiceMix 6.0.0 release.

That release represents a major change for most of our users, with the
Karaf 3 upgrade. Perhaps we should start with one or two (unstable)
milestone releases (e.g based on the latest Karaf 3.0.1) to get our
users (and ourselves) familiarized with the technology before calling
it the official 6.0.0? Something like 6.0.0.RC1 or 6.0.0.EA1 perhaps?

Even though there are known issues with it, just having a milestone
out might encourage more people to play with it and give us more
feedback to work with. Also, it would give us something to start
working with for updating the documentation for that release.


Regards,

Gert Vanthienen

[Krzysztof Sobkowiak]

Hi Gert

+1
I think this is a good idea to make a release candidate with Karaf
3.0.1. The biggest problem with ServiceMix with Karaf 3.0.1 is the
problem with hot deployment of routes containing activemq endpoints.

I have tested the upgrade to Karaf 3.0.2-SNAPSHOT and it looks
promising. There is still one problem to solve, described here
https://issues.apache.org/jira/browse/SM-2321?focusedCommentId=14062669&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14062669

Best regards
Krzysztof

Post by Gert Vanthienen
L.S.,
With a release plan for the next few 5.x releases in the works, the
only remaining question would be about the ServiceMix 6.0.0 release.
That release represents a major change for most of our users, with the
Karaf 3 upgrade. Perhaps we should start with one or two (unstable)
milestone releases (e.g based on the latest Karaf 3.0.1) to get our
users (and ourselves) familiarized with the technology before calling
it the official 6.0.0? Something like 6.0.0.RC1 or 6.0.0.EA1 perhaps?
Even though there are known issues with it, just having a milestone
out might encourage more people to play with it and give us more
feedback to work with. Also, it would give us something to start
working with for updating the documentation for that release.
Regards,
Gert Vanthienen

--
Krzysztof Sobkowiak

JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
@ ASF
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: krzys.sobkowiak-***@public.gmane.org <mailto:krzys.sobkowiak-***@public.gmane.org> |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC

[Krzysztof Sobkowiak]

Hi Gert

We should probably revert the commit
http://git-wip-us.apache.org/repos/asf/servicemix/commit/a041239b in
master and make the pre-release from this version. Some next fixes need
upgrade to Karaf 3.0.2[-SNAPSHOT] and must wait until the pre-release is
ready.

Best regards
Krzysztof

Post by Krzysztof Sobkowiak
Hi Gert
+1
I think this is a good idea to make a release candidate with Karaf
3.0.1. The biggest problem with ServiceMix with Karaf 3.0.1 is the
problem with hot deployment of routes containing activemq endpoints.
I have tested the upgrade to Karaf 3.0.2-SNAPSHOT and it looks
promising. There is still one problem to solve, described here
https://issues.apache.org/jira/browse/SM-2321?focusedCommentId=14062669&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14062669
Best regards
Krzysztof

Post by Gert Vanthienen
L.S.,
With a release plan for the next few 5.x releases in the works, the
only remaining question would be about the ServiceMix 6.0.0 release.
That release represents a major change for most of our users, with the
Karaf 3 upgrade. Perhaps we should start with one or two (unstable)
milestone releases (e.g based on the latest Karaf 3.0.1) to get our
users (and ourselves) familiarized with the technology before calling
it the official 6.0.0? Something like 6.0.0.RC1 or 6.0.0.EA1 perhaps?
Even though there are known issues with it, just having a milestone
out might encourage more people to play with it and give us more
feedback to work with. Also, it would give us something to start
working with for updating the documentation for that release.
Regards,
Gert Vanthienen

--
Krzysztof Sobkowiak
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
Calendar: http://goo.gl/yvsebC

--
Krzysztof Sobkowiak

JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
@ ASF
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: krzys.sobkowiak-***@public.gmane.org <mailto:krzys.sobkowiak-***@public.gmane.org> |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC

[Gert Vanthienen]

Hi Krzysztof,

Yes, it probably makes sense to go back to the latest 3.0.x release
and get a ServiceMix release out with that change and then go back to
the latest SNAPSHOT again afterwards.

Regards,

Gert Vanthienen


On Thu, Jul 31, 2014 at 9:30 AM, Krzysztof Sobkowiak

Post by Krzysztof Sobkowiak
Hi Gert
We should probably revert the commit
http://git-wip-us.apache.org/repos/asf/servicemix/commit/a041239b in
master and make the pre-release from this version. Some next fixes need
upgrade to Karaf 3.0.2[-SNAPSHOT] and must wait until the pre-release is
ready.
Best regards
Krzysztof

Post by Krzysztof Sobkowiak
Hi Gert
+1
I think this is a good idea to make a release candidate with Karaf
3.0.1. The biggest problem with ServiceMix with Karaf 3.0.1 is the
problem with hot deployment of routes containing activemq endpoints.
I have tested the upgrade to Karaf 3.0.2-SNAPSHOT and it looks
promising. There is still one problem to solve, described here
https://issues.apache.org/jira/browse/SM-2321?focusedCommentId=14062669&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14062669
Best regards
Krzysztof

Post by Gert Vanthienen
L.S.,
With a release plan for the next few 5.x releases in the works, the
only remaining question would be about the ServiceMix 6.0.0 release.
That release represents a major change for most of our users, with the
Karaf 3 upgrade. Perhaps we should start with one or two (unstable)
milestone releases (e.g based on the latest Karaf 3.0.1) to get our
users (and ourselves) familiarized with the technology before calling
it the official 6.0.0? Something like 6.0.0.RC1 or 6.0.0.EA1 perhaps?
Even though there are known issues with it, just having a milestone
out might encourage more people to play with it and give us more
feedback to work with. Also, it would give us something to start
working with for updating the documentation for that release.
Regards,
Gert Vanthienen

--
Krzysztof Sobkowiak
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
Calendar: http://goo.gl/yvsebC

--
Krzysztof Sobkowiak
@ ASF
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
Calendar: http://goo.gl/yvsebC