guide: document embargoed security releases - #4152
Merged
Ben Hillis (benhillis) merged 1 commit intoAug 5, 2026
Merged
Conversation
Describe MSRC-coordinated private fix development, qualified downstream patch sharing, and coordinated patch-version source releases. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 4fe65aa5-d620-4856-a525-e32bf98c16b1
Contributor
There was a problem hiding this comment.
Pull request overview
Adds Guide documentation for handling embargoed security fixes and coordinated disclosure, clarifying how OpenVMM should accept private vulnerability reports and publish security releases while keeping internal operational details out of the public Guide.
Changes:
- Add a new “Security Releases” contributor-guide page describing private reporting via MSRC, embargoed fix development, downstream coordination, and coordinated disclosure.
- Add the new page to
SUMMARY.mdnavigation under Contributing. - Cross-link from the existing release management page to the new security releases guidance.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| Guide/src/SUMMARY.md | Adds the new “Security Releases” page to the Contributing section navigation. |
| Guide/src/dev_guide/contrib/security_releases.md | New policy page documenting private vulnerability reporting, embargo handling, downstream coordination, and disclosure steps. |
| Guide/src/dev_guide/contrib/release.md | Adds a “See also” admonish link pointing readers to the new security releases page. |
Steven Malis (smalis-msft)
approved these changes
Aug 4, 2026
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
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
Context
This is a draft policy for team and downstream consensus. It assumes the source-only, manually published standalone release model proposed in #4150; it does not add or change release implementation.
Questions for reviewers