[backport 3.3] tools: update release notes template #11270
Merged
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.
(This PR is a backport of #11210 to
release/3.3
to a future3.3.2
release.)The given template comes from the time, when we had 1.10 and 2.x with the old release policy (see https://github.com/orgs/tarantool/discussions/6182). In fact, almost every aspect of this template is obsolete now.
For example, we have no stable and non-stable releases anymore: there are pre-releases (marked with alpha, beta, rc keywords) and releases. We don't need to say explicitly that the given release is stable.
Also, 1.10 is not LTS anymore (it is EOL) and 2.11 is not the latest series.
The links needs an update too.
So, I decided to write these templates from scratch, but keep the idea: give some release status information, highlight notable changes (for feature releases), provide a few hints about the update procedure.
Resulting templates are below.
3.x
2.11