| Both sides previous revisionPrevious revision | |
| spec:publish [2023/08/21 15:54] – [Step-by-step Publishing a CSS Spec] switch to bullets fantasai | spec:publish [2023/08/21 15:55] (current) – [Step-by-step Publishing a CSS Spec] add abbrevitions fantasai |
|---|
| * 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 and Candidate Recommendation Drafts** on Bikeshed-formatted specs, you can generally **use the ''[[https://tabatkins.github.io/bikeshed/#cli-echidna|bikeshed echidna]]'' command**. (Don't forget to [[https://tabatkins.github.io/bikeshed/#metadata-status|set the status]] first.) If you need to publish manually for some reason (non-Bikeshed specs, spec shortname changes, other weirdness), see [[#steps-for-manual-publication]]. | * **For regular Working Drafts (WD) and Candidate Recommendation Drafts (CRD) ** on Bikeshed-formatted specs, you can generally **use the ''[[https://tabatkins.github.io/bikeshed/#cli-echidna|bikeshed echidna]]'' command**. (Don't forget to [[https://tabatkins.github.io/bikeshed/#metadata-status|set the status]] first.) If you need to publish manually for some reason (non-Bikeshed specs, spec shortname changes, other weirdness), see [[#steps-for-manual-publication]]. |
| * **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 the manual publication request. Best way to do this is to [[https://github.com/w3c/transitions|file an issue in the Transitions repo]]. The Team will publish the FPWD. | * **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 the manual publication request. Best way to do this is to [[https://github.com/w3c/transitions|file an issue in the Transitions repo]]. The Team will publish the FPWD. |
| * **For CR (Candidate Recommendation Snapshot), PR, REC ** 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. The Team will publish the spec and send out relevant announcements. | * **For Candidate Recommendation Snapshots (CRS), PR, REC ** See [[https://www.w3.org/Guide/transitions|Spec Status Transitions Documentation]]. You will 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. The Team will publish the spec and send out relevant announcements. |
| - **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. |
| - **Announce Your Spec -** If there were substantial changes since the previous draft, post an announcement of your new spec to [[mailto:www-style@w3.org|www-style]] (and cross-post to [[mailto:public-review-announce@w3.org|public-review-announce]] and any other relevant mailing lists) and the [[https://www.w3.org/blog/CSS/wp-admin/|CSSWG Blog]] (See Templates Below) and link the blog post from [[http://twitter.com/csswg|@csswg]]. If you need help with this, ask fantasai. A good announcement includes: | - **Announce Your Spec -** If there were substantial changes since the previous draft, post an announcement of your new spec to [[mailto:www-style@w3.org|www-style]] (and cross-post to [[mailto:public-review-announce@w3.org|public-review-announce]] and any other relevant mailing lists) and the [[https://www.w3.org/blog/CSS/wp-admin/|CSSWG Blog]] (See Templates Below) and link the blog post from [[http://twitter.com/csswg|@csswg]]. If you need help with this, ask fantasai. A good announcement includes: |
