As per the 2024-06-13 WASI SG meeting: the timezone extension to wasi:clocks already meets the phase 2 criteria by virtue of being part of an existing phase 3 proposal. It should have been introduced at phase 2, not phase 0. This allows it to be introduced as @unstable and be implemented by runtimes, but still needs a vote before it can be stabilized behind an @since gate.
I'll file a follow-up PR to clarify the process changes to existing proposals should go through, so we can follow this same process for other changes too.
As per the 2024-06-13 WASI SG meeting: the timezone extension to
wasi:clocksalready meets the phase 2 criteria by virtue of being part of an existing phase 3 proposal. It should have been introduced at phase 2, not phase 0. This allows it to be introduced as@unstableand be implemented by runtimes, but still needs a vote before it can be stabilized behind an@sincegate.I'll file a follow-up PR to clarify the process changes to existing proposals should go through, so we can follow this same process for other changes too.