I find myself needing to make a branch of a project for some experimentation. I've been doing a bit of reading, and I'm getting this sinking feeling that the way I have my project structure set up it's going to be a hell of a lot of work. Maybe there's a way out...
So I have my Source Control project under $/Foo. There's an associated Team Project called "Foo". All has been good up till now. We just released, I've dropped my label and this particular code base is stable and not being actively worked on. But I do want to do a little experimentation on a possible feature, for which I'd like to make a branch.
If I'd been smart (and planned ahead), I'd have made my main project $/Foo/main and then I could branch to $/Foo/Experimental1. But I wasn't smart. :-(
My question, now that the source is stable, can I "move" the entire project from $/Foo to $/Foo/main and start from there? I'm guessing not. I *really* don't have to make a whole other team project.
Any suggestions on how to clean up this mess?
Brad.
Brad Smith
To answer my own question, turns out I *can* move my entire project to a sub-folder. So I moved everything under $/Foo to $/Foo/v1.0 and then branched $/Foo/v1.0 to $Foo/v1.0_Experiment. It looks like it didn't lose anything. :-)