Skip to content

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Jan 30, 2025

Backport 1/1 commits from #140024 on behalf of @rail.

/cc @cockroachdb/release


Fixes: #139562
Epic: none
Release note: None


Release justification: test-only changes

Fixes: #139562
Epic: none
Release note: None
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-24.1-140024 branch from e7f47b4 to 5ed45c2 Compare January 30, 2025 13:54
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Jan 30, 2025
Copy link
Author

blathers-crl bot commented Jan 30, 2025

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Backports should only be created for serious
    issues
    or test-only changes.
  • Backports should not break backwards-compatibility.
  • Backports should change as little code as possible.
  • Backports should not change on-disk formats or node communication protocols.
  • Backports should not add new functionality (except as defined
    here).
  • Backports must not add, edit, or otherwise modify cluster versions; or add version gates.
  • All backports must be reviewed by the owning areas TL. For more information as to how that review should be conducted, please consult the backport
    policy
    .
If your backport adds new functionality, please ensure that the following additional criteria are satisfied:
  • 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. State changes must be further protected such that nodes running old binaries will not be negatively impacted by the new state (with a mixed version test added).
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.
  • Your backport must be accompanied by a post to the appropriate Slack
    channel (#db-backports-point-releases or #db-backports-XX-X-release) for awareness and discussion.

Also, please add a brief release justification to the body of your PR to justify this
backport.

@blathers-crl blathers-crl bot requested review from srosenberg and a team January 30, 2025 13:54
@blathers-crl blathers-crl bot added the backport Label PR's that are backports to older release branches label Jan 30, 2025
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@rail rail merged commit 6deffb9 into release-24.1 Jan 31, 2025
19 of 20 checks passed
@rail rail deleted the blathers/backport-release-24.1-140024 branch January 31, 2025 14:38
@crl-codesys-jira crl-codesys-jira added the T-release Release Engineering & Automation Team label Aug 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Label PR's that are backports to older release branches blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. T-release Release Engineering & Automation Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants