From: "Sam Ruby" <[EMAIL PROTECTED]> > To handle situations such as these, I recommend creating a branch for the > completion of the 1.3 work. While nobody is restricted from committing to > the branch, it is not the default action therefore it requires conscious > effort on the part of committers to place items in this branch. Any > changes made to the branch should also be made to the base tree as that is > the version from which the next release will be made. If the rate of > change during the release cycle slow down as it should, and if the release > cycle is short, then the divergence is small and this should involve > minimal extra effort.
No problems. I have created a branch, ANT_13_BRANCH, for the remainder of the release process. The MAIN trunk is now considered to be Ant 1.4 alpha. I will manage the merging of all 1.3 changes back into the MAIN trunk when the release is completed. Conor
