Jean-Baptiste, How about doing a big, bulky 4.1 release this week with components + nmr + features in it and then follow up with a servicemix 3.3.2 release next week, reusing the same component set? That way, we can announce a new release both weeks ;)
Regards, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ 2009/12/14 Jean-Baptiste Onofre <[email protected]>: > Hi gentlemen, > > Yesterday I have upgraded SMX resources (component, feature, etc) to use > Apache Camel 2.1 as it has been released. > > I think that we are not so far from a new SMX 3.3.2 and 4.1 release. > > I propose the following steps: > > 1/ I begin to prepare the 2009.02 components release. It includes: > - component-pom 4 > - jbi-maven-plugin 4.2 > These artifacts will be submit to a first vote. > - all components 2009.02 > All components artifacts will be submit to a second vote. > > 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly using > Karaf 1.2.0 and perform some test to check how it runs. > > 2/ once these steps 1 and 1 bis have been performed, we can upgrade the smx > 3 and smx 4 POMs to use the previously released components. > Two votes will be submitted: one for SMX3 and another one for SMX4. > > What do you think about that ? > > Regards > JB >
