-
Notifications
You must be signed in to change notification settings - Fork 388
tools: update release notes template #11210
New issue
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
tools: update release notes template #11210
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! It was a pain editing this template for each release.
The given template comes from the time, when we had 1.10 and 2.x with the old release policy (see [1]). 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. [1]: https://github.com/orgs/tarantool/discussions/6182 NO_DOC=dev tools NO_CHANGELOG=same NO_TEST=same
4b4358a
to
87735b6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, LGTM!
Successfully created backport PR for |
Successfully created backport PR for |
Successfully created backport PR for |
Backport summary
|
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