Ruwan, You are claiming that it would not be possible to get a Sandesha2 release out in time for the Synapse release. My point is that you can't claim this is you don't even ask the question on [email protected]. The fact that it didn't happen in the past doesn't mean that it would not be possible to do it today.
Here is what I propose: * You explain the situation on the [email protected] list and ask if it is possible to get a release quickly. * If a Sandesha2 release vote starts before the final Synapse release vote, you wait for the outcome of the Sandesha2 vote and publish Synapse with the released Sandesha2 version. * If it is not possible to get a Sandesha2 release, if the vote doesn't start in time, or if that vote fails, you go ahead and publish Synapse with your private build. Does that sound like a reasonable compromise to you? Andreas On Fri, Dec 3, 2010 at 03:42, Ruwan Linton <[email protected]> wrote: > There is a Sandesha RC which is being voted and is not out on the maven > repos yet. Synapse release has been dragging for too long almost 2 and half > years because of this compatible releases problem first we had transports > and no one including you were not interested about giving synapse a release > out, so I have done the transports release on my own and now stucked at the > Sandesha2 build and only that. > We cannot keep on dragging this, on the other hand Sandesha is Apache > license and there is no body permitting me doing a custom build of the code > if I want to. > I am sorry I have to do this release and be done with the Synapse-2.0. > Thanks, > Ruwan > > On Thu, Dec 2, 2010 at 3:41 PM, Andreas Veithen <[email protected]> > wrote: >> >> -1. Before doing this you should at least ask on the relevant mailing >> list if there are people willing to prepare a Sandesha2 release. From >> what you are saying it looks like the Sandesha2 code is in a >> releasable state. Therefore this would only require cleaning up the >> site and the build/release system. >> >> Andreas >> >> On Thu, Dec 2, 2010 at 05:10, Ruwan Linton <[email protected]> wrote: >> > We were initially thinking of dropping the Sandesha2 support for the >> > Synapse-2.0, but I have been keeping the Sandesha2 SNAPSHOT dependency >> > till >> > now, and I tried the RM samples with the SNAPSHOT build of Sandesha2 and >> > seems to be working just fine. This is not the case with the latests >> > release >> > available from Sandesha2 (1.3) where non of the samples are working. >> > So I suggest to do a custom build of the Sandesha2 trunk under synapse >> > and >> > ship it with Synapse and add it as a known issue to the site explaining >> > the >> > issues that it could lead to as we are shipping a SNAPSHOT of the >> > Sandesha2. >> > This will help us keep the samples working yet ask the production users >> > to >> > wait for a stable compatible Sandesha2 release. >> > WDYT? >> > Appreciate your quick feedback as I am planning to do a RC ASAP of >> > Synapse-2.0 >> > Ruwan >> > >> > -- >> > Ruwan Linton >> > Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb >> > WSO2 Inc.; http://wso2.org >> > >> > Lean . Enterprise . Middleware >> > >> > phone: +1 408 754 7388 ext 51789 >> > email: [email protected]; cell: +94 77 341 3097 >> > blog: http://blog.ruwan.org >> > linkedin: http://www.linkedin.com/in/ruwanlinton >> > google: http://www.google.com/profiles/ruwan.linton >> > tweet: http://twitter.com/ruwanlinton >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > Ruwan Linton > Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb > WSO2 Inc.; http://wso2.org > > Lean . Enterprise . Middleware > > phone: +1 408 754 7388 ext 51789 > email: [email protected]; cell: +94 77 341 3097 > blog: http://blog.ruwan.org > linkedin: http://www.linkedin.com/in/ruwanlinton > google: http://www.google.com/profiles/ruwan.linton > tweet: http://twitter.com/ruwanlinton > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
