- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Tue, 15 Sep 2020 10:47:07 +0200
- To: spec-prod <spec-prod@w3.org>
Le 15/09/2020 à 10:06, Denis Ah-Kang a écrit : > The process document 2020 is effective starting from today. As > such, pubrules [1] has been updated to handle the new types of > Candidate Recommendations and to check the wording proposed > in the mockups Philippe shared below. > You can always refer to [2] if you need details on what > pubrules is checking for each type of documents. > > Dom has submitted PRs for respec [3] and bikeshed [4] to > help with the transition to the new process document. The ReSpec upgrade comes with 5 new configuration options. Generic option: * wgPatentPolicy: which patent policy the group operates under, PP2017 or PP2020 - between now and January, most groups are expected to migrate to PP2020. If you're using the "group" configuration option, this is set automatically for you https://github.com/w3c/respec/wiki/group Living standard option: * lsMode: if you expect your spec to be a living standard in CR (rather than targeting Recommendation status), set this option to true and it will adapt the SOTD accordingly Rec-specific options: * revisionTypes: in Process 2020, Recommendations can be published with two types of substantive updates: corrections and additions; revisionTypes is an array that can take "correction" and/or "addition" values to mark a given Rec as having these types of revisions * updateableRec: in Process 2020, starting from Proposed Rec, a spec needs to be marked as updateable to allow for future in-line updates to the Rec; this configuration option needs to be set to true to trigger the right wording in the SOTD * revisedRecEnd: when a Rec gets in-line normative updates, it needs to be approved by the Advisory Committee during a 4 weeks review - this configuration option defines the deadline of that review (using the usual YYYY-MM-VV format) Since bikeshed for the most part doesn't manage SOTDs, the equivalent wording changes there will have to be handled manually by the groups; the bikeshed upgrade does contain a new requirement to set the new implementationReport metadata key from CR onwards. Dom [3] https://github.com/w3c/respec/pull/3096 [4] https://github.com/tabatkins/bikeshed/pull/1760
Received on Tuesday, 15 September 2020 08:47:11 UTC