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
@pcantera commented on Tue May 22 2018
Once implemented "goreleaser" tool, i,t's a must to evaluate the need for "release.sh" / "utils/version.sh" files.
If it is really a need, they have to be updated and support Alpha, Beta and Release candidates prior to generate the stable release (RTM).
Otherwise, they should be removed
1. 2. 3. 4.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
@pcantera commented on Tue May 22 2018
Once implemented "goreleaser" tool, i,t's a must to evaluate the need for "release.sh" / "utils/version.sh" files.
If it is really a need, they have to be updated and support Alpha, Beta and Release candidates prior to generate the stable release (RTM).
Otherwise, they should be removed
Expected Behavior
Current Behavior
Possible Solution
Steps to Reproduce (for bugs)
Context and environment
The text was updated successfully, but these errors were encountered: