+1 from me. if we do a code reformatting that should be done just before the branch is cut. Then we have almost same code base in both branch and the trunk. This enable developers to work on one code base (either trunk or branch) and apply patches to other (from the working codebase) easily.
Thanks Amila. On 4/24/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> Hi Axis2 developers: > > In an effort to coalesce some recent discussion into a policy, here is > a proposal for how we should manage releases and dealing with SVN. If > we can agree on this, I'll check in an HTML version, and we can start > following these guidelines for our next release. +1 > > > This is important stuff, please take a moment to read it over and see > if you agree with the principles. The goals are 1) minimize "speed > bumps" to active development, 2) make it easy to manage releases both > as they're going out and for future bug fixes, 3) make sure we don't > lose anything and also avoid giant merges. +1, I think we are too late for this release , o.w we can follow the procedure for 1.2 release as well. Thanks Deepal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Amila Suriarachchi, WSO2 Inc.
