blathers-crl[bot]
commented
14 hours ago Thanks for opening a backport.
Please check the backport criteria before merging:
- [x] Backports should only be created for serious issues or test-only changes.
- [x] Backports should not break backwards-compatibility.
- [x] Backports should change as little code as possible.
- [x] Backports should not change on-disk formats or node communication protocols.
- [x] Backports should not add new functionality (except as defined here).
- [x] Backports must not add, edit, or otherwise modify cluster versions; or add version gates.
- [x] 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:
- [x] There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way. - [x] The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting). - [x] 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). - [x] The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules. - [x] 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.
cockroach-teamcity
Backport 1/1 commits from #133284 on behalf of @angles-n-daemons.
/cc @cockroachdb/release
demo: remove copy referring to telemetry disabling env var
COCKROACH_SKIP_ENABLING_DIAGNOSTIC_REPORTINGcan still be used to disable telemetry for CRDB. With the core deprecation happening however, we want to streamline how people enable / disable telemetry in their cluster, so the copy to this variable has been removed.It will still function as before, the only difference is that it will not show up in the demo startup message.
Epic: CRDB-40209 Fixes: #132688 Release note (general change): COCKROACH_SKIP_ENABLING_DIAGNOSTIC_REPORTING is no longer mentioned in the demo command.
Release justification: part of the core license policy changes