Is maintaining 1 branch per version really a better option than having a subfolder per version?
samuele-mattiuzzo opened this issue · 0 comments
samuele-mattiuzzo commented
As per topic
We have version-xxx branches, with a branch per Standard version. This is true for the SSOT Reference Site (hence the refactoring task) and the Submodules.
Now, what's the benefit of this rather than having a structure like
/project-root-folder/standard/203/ruleset.json
/project-root-folder/standard/202/ruleset.json
...
(Using rulesets as example, but appliable to most)
Any thoughts? Effort is the same, except we don't have to work funky merges and constantly switch back and forth in between branches, merges and whatnot.
@Ocre42 and @sargentfrancesca thoughts?