-
Notifications
You must be signed in to change notification settings - Fork 4.1k
clusterversion: bump binaryMinSupportedVersion to 23.1 #111760
Copy link
Copy link
Closed
Labels
A-releaseC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-releaseRelease Engineering & Automation TeamRelease Engineering & Automation Teambranch-release-23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2
Metadata
Metadata
Assignees
Labels
A-releaseC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-releaseRelease Engineering & Automation TeamRelease Engineering & Automation Teambranch-release-23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2
We need to bump binaryMinSupportedVersion to 23.1 before we release the first 23.2 beta (branch cut is currently scheduled for Oct 10).
TODO:
TODODelete_prefix or something, so when teams see if in the code they know they can clean up related code.Also tracked in https://cockroachlabs.atlassian.net/browse/REL-506
Jira issue: CRDB-32062