MC
16 years agoContributor
subversion/scc best practices
We currently have a small group of three creating test cases for a set of webservices.
We've version controlled the (non-composite) project file, let's call it tests-soapui-project.xml.
We have tests-soapui-project.xml under subversion control. Unfortunately, being
a single monolithic file, we need to merge changes whenever one of us changes the
project file, which we do on every commit to the subversion repository. If we botch
the merge, then we corrupt the project file, moreover since we're merging at the
.xml file level, it's not always clear what we're merging together.
What are your "best practices" for having several people work on a single project?
Please advise. Thanks.
We've version controlled the (non-composite) project file, let's call it tests-soapui-project.xml.
We have tests-soapui-project.xml under subversion control. Unfortunately, being
a single monolithic file, we need to merge changes whenever one of us changes the
project file, which we do on every commit to the subversion repository. If we botch
the merge, then we corrupt the project file, moreover since we're merging at the
.xml file level, it's not always clear what we're merging together.
What are your "best practices" for having several people work on a single project?
Please advise. Thanks.