I am part of a team that issues versions of our software 4-5 times for our customers. Even by fixing such errors, we keep the last 2-3 versions of our product which we see in later versions. We are using TFS 2008 for source control and are trying to find the best way to maintain older versions.
Every time we make a new edition, we currently make a branch of our application, but we are searching for a better way to update the old version more easily. For example, we 9.5, but after two weeks after the formation of the branch, we are working on 10.0, we know that there is an error in 9.5. We currently make changes to version 10.0 and then open 9.5, to make changes again. Is this what it is?
Thank you!
This is one of the main reasons for the merger and the branches.
In your situation, I am making a change to 9.5 and then merge the change in my main branch, and then returning it to my 10.0 branch. Made in merge tools works well for it.
If you go in the other direction, you run the risk of adding new 10.0 accessories to the 9.5 branch, when you want you to fix the bug.
I will also take a look for more information about branches and merger.
Comments
Post a Comment