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.

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

How is the version (major, minor, patch) going to evolve? #21

Open
Galbar opened this issue Apr 2, 2015 · 4 comments
Open

How is the version (major, minor, patch) going to evolve? #21

Galbar opened this issue Apr 2, 2015 · 4 comments

Comments

@Galbar
Copy link
Contributor

Galbar commented Apr 2, 2015

I've added the version defines in #20 . I'm using this to make sure the installed version in the system is compatible with the one I developed the app for (mainly the new functionalities I added in that same PR). How is the version going to evolve to make sure this is reliable?
@andrewrk
Copy link
Collaborator

andrewrk commented Apr 2, 2015

http://semver.org/

@Galbar
Copy link
Contributor Author

Galbar commented Apr 2, 2015

Ok, then as I added functionality in a backwards-compatible manner in #20 , shouldn't the version be 1.1.0 now?
We should also add a patch version define to the code.

@andrewrk
Copy link
Collaborator

andrewrk commented Apr 2, 2015

Yes, you're right. I'll do that and then make a release tag.

@andrewrk andrewrk mentioned this issue May 31, 2015
Merged
@RobLoach
Copy link
Contributor

I've been using https://github.com/h2non/semver.c with some great success.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@RobLoach @andrewrk @Galbar