[Docs] Deprecation policy, SDK tier target, and CONTRIBUTING.md - #472
Open
chr-hertel wants to merge 8 commits into
Open
[Docs] Deprecation policy, SDK tier target, and CONTRIBUTING.md#472chr-hertel wants to merge 8 commits into
chr-hertel wants to merge 8 commits into
Conversation
Formalizes the Active -> Deprecated -> Removed lifecycle and the twelve-month deprecation window the SDK already applies via SEP-2577, and states the SDK's own BC promise ahead of 1.0.
Adds both pages under a new Project section in mkdocs.yml, links them from index.md's "Where to go next", and points their repo-root references at GitHub URLs instead of paths escaping docs/ (dead under Zensical's --strict build).
Root-level contribution guide: dev setup, the make ci checks to run before a PR, coding standards, testing expectations, the docs-guide link-resolution rule Zensical enforces, and licensing terms. Linked from README's existing Contributing section.
chr-hertel
requested review from
CodeWithKyrian,
Nyholm and
soyuka
as code owners
August 22, 2026 00:11
chr-hertel
commented
Aug 22, 2026
chr-hertel
commented
Aug 22, 2026
chr-hertel
commented
Aug 22, 2026
Drop the worked SEP-2577 example and the "relationship to the protocol lifecycle" section; both were redundant restating of detail that lives in the code/CHANGELOG and protocol-versions.md already.
Replace our own hand-rolled conformance numbers with the authoritative audit in modelcontextprotocol/modelcontextprotocol#3274: SDK is currently Tier 3, blocked from Tier 2 by client OAuth conformance (20%) and no stable 1.0.0+ release. Add the Versioning section the audit found missing — SemVer commitment pre-1.0, Symfony's BC promise after — and point CONTRIBUTING.md at it.
Was plain text; sdk-tier.md's Versioning section already links it.
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.
Summary
docs/deprecation-policy.md(SEP-2596): the Active → Deprecated → Removed lifecycle, the twelve-month window, and the@deprecatedtag convention already in use since SEP-2577 ([Schema][Client][Server] Deprecate Roots, Sampling and Logging (SEP-2577) #427). Closes [Docs] SEP-2596: Adopt MCP feature lifecycle policy; document PHP SDK BC promise mirroring 12-month spec window #366.docs/sdk-tier.md(SEP-1730): gap analysis against the Tier 2 bar. Server conformance is ~99%/98%; client conformance is only 20%/5% — flagged as the real gap, not a docs one. Closes [Meta] SEP-1730: Target SDK Tier 2 classification — gap analysis, roadmap, dependency policy #368.mkdocs.yml's nav under a new Project section, and links them fromindex.md's "Where to go next". Fixes two links insdk-tier.mdthat pointed at repo-root files via a path escapingdocs/— dead under Zensical's--strictbuild ([Docs] Render the guides with Zensical instead of phpDocumentor #414); pointed them at GitHub URLs instead, matching the existing convention.CONTRIBUTING.mdat the repo root — dev setup, themake cichecks to run before a PR, coding standards, testing expectations, the docs-guide link-resolution rule Zensical enforces, and licensing terms. Linked from README's Contributing section.Test plan
make docs-guides(Zensical--strictbuild) — no issues foundvendor/bin/phpstan analyse— no errorsvendor/bin/php-cs-fixer fix --dry-run --diff— 0 files need fixing