> After some thought, I'm +1 to dims' position. Per-release branches are > much easier to maintain into the future, too - you branch, release, and > then you always have an easy place to go back and fix release-specific > problems.
Absolute +1 to this moving forward as a release approach. This will allow service releases in the future along with major development. -Nick Nicholas Gallardo WebSphere - WebServices Development [EMAIL PROTECTED] Phone: 512-838-1182 Building: 901 / 5G-016 Glen Daniels <[EMAIL PROTECTED]> 03/27/2007 08:48 AM Please respond to [email protected] To [email protected] cc Subject Re: [Axis2]Code freeze in trunk After some thought, I'm +1 to dims' position. Per-release branches are much easier to maintain into the future, too - you branch, release, and then you always have an easy place to go back and fix release-specific problems. Let's keep the trunk moving forward and release by branching. Release manager is responsible for the branch, but the individual change authors who write things that they want included in the release are the ones who have to do the merging, RM just coordinates and acts as gatekeeper. --Glen Davanum Srinivas wrote: > Deepal, > > I don't agree with this approach. If you want to make a release, then > cut a branch for the release. trunk should always be open for > business. > > thanks, > dims > > On 3/27/07, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: >> I agree .. IMO it'll be better to create a branch. And if we do release >> 1.2 within a week as planned the diff will be minor. Last time we spent >> *months* in a branch, which of course lead to major differences. >> >> Sanjiva. >> >> Thilina Gunarathne wrote: >> >> I have past experience in merging branch and trunk :) so this time I >> >> have no idea to cut a branch in the meantime dont see real requirement >> >> of doing so. >> > But you might have noticed the advantage of having the branch when we >> > are going for the 1.1.1... >> > >> >> I saw couple of commits in jax-ws module , since you guys are >> continuing >> >> development of jax-ws stuff it will be very helpful for you to >> create a >> >> branch and continue the development there in the branch. Then we can >> >> continue release related development in the trunk :). >> > Same problem... Different interface ;-) >> > >> > ~Thilina >> >> >> >> So I would like to declare a code freeze in Axis2 trunk .... >> >> >> >> comments ........ >> >> >> >> Thanks >> >> Deepal >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > >> >> -- >> Sanjiva Weerawarana, Ph.D. >> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/ >> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ >> Director; Open Source Initiative; http://www.opensource.org/ >> Member; Apache Software Foundation; http://www.apache.org/ >> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
