Hi Kym Thanks very much for such a detailed response. So just to be 100% sure of what you're saying: 1. You should only ever one version of the code on your dev machine i.e. if you're working on one branch (Branch A) but need to swap to another branch (Branch B) than you should check in Branch A and checkout Branch B i.e. Branch B overrides Branch A in your working copy. This makes sense because you wouldn't want to have more than one project checked out at anyone time. Would you recommend checking in daily work to the branch, trunk or both? 2. Once you've completed a branch, check it back in, copy it to a tag (i.e. latest version ready for production), and perhaps delete the Branch to clean things up. Then export the tagged version for Production via SVN or FTP or whatever you prefer. So essentially the production server could have Subversion installed and it's "working copy" is the code which is live. So all you are doing is checking out a tagged version from shared server to production server when you upgrade to new version. Makes sense! 3. All I've got to work out now is how to override my dev working copy in Eclipse because so far I've only worked out how to checkout a version into a new project... I'll keep playing around. I guess the other option is to try Tortoise as per your "switching" suggestion.
Thanks a million again! Cheers Matthew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
