Advice for use of Subversion
From: Clark, Ken <Ken.Clark_at_pfizer.com>
Date: 2006-04-20 22:01:23 CEST
We have an existing production system that uses CVS as its CM store. There is ongoing maintenance against a branch (the most recent major release).
We have another project which is about to come on line. One of its major activities is to convert about 1/4 the code base to use an upgraded framework. In order to do the upgrade, the easiest path is to break a single monolithic code tree into a number of smaller subsections. This must at least be done at build time to comply with the new FW. But it would be better still to alter the layout of the source code also, along the same lines as the deployment.
In CVS, of course, this could not be done without abandoning the original repository, and along with it the ability to merge the maintenance code changes with the new development.
We are considering using Subversion instead because it appears that this should be possible.
Some questions:
1) First, will Subversion allow us to merge code changes from a branch to code changes on HEAD, even when the code is completely reorganized in HEAD
Thanks,
----------------------------------------------------------------------
---------------------------------------------------------------------
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.