We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As described in the guidelines Galaxy tool version should derive from the version of the actual tool.
Are there guidelines/suggestions for older tools where the version of the Galaxy tool already departed from the version of the underlying tool.
Examples:
For instance we could decide to increase only minor tool version until the actual tool catches up (which might work for some tools).
The text was updated successfully, but these errors were encountered:
That might be a sensible approach, but in some cases it will never catch up.
Sorry, something went wrong.
Versioning scheme improvements
14f4f44
Applies for tools where the TOOL_VERSION+galaxyN can not be applied. Started a discussion here: galaxyproject/tools-iuc#2119
Sound good.
No branches or pull requests
As described in the guidelines Galaxy tool version should derive from the version of the actual tool.
Are there guidelines/suggestions for older tools where the version of the Galaxy tool already departed from the version of the underlying tool.
Examples:
For instance we could decide to increase only minor tool version until the actual tool catches up (which might work for some tools).
The text was updated successfully, but these errors were encountered: