add RELEASE_NOTE generation script (backport #336) #339
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
closes: #XXXX
RELEASE_NOTE
by codewhat's changed
only for regular release, not for release candidates. Because people mostly want to know the difference between main release. If we deploy the rc release notes separately, It's hard to track the changes at once.RELEASE_CHANGELOG
. UseCHANGELOG
instead.Motivation and context
How has this been tested?
Sample output
Screenshots (if appropriate):
Checklist:
CHANGELOG.md
This is an automatic backport of pull request #336 done by [Mergify](https://mergify.com).