Skip to content
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

[14.0] Rework the generation of the release notes #10532

Merged
merged 1 commit into from
Jun 17, 2022

Conversation

frouioui
Copy link
Member

Description

This is a backport of #10510.

Related Issue(s)

Checklist

  • "Backport me!" label has been added if this change should be backported
  • Tests were added or are not required
  • Documentation was added or is not required

* generate the release changelog as a second document

Signed-off-by: Florent Poinsard <[email protected]>

* include every PR in the release notes

Signed-off-by: Florent Poinsard <[email protected]>

* Moved changelog metrics away from the changelog and added summary for v15

Signed-off-by: Florent Poinsard <[email protected]>
@github-actions
Copy link
Contributor

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has the correct release notes label. release notes none should only be used for PRs that are so trivial that they need not be included.
  • If a new flag is being introduced, review whether it is really needed. The flag names should be clear and intuitive (as far as possible), and the flag's help should be descriptive.
  • If a workflow is added or modified, each items in Jobs should be named in order to mark it as required. If the workflow should be required, the GitHub Admin should be notified.

Bug fixes

  • There should be at least one unit or end-to-end test.
  • The Pull Request description should either include a link to an issue that describes the bug OR an actual description of the bug and how to reproduce, along with a description of the fix.

Non-trivial changes

  • There should be some code comments as to why things are implemented the way they are.

New/Existing features

  • Should be documented, either by modifying the existing documentation or creating new documentation.
  • New features should have a link to a feature request issue or an RFC that documents the use cases, corner cases and test cases.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • vtctl command output order should be stable and awk-able.

Copy link
Member

@deepthi deepthi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍
Not merging yet because our same old query serving upgrade/downgrade tests are failing.

@deepthi
Copy link
Member

deepthi commented Jun 17, 2022

Not merging yet because our same old query serving upgrade/downgrade tests are failing.

Actually this PR contains no executable code changes, only release notes generation. Merging now, but please take a look at the test failures anyway.

@deepthi deepthi merged commit b1ab98f into vitessio:release-14.0 Jun 17, 2022
@deepthi deepthi deleted the bp-10510-on-14 branch June 17, 2022 23:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants