Figure out a branching strategy and document it
Figure out a branching strategy and document it
Suggestion:
develop represents current development, "unstable", default branch on GitHub. All PRs to/from this
master represents "stable". On release, commits are merged from develop into master, and tagged (useful for #12 )
Suggestion 2:
master represents current development, "unstable", default branch on GitHub. All PRs to/from this.
Releases are tracked as tags. To checkout, simply checkout by specific tag.
Personally I prefer the latter, as it removes the need for an extra branch.
Suggestion 1 mirrors how Home Assistant does this.
It might be a plan to avoid the master branch name controversy and rename it to stable.
i like 1 and also think we should use stable vs master...