Config. Management for Concurrent programming
In our company we are setting up Configuration Management Process. Looking for strategies to efficiently manage codes in current development environment. Currently we are considering the following two approaches. Most of our codes are system generated XMLs (tool based development)
Approach 1 : Have new folders created for each release and maintain XMLs in there till moved to production.Manually reconsile the changes made to codes due to other concurrent releases
Approach 2 : create branches for each release and finally merge back to main. Using merge features of CM tools to reconsile changes
Since most of our codes are XMLs, we are not really depending on the merge features provided by CM tools like CVS or VSS and plannign to manually merge.
Please suggest if there are other strategies to implement this.
thanks in advance.
Re: Config. Management for Concurrent programming