To create a sandbox for any 0.5 work, do this:
cvs co -r CHANDLER_0_5_BRANCH <module name>
Any work done in that sandbox will be posted to the 0.5 branch
NOTE -- do not use the -A flag for updating as that will clear the branch tag and you will get magically transported to the trunk - *not* a Good Thing(tm)
A set of tinderboxes for 0.5 will be created and running by Monday (March 21st), so until then just be careful.
The 0.5 branch will be orphaned after the release, so if any bug fixes are needed in both the branch and the trunk, you must check them into both sandboxes. No merge will occur after the release.
If you are working on the trunk, you do not need to do anything special - just keep creating bugs like normal ;)
For the manual-reading-inclined folks: https://www.cvshome.org/docs/manual/cvs-1.11.19/cvs_5.html#SEC54
--- Bear http://code-bear.com
Open Source Applications Foundation (OSAF) http://www.osafoundation.org
PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
PGP.sig
Description: This is a digitally signed message part_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
