Skip to content

DOC: Add patch release guide to release process#1585

Open
romanlutz wants to merge 4 commits intomicrosoft:mainfrom
romanlutz:doc/patch-release-guide
Open

DOC: Add patch release guide to release process#1585
romanlutz wants to merge 4 commits intomicrosoft:mainfrom
romanlutz:doc/patch-release-guide

Conversation

@romanlutz
Copy link
Copy Markdown
Contributor

Add an appendix explaining cherry-pick-based patch releases, covering when to use them, the abbreviated steps, and key differences from regular releases.

romanlutz and others added 2 commits April 9, 2026 15:42
Add an appendix explaining cherry-pick-based patch releases,
covering when to use them, the abbreviated steps, and key
differences from regular releases.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copy link
Copy Markdown
Contributor

@hannahwestra25 hannahwestra25 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for adding! the only thing that i might add is what to do for release notes (ik it's in the 10th step but I'm assuming it would look a little different / should highlight the reason for the patch ?)

romanlutz and others added 2 commits April 10, 2026 10:32
Co-authored-by: jsong468 <songjustin@microsoft.com>
Address review feedback: clarify that patch release notes should
highlight the specific reason for the patch (security fix, critical
bug, etc.) and will be shorter than regular release notes.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants