Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
spec:publish [2018/07/17 15:11]
fantasai [Step-by-step Publishing a CSS Spec]
spec:publish [2018/07/17 15:14] (current)
fantasai [Step-by-step Publishing a CSS Spec]
Line 14: Line 14:
     - Optional: If you feel so inclined, you can use [[https://​labs.w3.org/​pubrules/​|the new pubrules checker]] (if it's working), review its results, and correct any errors. (Some errors are expected/​harmless if you check an editor'​s draft, so read carefully!)     - Optional: If you feel so inclined, you can use [[https://​labs.w3.org/​pubrules/​|the new pubrules checker]] (if it's working), review its results, and correct any errors. (Some errors are expected/​harmless if you check an editor'​s draft, so read carefully!)
   - **Request Publication -**   - **Request Publication -**
-    - **For regular Working Drafts** on Bikeshed-formatted specs, you can use the ''​bikeshed echidna''​ command. ​Otherwise, send a message (See Template Below) to ChrisL and webreq, CCing w3c-css-wg, asking them to put your spec in the publication pipeline. Include a link to your draft and to the minutes with the resolution to publish. Put ''​[Publish]''​ in the subject line. +    - **For regular Working Drafts** on Bikeshed-formatted specs, you can generally ​use the ''​[[https://​tabatkins.github.io/​bikeshed/#cli-echidna|bikeshed echidna]]''​ command. ​If you need to publish manually for some reason (non-Bikeshed specsspec shortname changes, FPWD) send a message (See Template Below) to ChrisL and webreq, CCing w3c-css-wg, asking them to put your spec in the publication pipeline. Include a link to your draft and to the minutes with the resolution to publish. Put ''​[Publish]''​ in the subject line. 
-    - **For FPWD**, you also need a resolution on the shortname of the spec, and need the W3C domain leader (plh, in our case) to approve the FPWD publication and the choice of URL.+    - **For FPWD**, you also need a resolution on the shortname of the spec, and need the W3C domain leader (plh, in our case) to approve the FPWD publication and the choice of URL before requesting manual publication.
     - **For CR, etc.** See [[https://​www.w3.org/​Guide/​transitions|Spec Status Transitions Documentation]]. You may need to file an issue in the [[https://​github.com/​w3c/​transitions|Transitions Repo]]; ask ChrisL or fantasai for guidance and complain at plh for any poor documentation.     - **For CR, etc.** See [[https://​www.w3.org/​Guide/​transitions|Spec Status Transitions Documentation]]. You may need to file an issue in the [[https://​github.com/​w3c/​transitions|Transitions Repo]]; ask ChrisL or fantasai for guidance and complain at plh for any poor documentation.
   - **Wait for Publication -** Wait for the spec to be published. For Echidna-published specs, this should take a few minutes. For other specs, W3C publishes on Tuesdays and Thursdays once webreq has approved the publication.   - **Wait for Publication -** Wait for the spec to be published. For Echidna-published specs, this should take a few minutes. For other specs, W3C publishes on Tuesdays and Thursdays once webreq has approved the publication.
 
spec/publish.txt · Last modified: 2018/07/17 15:14 by fantasai
Recent changes RSS feed Valid XHTML 1.0 Valid CSS Driven by DokuWiki