release-23.1: clusterversion: set developmentBranch to false#99387
release-23.1: clusterversion: set developmentBranch to false#99387celiala merged 1 commit intocockroachdb:release-23.1from
Conversation
|
It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR? 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
7bfced2 to
6f75eed
Compare
6f75eed to
e42af56
Compare
This commit is causing these test to fail:
Because we really need version.txt to be alpha.8 in order to select this week's candidate, I'm going to pull this into its own PR, so we can merge that asap: |
rail
left a comment
There was a problem hiding this comment.
Reviewed 9 of 9 files at r1, 1 of 1 files at r2, all commit messages.
Reviewable status:complete! 0 of 0 LGTMs obtained (waiting on @celiala, @dt, and @renatolabs)
docs/generated/settings/settings-for-tenants.txt line 292 at r2 (raw file):
trace.span_registry.enabled boolean true if set, ongoing traces can be seen at https://<ui>/#/debug/tracez trace.zipkin.collector string the address of a Zipkin instance to receive traces, as <host>:<port>. If no port is specified, 9411 will be used. version version 22.2-94 set the active cluster version in the format '<major>.<minor>'
Do you know why we set the version to xx.yy-zz, but mention it as <major>.<minor>?
pkg/clusterversion/cockroach_versions.go line 901 at r1 (raw file):
// 2. forced to `false` on release branches: this allows running a // release binary in a dev cluster. var developmentBranch = false || envutil.EnvOrDefaultBool("COCKROACH_FORCE_DEV_VERSION", false)
Is there any specific reason to have false || ... here? Looks like the first part is ignored in any case and can be removed.
5dc7a43 to
affbbb1
Compare
celiala
left a comment
There was a problem hiding this comment.
Reviewable status:
complete! 0 of 0 LGTMs obtained (waiting on @dt, @rail, and @renatolabs)
docs/generated/settings/settings-for-tenants.txt line 292 at r2 (raw file):
Previously, rail (Rail Aliiev) wrote…
Do you know why we set the version to
xx.yy-zz, but mention it as<major>.<minor>?
Not sure tbh? (all I know is that this has been the format for a while 🤷 )
pkg/clusterversion/cockroach_versions.go line 901 at r1 (raw file):
Previously, rail (Rail Aliiev) wrote…
Is there any specific reason to have
false || ...here? Looks like the first part is ignored in any case and can be removed.
Ack, removed false ||
|
following up here #100685 |
|
3 tests are failing here: (1) (2) (3) |
|
Fixes for failing tests have been backported 🎉 (#100685). Re-triggering CI. |
affbbb1 to
d367519
Compare
This sets developmentBranch to false for the release branch. We plan to backport this commit as soon as the branch is cut. Release note: none. Epic: REL-283
d367519 to
5fa823b
Compare
This PR sets developmentBranch to false, which must be set before selected a beta.1 candidate.
Release note: none.
Epic: REL-283
Release justification: Infra-only change. Denotes
release-23.1as a release branch/versions.Backport 1/4 commits from #99128.
/cc @cockroachdb/release
As part of the 23.1 stability period tasks, this PR preps the 23.1 release branch and initializes 23.2 development, as per this release runbook: Prep Release and Define Start of Development for Next Release.
This PR will contain 4 commits:
beta.1this week's alpha.8 candidateRelease note: none.
Epic: REL-283