I suppose this is a pretty noob question, but I haven’t found an answer that satisfy me. I want to achieve the following:
- I have a project with repository with a master-branch which contains the currently released version of the project. (I use tags to mark every release)
- The customer now have a bunch of changes that needs to be applied, in many ways changing basic functionality of the project, or at least change the way certain things are being handled. I feel that the changes are major so a release 2.0 is motivated.
- However I still need to maintain version 1.0.x as this version is used for other customers.
My first idea was to create a fork, but they can´t be placed within the same group which causes un non logical structure for me. So, what would you say is the best way to maintain multiple major versions of a project?