Stabilization Exception Process - SLA for a SIG approval?

[tonybalandiuk]

This came up in the 4/11/2023 sig-release meeting when discussing the stabilization process and the steps in obtaining approvals for an exception. Recall that in order to submit new features into stabilization (and in order to submit lower priority bugs later in the stabilization period) you need to get this checklist filled out.

Question: In the checklist, after a sig has been notified, should we have a timeframe by which they need to give their approval (e.g. N hours from being notified)? In essence this is Service Level Agreement (SLA).

If they do not meet the SLA then the exception may move forward based on X.

Looking for feedback here on
What does everyone think?
If we want an SLA, then what are N, X?
Is there another way to phrase this that we would prefer, other than an SLA? if so, what?

[tonybalandiuk]

I'll start. This could read something like
"SIGs should ideally respond within 12 hours. If they do not respond within 12 hours, then their approval can be skipped if chairs/co-chairs from 2 other SIGs agree: One sig must be SIG-Release."