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

Branches and tags #14

Open
deohnas opened this issue Jan 17, 2016 · 0 comments
Open

Branches and tags #14

deohnas opened this issue Jan 17, 2016 · 0 comments

Comments

@deohnas
Copy link

deohnas commented Jan 17, 2016

You should use branches and tags to get a better structure on the repository.

I would suggest that you adopt a semantic version approach. This approach are used by many popular frameworks and libraries.

MAJOR.MINOR.PATCH
Take a look at http://semver.org/

Branches:

master - The most recent stable version
develop - The branch you are developing next release on

Tags:
x.x.x

Until you have a first release (1.0.0) I would simply use the develop branch and then push in to the master and call it the day. When you release 1.0.1, I would tag 1.0.0 and move 1.0.1 to master branch from develop.

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

No branches or pull requests

1 participant