microsoft / microsoft/documentdb-mcp
[Positioning] Publish public roadmap
Open
@khelanmodi is already working on this.
Since May 13, 2026.
documentation
positioning
tier-2
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 4
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 3
Description
Goal
External visibility into what's shipping when.
What to ship
A ROADMAP.md at repo root (or GitHub Projects board, public), with:
- Public preview milestones (what's in / out).
- v1 / GA criteria.
- Known gaps deliberately deferred.
- Link to
docs/release-readiness-check.mdanddocs/gaps-on-rbac.mdfor the technical detail.
Group by:
- Preview (current): what's shipping.
- v1: blocking GA.
- Future: tracked but not committed.
Acceptance criteria
- Updated at every release.
- Reviewed by PM.
- Linked from README and from
aka.ms/documentDBMCPToolkitlanding.
Depends on
- All four Positioning Decisions.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.