I mean to fix v1.0 as the main branch and as v2.0 subbranch? What will happen if I make v3.0 SDK, a branch v2.0 suburban?
OR
Create a new repository with "v2.0" / "v3.0". Postfixes?
So the question is: What is the best way to support many different versions of your SDK and keep them in one place at the same time?
Thx.
I definitely make different repos per edition, assuming that these versions 1.0, 2.0, 3.0 are called to be called. This will make life a lot easier for you to manage bridge requests. Apart from this, it is better if it comes to the generation of this branch.
IMHO, if you keep only one branch alive and overwritten version, then there can be a disturbance in the end. Imagine that you have a new feature under the specific commitment pending development (v1.0), while v2.0 has been corrected and it is ready to be distributed. Add a pull request to the developer, which has fixed the weight of the bugs in the initial release of v1.0 ....
In this case, then IMHO, split and win. Repo Per Edition
Hope you like it!
No comments:
Post a Comment