+1 I think we should do an update release of all components around the same time we do the 4.0 release, and then do individual releases after that. I think it is going to be important to document and track the components slightly differently than we do now so that releases are as easy as possible. I think you are covering that in a different thread so I will respond to that as well.
Chris -- Chris Custine My Blog :: http://blog.organicelement.com Apache ServiceMix :: http://servicemix.apache.org Apache Directory Server :: http://directory.apache.org On Thu, Feb 12, 2009 at 11:07 AM, Gert Vanthienen <[email protected] > 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 >
