Reserve Sev 2 package withdrawal escalations for serious security issues - #48927
Open
Yuchao Yan (msyyc) wants to merge 2 commits into
Open
Reserve Sev 2 package withdrawal escalations for serious security issues#48927Yuchao Yan (msyyc) wants to merge 2 commits into
Yuchao Yan (msyyc) wants to merge 2 commits into
Conversation
Yuchao Yan (msyyc)
requested review from
a team and
Daniel Jurek (danieljurek)
as code owners
September 8, 2026 09:04
|
Azure Pipelines: Successfully started running 1 pipeline(s). 10 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The updated documentation line introduces a grammar/capitalization issue that should be corrected for clarity and consistency.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Updates the ESRP “break glass” guidance for urgent yank/delete requests by changing the escalation path from a Sev 2 ICM to a Sev 3 ICM.
Changes:
- Adjusted the documented escalation severity level for urgent ESRP-related requests (Sev 2 → Sev 3).
- Updated the corresponding line in the ESRP release process documentation.
File summaries
| File | Description |
|---|---|
| doc/esrp_release.md | Updates the documented escalation severity for urgent ESRP yank/delete requests. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
Yuchao Yan (msyyc)
changed the title
| For low priority yank requests, directly contact the `python` team via email @ `python@microsoft.com`. Ensure that the `package name`, the `version`, and the `yank reason` are readily available in the yank request email. | ||
|
|
||
| If there is no response on the email, and the request is urgent. escalate to filing a sev 2 ICM. The process is documented [here](https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/1035/ESRP-Release-Task?anchor=escalating-to-esrp). | ||
| If an urgent yank or deletion request remains unanswered by email, follow the [ESRP escalation process](https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/1035/ESRP-Release-Task?anchor=escalating-to-esrp) to file an ICM at severity 3, or severity 2 only if the request addresses a serious security issue. |
Member
Author
There was a problem hiding this comment.
Hi Daniel Jurek (@danieljurek) , please help take a review for docs update.
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.
related with https://github.com/Azure/azure-sdk-pr/issues/2684