[tooling] Script to test compatiblity between releases - #1624
Open
the-glu wants to merge 1 commit into
Open
Conversation
the-glu
force-pushed
the
release_compact_script
branch
from
August 12, 2026 07:14
b495d95 to
1a6ced6
Compare
the-glu
marked this pull request as draft
August 12, 2026 13:34
the-glu
force-pushed
the
release_compact_script
branch
from
August 19, 2026 08:18
1a6ced6 to
ebdacab
Compare
the-glu
marked this pull request as ready for review
August 19, 2026 08:19
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contribute to #1598 by proving an helper script who test compatibility between a list of DSS release.
Each pair is tested, with latest migration of each member of the pair tested.
Related documentation will come in sibling PRs.
The following output is produced with an old monitoring image:
The following matrix shows what is possible when a user wants to upgrade a pool on version A (rows) to
version B (columns).
The table always assumes a migration to the latest schema of the target version B prior to DSS version upgrade per "Rolling upgrade procedure" below. Where this cannot be accomplished (e.g., DSS version X cannot function with the latest schema of DSS version X+1), the transition will be indicated as incompatible.
✅ compatible · ⚠ degraded, see explanation below · ❌ incompatible · ⚪ not evaluated
1Some tests in a multi-version pool may fail due to improvements in the test suite and DSS behavior.