[2026-07-28] Governance: deprecations, lifecycle, conformance, SDK tier

未关闭

#339 创建于 2026年5月26日 0 条评论 0 个 reaction 已指派 0 人在 GitHub 查看

还没有人认领这个 Issue。

评估

难度: 5/5
预计耗时: 一周以上
新手友好度: 25/100

Issue 类型: 功能
描述清晰度: 基本清楚
活跃度: 冷清
技术栈: php
领域: developer-experience, documentation, testing-qa

调研方向

从子议题 #365–#368 及其中链接的 SEP 材料开始，尤其关注议题中提到的 conformance test runner 和 PHP SDK BC 承诺。完成意味着完成四项治理任务：弃用通知和迁移文档、生命周期采纳、conformance tests 中的 SEP 可追溯性，以及 SDK Tier 2 的差距分析和路线图。

由索引模型根据 Issue 内容生成。

描述

2026-07-28 Client documentation enhancement improves spec compliance Server

Tracking issue for the MCP Spec 2026-07-28 release — Governance & lifecycle milestone.

Coherent governance bundle: lifecycle policy (2596) governs what gets deprecated, conformance tests (2484) gate when SEPs go Final, and SDK tiers (1730) measure how well each SDK keeps up. SEP-2577 is the first concrete deprecation pass under the new policy.

SEPs covered

SEP	Title	Spec PR
SEP-2577	Deprecate Roots, Sampling, and Logging	#2577
SEP-2596	Feature Lifecycle and Deprecation Policy	#2596
SEP-2484	Conformance Tests required for Final status	#2484
SEP-1730	SDK Tiers definition	#1777

Sub-issues

#365 — SEP-2577: Mark Roots/Sampling/Logging @deprecated, emit notices, document migration
#366 — SEP-2596: Adopt MCP feature lifecycle policy; document PHP SDK BC promise
#367 — SEP-2484: Wire SEP traceability files into conformance test runner
#368 — SEP-1730: Target SDK Tier 2 classification — gap analysis, roadmap, dependency policy

Notes

All four SEPs are merged.
SEP-2577: implementations of Roots/Sampling/Logging stay — only public APIs gain @deprecated, plus runtime notices. Minimum 12-month removal window per SEP-2596.
SEP-1730: realistic target is Tier 2 immediately, Tier 1 post-1.0.

主要语言: PHP
星标: 1.6k
派生: 173
平均合并: 2 天 49 分钟
30 天内合并 PR: 23