If we can get away without having to maintain a branch before the release, then that would make things easier. I set the version to 1.5 to avoid accidental introduction of code that depends on post-1.5 features. If there is a need to start developing things for the 1.1 release of the transports, then we should of course create a branch for the 1.0 release.
Andreas On Mon, Jun 1, 2009 at 16:58, Amila Suriarachchi <[email protected]> wrote: > Are you going to do the release from the trunk? > > > On Sun, May 31, 2009 at 9:34 PM, <[email protected]> wrote: > >> Author: veithen >> Date: Sun May 31 16:04:35 2009 >> New Revision: 780463 >> >> URL: http://svn.apache.org/viewvc?rev=780463&view=rev >> Log: >> Set Axis2 version to 1.5; we need to make sure that we will be able to do a >> release of the transports againsts that Axis2 version. >> >> Modified: >> webservices/commons/trunk/modules/transport/modules/parent/pom.xml >> >> Modified: >> webservices/commons/trunk/modules/transport/modules/parent/pom.xml >> URL: >> http://svn.apache.org/viewvc/webservices/commons/trunk/modules/transport/modules/parent/pom.xml?rev=780463&r1=780462&r2=780463&view=diff >> >> ============================================================================== >> --- webservices/commons/trunk/modules/transport/modules/parent/pom.xml >> (original) >> +++ webservices/commons/trunk/modules/transport/modules/parent/pom.xml Sun >> May 31 16:04:35 2009 >> @@ -405,7 +405,7 @@ >> </distributionManagement> >> <properties> >> <axiom.version>1.2.8</axiom.version> >> - <axis2.version>SNAPSHOT</axis2.version> >> + <axis2.version>1.5</axis2.version> >> <failIfNoTests>false</failIfNoTests> >> </properties> >> </project> >> >> >> > > > -- > Amila Suriarachchi > WSO2 Inc. > blog: http://amilachinthaka.blogspot.com/ >
