Repository navigation
docs: publish canonical xerial conformance statement - #181
Merged
magnusp merged 1 commit intoOct 24, 2026
Merged
Conversation
magnusp
force-pushed
the
docs/171-conformance-statement
branch
from
October 23, 2026 23:35
16e220d to
562beb3
Compare
magnusp
force-pushed
the
docs/171-conformance-statement
branch
from
October 23, 2026 23:40
562beb3 to
7684661
Compare
magnusp
force-pushed
the
docs/171-conformance-statement
branch
from
October 23, 2026 23:47
7684661 to
515dcdd
Compare
magnusp
force-pushed
the
docs/171-conformance-statement
branch
from
October 24, 2026 00:08
515dcdd to
65270da
Compare
magnusp
force-pushed
the
docs/171-conformance-statement
branch
from
October 24, 2026 00:12
65270da to
32910bf
Compare
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
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.
Why
There is no single document that answers whether the driver has reached xerial conformance, and the answer was scattered across the conformance module, the vendored manifest, agent guidance, and the closed parity queue.
What changed
Scope
Tradeoffs
Blast Radius
Verification
./mvnw spotless:check: BUILD SUCCESS.