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

Closed binary update should triggger a minor version update. #21

Open
dominig opened this issue Apr 24, 2017 · 0 comments
Open

Closed binary update should triggger a minor version update. #21

dominig opened this issue Apr 24, 2017 · 0 comments

Comments

@dominig
Copy link
Contributor

dominig commented Apr 24, 2017

Hello,

oeSENC is the type of plugin where the version is important as it may need changes once in a while.
I notice a change on closed source binaries on March 17th, followed by a Version Patch change but in OpenCPN only the version Major and Minor are reported, so a user who does not understand Git has no mean to know which version he runs.
It would be a good idea to update the minor even when only binary changes to let any user knows what he runs.
screenshot_20170424_145041

SET(VERSION_MAJOR "0")
SET(VERSION_MINOR "4")
-SET(VERSION_PATCH "1515")
+SET(VERSION_PATCH "1516")

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