+1, Agree with Chris and Edell on waiting till 4.0 release.
-- Ulhas
Edell Nolan wrote:
+1 - I would wait for 4.0 as Chris mentioned as we will have all the
components released together and will be easier to track from that and they
will all be releeased with Spring DM 1.2.0
On Fri, Feb 13, 2009 at 1:42 PM, jgoodyear <[email protected]> wrote:
+1
Gert Vanthienen wrote:
L.S.,
A while back, we separated the components into a separate build so they
could be shared between ServiceMix 3 and ServiceMix 4, but we also made
every component a Maven project on its own to allow them to be released
independently. Up to now, we didn't really leverage all the hard work
that was done to make this happen, but we might have a good opportunity
to start the habit now:
- Camel 1.6.0 is being voted and we don't even have a Camel 1.5.0
component in Servicemix, so we could do with a release of
servicemix-camel
- I guess the same also goes for CXF, we should be able to release a new
CXF component whenever CXF itself is released
On the other hand, I think we are also waiting for a Spring DM 1.2.0
release to get a full set of components released again, so it might be
better to just wait a little while and do a full component release once
more before we start our new best habit.
Once again: thought? suggestions?
Regards,
Gert
-----
---
Gert Vanthienen
http://gertvanthienen.blogspot.com
-----
Jamie Goodyear
------------------------
Blog: http://icodebythesea.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
--
View this message in context:
http://www.nabble.com/-DISCUSS--Release-frequency-for-components-tp21981581p21996547.html
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
