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.

Sign up for GitHub

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

Jump to bottom

Better release process #163

Open

macrozone opened this issue Feb 28, 2018 · 0 comments

Collaborator

macrozone commented Feb 28, 2018

Currently, latest features get into master and we usually publish a beta version of that.

But new users heading to this repo might install the stable release, but see the beta version of the readme, which leads to confusion.

so we should make master always match the latest stable release and introduce a develop-branch.

Any thoughts and advice?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment