Version Control project to project

[nfberg]

Howdy,

I tried to search on this topic but all the search terms were to common.

We are about to start work on a version 1.1 of a product since 1.0 has been released. Management wants to lock down 1.0 and have all the help docs archived. v 1.1 is not going to add a lot and to me it would make sense just to edit a few areas in 1.0 but as they want to have all versions as stand alones I'm a bit confused as to how I want to proceed.

I'm thinking I create a new project importing all of 1.0 and then editing to suit. Before I build I shut off checking for updates from outside source.

I'm certainly open to other suggestions.

Thanks

[KevinDAmery]

An even simpler way to do it would be to copy the project folder structure - this would give you two identical sets of files. You could then modify the 1.1 version as required.

I think a better way would be to keep everything in one project and use conditions to include / exclude content that is not relevant for the particular versions, but if management understands that process and still want to have a complete separation between 1.0 and 1.1, then duplicating the help projects works well enough.