-
Notifications
You must be signed in to change notification settings - Fork 100
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
Add --match v.[0-9]*
to git describe
#1857
Conversation
In order to prevent non-official tags from causing server/client version breakage, filter out all non official-looking tags, i.e. "v.4.4.9"
The odd case where the custom tag starts with |
Added a commit to make the value externally configurable. Do you think the following would be a better default?
|
@joshmoore: since we committed to using semantic versioning for our version numbers, I would think |
Commit for semver pushed. |
Looks good. Are you planning any additional change? |
No sir. |
Add `--match v.[0-9]*` to `git describe`
--rebased-to #1879 |
In order to prevent non-official tags from causing
server/client version breakage, filter out all non
official-looking tags, i.e. "v.4.4.9"
see: http://trac.openmicroscopy.org.uk/ome/ticket/11727
Testing
git tag -a foo_bar
) should NOT affect the output of./build.py version