This is an issue every time we do a release. I wonder if we should split out the Rampart/Sandesha2 integration into some separate modules so we can do releases without them and then play catch up when they are available? Not sure if that would work!
Paul On Mon, Jun 15, 2009 at 4:18 AM, Asankha C. Perera<[email protected]> wrote: > Hi all > > I am sorry I've been a bit busy lately, but now we have Axis2 1.5 released, > HttpComponents 4.0.1 on the way etc.. However, I am not sure on the release > plans of Rampart/Sandesha etc - Ruwan are you aware? > > I am also seeing some refactoring of the Commons/Transports by Andreas, and > assume we should pick a new release of it if/once thats complete. Also from > the JIRA's marked fix for 1.3, the remaining bugs seem to be pushable into > 1.3.1 - Synapse-527, 348, 330, 310. > > I think we should draw the line, and start on a first RC now (as soon as > Andreas can confirm the Transport refactoring are ready).. then wait for > Rampart/Sandesha to release. I am also ok to branch out, so that others can > continue development of anything else on trunk - *if thats required*. But > basically whats there right now - to go into Synapse 1.3 > > Please let me know your thoughts on this > > thanks > asankha > > -- > Asankha C. Perera > AdroitLogic, http://adroitlogic.org > > http://esbmagic.blogspot.com > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [email protected] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
