Update WG-12-14.md #1181
Update WG-12-14.md #1181
Conversation
|
This seems fine to me if enough folks will be available / not on vacation. I think @conrad-watt will be gone already, not sure about @dtig. Do we want to ensure that @ericprud will be available too? |
|
Yes, I think this won't make much sense without @ericprud, since he apparently is the only one who understands and controls the process. :) Happy to push it to the next date if too many people can't make it. That would be the Jan 11th? |
|
Yes, January 11. That date would also work for me, let's see what some other folks say about their availability (I also forgot to @lukewagner in my last post) |
|
I'll be around for the 14th, but agree with @rossberg that we probably want @ericprud around for the discussion. I'm sometimes unable to participate actively during that time slot, and only have one question re. Wasm 2.0 so I'll just post here. We had previously decided that a CR should go out for every major version bump, is a CR needed for the 2.0 bump? It doesn't look like the previous CR covers the recent changes before the major version change. |
|
The last published version was on 19 April 2022. The evergreen approach allows for arbitrary (capricious) publication of CRs; I believe we said we'd do it whenever a proposal was merged (I don't see any in Finished Proposals) so we might want to gear up for more frequent publication. |
|
Actually, it turns out that I myself cannot make it next Wednesday. :-} So let's perhaps push to January. |
|
ok, I'll cancel tomorrow. @ericprud can you let us know how to find out our W3C rep's availability for January? |
|
I just got word that @plehegar will be taking over for me. It would probably make sense for both of us to attend the 11 Jan meeting. Plh, would that work for you? |
|
Yes, I'll be there |
|
I've updated the agenda for Jan 11 in #1192 |
No description provided.