I started working at a startup and some bad version control practices
were being followed in CVS. The developers were being forced to add
features as well as bug fixes to a production branch to the point where
trunk became hopelessly out of sync with the branch. I migrated the
repository to Subversion preserving the old CVS revision histories. So
far so good, but now I want to get back to sanity where trunk is where
new development occurs, tag releases that pass unit tests and are
deployed to the Dev environment, branch the tag when it is promoted to
production, and branch bug fixes and merge those back to trunk.
If I tag the trunk prior to copying branch over it, then do an svn copy
over trunk from production branch, will that do what I want? To be more
explicit, I will still be able to access the old trunk's files from the
tag. If I do a checkout of trunk at this point I should get exactly the
files I would have from the production branch, no more, no less, correct?
Now I can tag my trunk and then branch from the tag, when it is rolled
into production. Considering the situation, is this a good and
appropriate solution to my bad situation? Are there any gotchyas?
Thank you.
Fred
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Feb 17 12:36:29 2007