microsoft / microsoft/simplechat
Evaluate per-version release notes files
@paullizer is already working on this.
Since Jun 26, 2026.
- Dominant language
- Python
- Stars
- 152
- Forks
- 116
- Avg merge
- 7h 7m
- Merged PRs (30d)
- 122
Description
## Summary
Evaluate replacing or augmenting the single release notes file with per-version markdown files.
## Scope
- Preserve current public links, index/search behavior, and the latest-release docs workflow. Decide whether the single file becomes an index, generated aggregate, or legacy page.
- Validate links, screenshots, UI labels, and examples against the current SimpleChat experience.
- Keep tenant-specific secrets, IDs, and environment-specific values out of published examples.
## Acceptance Criteria
- [ ] Documentation or content covers the requested scope clearly.
- [ ] Relevant links, images, and examples are reviewed for accuracy.
- [ ] Any related existing feature documentation is linked instead of duplicated.
## Notes
- Source backlog entry: Release Notes By Version Folder
- Source file: priv-simplechat-2/grouped_feature_fix_backlog.md
- Backlog status: Docs / Content, Research
- Current anchors: `docs/explanation/release_notes.md`, `docs/latest-release/`
- Proposed roadmap priority: P2
- Proposed roadmap size: M
Contributor guide
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.