From a35131fff2b4fac719f74e0a70eaf99801e919db Mon Sep 17 00:00:00 2001 From: Yuchao Yan Date: Tue, 8 Sep 2026 17:02:50 +0800 Subject: [PATCH 1/2] Update escalation severity from sev 2 to sev 3 --- doc/esrp_release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/esrp_release.md b/doc/esrp_release.md index 22c8b4298275..ba9c6abe3708 100644 --- a/doc/esrp_release.md +++ b/doc/esrp_release.md @@ -12,4 +12,4 @@ Further details on ESRP release methods is available at [docs.opensource.microso 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 there is no response on the email, and the request is urgent. escalate to filing a sev 3 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). From 396e940e051fd71fb8192d530b3ef3a04bf666df Mon Sep 17 00:00:00 2001 From: Yuchao Yan Date: Tue, 8 Sep 2026 17:20:42 +0800 Subject: [PATCH 2/2] Clarify ICM severity for package withdrawal requests --- doc/esrp_release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/esrp_release.md b/doc/esrp_release.md index ba9c6abe3708..7df928514785 100644 --- a/doc/esrp_release.md +++ b/doc/esrp_release.md @@ -12,4 +12,4 @@ Further details on ESRP release methods is available at [docs.opensource.microso 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 3 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.