> Hi all > > This is to let you know that I hope to work on getting Synapse 1.3 out > soon.. I also think we should cut the branch when we are quite close > to the release, to ensure that the merging back [if any] will be > minimal.. Thus here is my plan of action proposed.. +1 How about releasing transport module and then make Synapse depend on that ? is it doable ?
Deepal > > 1. Change pom's to refer to Axis2 1.4.1 and related artifacts > 2. Review all critical issues, and those marked for 1.3 release > 3. Get the build stable with any changes from #2 > 4. Make builds available via automated Hudson builds, and get users to > help us with QA > 5. Update docs and samples through #4 > 6. Cut final branch, release and tag > > However, we have one major issue with the movement of the transports > to WC-Commons, .. with the package name conflict.. Does anyone have > any suggestions to solve this? > > Please let me know your comments and agreement with the above plan, > and any changes > > asankha > -- Thank you! http://blogs.deepal.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
