M
Marcus Leon
Hello, we're looking for advice with a source control issue. Can
anyone offer any suggestions?
We use AllFusion Harvest for source control. We currently get a new
release of a large software product from a vendor every quarter. This
release comes in the form of Java code, build scripts, etc. We
sometimes modify this code ourselves so we would like this code in
source control.
We are wondering how best to handle dealing with new releases. We are
assuming that our modifications to the code will have been added to the
new releases by the vendor so new releases won't overwrite our changes.
We're just not sure how to properly deal with new versions.
I believe you can label the current code base to indicate a specific
release. But what if release 1 includes file X and release 2 has
removed this file from the project. If we copy release 2 over release
1 then file X will still be there which could cause problems. Or
should we delete release 1 and then add release 2?
Any suggestions would be great.
Thanks
anyone offer any suggestions?
We use AllFusion Harvest for source control. We currently get a new
release of a large software product from a vendor every quarter. This
release comes in the form of Java code, build scripts, etc. We
sometimes modify this code ourselves so we would like this code in
source control.
We are wondering how best to handle dealing with new releases. We are
assuming that our modifications to the code will have been added to the
new releases by the vendor so new releases won't overwrite our changes.
We're just not sure how to properly deal with new versions.
I believe you can label the current code base to indicate a specific
release. But what if release 1 includes file X and release 2 has
removed this file from the project. If we copy release 2 over release
1 then file X will still be there which could cause problems. Or
should we delete release 1 and then add release 2?
Any suggestions would be great.
Thanks