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

release-21.2: ui: say "reset" SQL stats instead of "clear" #74417

Merged
merged 1 commit into from
Jan 6, 2022

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Jan 4, 2022

Backport 1/1 commits from #73922 on behalf of @matthewtodd.

/cc @cockroachdb/release


Fixes #73444

Release note (ui change): The "clear SQL stats" links on the statement
and transaction pages were relabeled "reset SQL stats," for consistency
with the language in the SQL shell.


Release justification: Category 2: Bug fixes and low-risk updates to new functionality

Fixes #73444

Release note (ui change): The "clear SQL stats" links on the statement
and transaction pages were relabeled "reset SQL stats," for consistency
with the language in the SQL shell.
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-21.2-73922 branch from c337070 to c402fcc Compare January 4, 2022 18:56
@blathers-crl blathers-crl bot requested a review from Azhng January 4, 2022 18:56
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Jan 4, 2022
@blathers-crl
Copy link
Author

blathers-crl bot commented Jan 4, 2022

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues or test-only changes.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@matthewtodd matthewtodd requested a review from a team January 4, 2022 18:57
@maryliag maryliag merged commit fee0515 into release-21.2 Jan 6, 2022
@maryliag maryliag deleted the blathers/backport-release-21.2-73922 branch January 6, 2022 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants