yes. I think the better solution is to cut the axis2 branch now. Any way now we depend on the Axis2 1.6 release branch where we can not expect many changes. Then after cutting the 3.2.0 branch move to axis2 trunk.
thanks, Amila. On Fri, Feb 25, 2011 at 6:52 PM, Thilina Buddhika <[email protected]> wrote: > One solution might be to branch in the dependencies for the next release. > So that people can commit the necessary changes to our internal branch which > should be go into the release when committing them to the trunk. > > Since we are getting closer to the release, I think it is better to take > dependencies in and stabilize the build. > > Thanks, > Thilina > > > On Fri, Feb 25, 2011 at 6:33 PM, Amila Suriarachchi <[email protected]>wrote: > >> >> >> On Fri, Feb 25, 2011 at 11:31 AM, Sameera Jayasoma <[email protected]>wrote: >> >>> Hi Supun, >>> >>> What are the advantages of moving the Axis2 trunk again? Is there any new >>> stuff in Axis2 trunk? At the moment we are using Axis2 1.6 release branch. >>> >> >> Whether we move to Axis2 trunk or not is a separate concern. But we need a >> method so that we can do changes to the axis2. I also want to do two changes >> to axis2 regarding SQS. >> >> thanks, >> Amila. >> >>> >>> Thanks >>> Sameera >>> >>> >>> On Fri, Feb 25, 2011 at 11:19 AM, Supun Kamburugamuva >>> <[email protected]>wrote: >>> >>>> ---------- Forwarded message ---------- >>>> From: Andreas Veithen <[email protected]> >>>> Date: Sun, Feb 20, 2011 at 1:59 AM >>>> Subject: [Axis2][Rampart][Sandesha2] Migration to Neethi 3 completed >>>> To: java-dev <[email protected]> >>>> >>>> >>>> All builds are now stable again, with the 1.6 branches depending on >>>> Neethi 2.0.4 and the trunks depending on 3.0.0-SNAPSHOT. >>>> >>>> All three projects now have a release branch with version number >>>> 1.6.0-SNAPSHOT (actually 1.6.1-SNAPSHOT for Axis2, since Ruwan already >>>> created the 1.6.0 release tag) and a trunk with version number >>>> 1.7.0-SNAPSHOT. For Sandesha2, this means that we skip version 1.5 (as >>>> discussed previously). All Hudson builds automatically deploy to >>>> repository.apache.org. This means that downstream projects such as >>>> Synapse now need to make a choice with respect to the Axis2 version >>>> they want to use, and update their POM files accordingly. >>>> >>>> >>>> Thanks, >>>> -- >>>> Supun Kamburugamuva >>>> Technical Lead & Product Manager, WSO2 Inc.; http://wso2.com >>>> Member, Apache Software Foundation; http://www.apache.org >>>> WSO2 Inc.; http://wso2.org >>>> E-mail: [email protected]; Mobile: +94 77 431 3585 >>>> Blog: http://supunk.blogspot.com >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> [email protected] >>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>> >>> >>> >>> -- >>> Sameera Jayasoma >>> Technical Lead and Product Manager, WSO2 Carbon >>> >>> WSO2, Inc. (http://wso2.com) >>> email: [email protected] >>> blog: http://tech.jayasoma.org >>> >>> Lean . Enterprise . Middleware >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Thilina Buddhika > Senior Software Engineer > > WSO2 Inc. ; http://wso2.com > lean . enterprise . middleware > > phone : +94 77 44 88 727 > blog : http://blog.thilinamb.com >
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
