I publish COM addins for Office via ClickOnce. At the moment, I have only one main branch on the Repos tree (using Azure DevOps), and each time I publish, all the users are automatically updated.
Now, what if I release a substantial update - which would involve a change in a work flow - and one of the teams wishes not to roll the update? (could be for many reasons such as "we are in the middle to sending something out and no time for learning curve right now", to "the new update does not provide a feature we loved") I can implement this, but what if then I have to undertake a critical-compulsory fix?
I am thinking of allowing several major versions to be available in parallel, whilst within each of them a minor version update would be compulsory. That is, going from 1.2 to 2.0 would be optional, but going from either 1.2 to 1.3 or 2.0 to 2.1 would be compulsory. This way, everyone is happy.
Well, I hope.. Because I never worked on distinct Repos branches. Also, not sure how ClickOnce might like this..
Any tips or warnings for potential challenges would be much appreciated. Thanks!