Hi Deepal! Deepal Jayasinghe wrote:
I have created a branch for 1.0 [1] release so let's continue the release related stuff in the branch. In the meantime please do not forget to keep the trunk in sync with the branch (meaning whenever you do a commit to branch ,please commit that to truck as well , create a patch from branch before you commit and then apply that to trunk).
The right way to do this is actually the other direction - continue to work on the trunk, and make sure to merge your changes over to the branch. See the Axis2 release process [1] for details. The idea here is that the trunk should always be "cutting edge" and contain all fixes. There should never be a time when actual work is happening on the branch that isn't reflected on the trunk (except when a) it's actually release specific work that won't ever go on the trunk (version numbers etc), or b) the trunk has moved on in an incompatible way, which should be VERY rare).
Please noticed that we're ALREADY in a bad situation with several commits to the 1_0 branch that are not yet reflected on the trunk.
Let's please switch to the other way? Thanks, --Glen _______________________________________________ Registry-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
