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
Storing release notes in the repository has the following advantages compared to using GitHub releases as a source of truth:
The best practice I've encountered is to put a separate file in docs/release-notes for each new release.
docs/release-notes
See dcrpool, dcrd or vspd as examples of adopting this convention.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Storing release notes in the repository has the following advantages compared to using GitHub releases as a source of truth:
The best practice I've encountered is to put a separate file in
docs/release-notes
for each new release.See dcrpool, dcrd or vspd as examples of adopting this convention.
The text was updated successfully, but these errors were encountered: