-
Notifications
You must be signed in to change notification settings - Fork 4k
Closed
Labels
C-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)GA-blockerT-sql-queriesSQL Queries TeamSQL Queries Teambranch-release-25.4Used to mark GA and release blockers and technical advisories for 25.4Used to mark GA and release blockers and technical advisories for 25.4
Description
Part of #153300 for DB teams to go through the upgrade compatibility checklist for 25.4.
Upgrade compatibility requirements for 25.4
25.4 must be upgradeable from both 25.2 and 25.3
Checklist Sign-off for 25.4
Checklist
[from doc: Upgrade compatibility checklist for 25.4. Tip: one way to review the checklist could be to integrate it into the team pre-mortem, with EMs and TLs signing-off that this has been reviewed with the team.]
New Functionality:
- Has upgrade compatibility from both 25.2 and 25.3 been considered in your team pre-mortem?
- Has the team introduced any migrations or version gates?
- Have you tested all your migrations in upgrades from 25.2 and 25.3?
- Have you tested all your version gates and related logic?
- Has upgrade and mixed-version functionality (mixed versions including 25.2, 25.3 and 25.4) been tested against new functionality [1]?
Existing Functionality:
- Have you pulled out any 25.3 code (since May 2025) that could potentially impact upgrades or mixed-version functionality?
- (if so, has this been resolved to support upgrade compatibility?)
- Have you made any changes to existing functionality that could misbehave on a cluster created at an arbitrarily old version (either after upgrade to 25.4, or in a mixed cluster with some 25.2 or 25.3 nodes)?
[1] Note that there are a ton of other ways to break upgrades, ways that may not even use any migrations or version gates. e.g. Storage team recently made a fix to the Pebble comparator (related to a now obsolete flag) which lead to inconsistent replica crashes on a 24.2 cluster
Jira issue: CRDB-54341
Metadata
Metadata
Assignees
Labels
C-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)GA-blockerT-sql-queriesSQL Queries TeamSQL Queries Teambranch-release-25.4Used to mark GA and release blockers and technical advisories for 25.4Used to mark GA and release blockers and technical advisories for 25.4
Type
Projects
Status
Done