More than this, the specification cannot go to Freeze (public review)
toggle quoted messageShow quoted text
until any SBI changes are in place.
One thing we might want to consider is having an "SBI approval"
process. That would allow SBI changes to be "upstreamed but not
released", and allow specifications to go to Freeze & Ratification
while they wait for the SBI changes to be released in the next version
This is no different than the upstreaming of things like GCC today. We
could make these changes to the process without changing the policy.
(no vote needed)
On Thu, Jun 2, 2022 at 8:06 AM mark <markhimelstein@...> wrote:
Just remember that something that depends on an SBI change can't get ratified until the SBI change is ratified.
If there is a roll up, there still needs to a TG governing it or it needs to be a fast track with the committee governing it and there needs to be a rat plan.
On Thu, Jun 2, 2022 at 7:38 AM Anup Patel <apatel@...> wrote:
On Thu, Jun 2, 2022 at 7:36 PM mark <markhimelstein@...> wrote:
My understanding is that different TGs or SIGs will propose their own
we have seen a number of SBI changes proposed (debug console, ap tee, ...).
will there be one big rev ala priv 1.12, small fast tracks , something else?
I also suggest that this either needs to be run out of the priv sw HC or convene a new TG. Can we conduct this conversation there (and create the appropriate group or committee mail aliases).
SBI extensions. Once a set of changes for next SBI spec release are
finalized, the SBI TG can collect all new SBI extensions and prepare a
draft of the next SBI spec. It will be the responsibility of SBI TG to
complete the ratification process.
Is this understanding correct ?
sent from a mobile device. please forgive any typos.