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-23.1.21-rc: release: move release qualification buckets #122804

Merged

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Apr 22, 2024

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

/cc @cockroachdb/release


This PR moves the release qualification bucket to a new project.

Part of: RE-163
Release note: None


Release justification: release automation changes

This PR moves the release qualification bucket to a new project.

Part of: RE-163
Release note: None
@blathers-crl blathers-crl bot requested a review from a team as a code owner April 22, 2024 14:39
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-23.1.20-rc-122646 branch from e259d6b to bbdef3f Compare April 22, 2024 14:39
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Apr 22, 2024
@blathers-crl blathers-crl bot requested a review from celiala April 22, 2024 14:39
Copy link
Author

blathers-crl bot commented Apr 22, 2024

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 and one additional
    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 added the backport Label PR's that are backports to older release branches label Apr 22, 2024
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@celiala celiala changed the title release-23.1.20-rc: release: move release qualification buckets release-23.1.21-rc: release: move release qualification buckets Apr 26, 2024
@rail rail merged commit fceb4cf into release-23.1.21-rc Apr 29, 2024
6 checks passed
@rail rail deleted the blathers/backport-release-23.1.20-rc-122646 branch April 29, 2024 13:15
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants