Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out a branching strategy and document it #14

Open
ironicbadger opened this issue Oct 10, 2020 · 3 comments
Open

Figure out a branching strategy and document it #14

ironicbadger opened this issue Oct 10, 2020 · 3 comments
Labels
documentation Improvements or additions to documentation

Comments

@ironicbadger
Copy link

Figure out a branching strategy and document it

@ironicbadger ironicbadger added the documentation Improvements or additions to documentation label Oct 10, 2020
@RealOrangeOne
Copy link
Member

RealOrangeOne commented Oct 10, 2020

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.

@Landrash
Copy link

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.

@WhiteNight121
Copy link

i like 1 and also think we should use stable vs master...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

4 participants