[meta] Publish a new Working Draft

[anssiko]

There has been some substantial changes to the latest Editor's Draft since the previous Working Draft was published, so we should publish a new WD.

@fhirsch @dontcallmedom, should we issue a CfC or just go ahead and publish using the amazing bikeshed echidna integration?

Related question (not blocking this publication): @tobie, where are we in terms of the Level 1 milestone? Has the current list been triaged already (see action-785)? Regardless, I think we want to publish a new WD now and do another publication when the Level 1s have been addressed.

[dontcallmedom]

no CfC needed from my perspective - there was agreement from the group to auto-publish spec updates a while back

[anssiko]

@dontcallmedom, thanks for the confirmation.

@tobie, could you please cast the bikeshed echidna magic spell?

[fhirsch]

no CfC needed. Publish Working Drafts early and often.

[anssiko]

@tobie, let's publish immediately after #191 lands. Or better, setup automatic publishing on each commit.

[tobie]

Or better, setup automatic publishing on each commit.

See #74

[anssiko]

OK, then let's just publish with your echidna.sh (btw. what does the undocumented --self-contained switch do, I did not use it for other specs, what did I miss?)

[anssiko]

#191 landed. Should land #190 as well before the new Working Draft publication to make the mitigation strategies sections more complete.

@tobie, I assigned #190 to you and expect it to land soon given you seemed to have a clear vision where you wanted to take it.

[tobie]

Blocked on speced/bikeshed#1029.

[anssiko]

Thanks!