Differences

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

--- spec:publish [2023/08/21 15:14] – [Step-by-step Publishing a CSS Spec] fantasai
+++ spec:publish [2023/08/21 15:55] (current) – [Step-by-step Publishing a CSS Spec] add abbrevitions fantasai
@@ Line 3: / Line 3: @@
   - **Summarize Changes -** Make a Changes section summarizing the major changes since the last publication. ("Major" is relative---for a CR, it's any non-editorial change, but for an early-stage WD it would be sections that got an overhaul, major syntactic changes, or major behavioral changes, not every minor detail that got fixed.) This will help reviewers focus their review.
-    - If there have been only [[https://www.w3.org/2019/Process-20190301/#correction-classes|editorial]] changes, make such a statement and, ideally, link to a [[https://services.w3.org/htmldiff|diff]] of those changes so reviewers can verify this. E.g. ''There have been only __editorial__ changes since the __previous Working Draft__; see __diffs__.''
+    * If there have been only [[https://www.w3.org/2019/Process-20190301/#correction-classes|editorial]] changes, make such a statement and, ideally, link to a [[https://services.w3.org/htmldiff|diff]] of those changes so reviewers can verify this. E.g. ''There have been only __editorial__ changes since the __previous Working Draft__; see __diffs__.''
-    - FPWD doesn't need a Changes section, since there's no previous version.
+    * FPWD doesn't need a Changes section, since there's no previous version.
   - **CSSWG Resolution -** Get an official CSSWG Resolution to publish. Make any changes requested.
-    - **For WD** if there are only non-controversial [[https://www.w3.org/2019/Process-20190301/#correction-classes|editorial]] changes and/or substantive changes approved by the WG, there is no requirement to get an explicit WG resolution. The decision URL is this wiki page, and you can publish using Echidna.
+    * **For WD** if there are only non-controversial [[https://www.w3.org/2019/Process-20190301/#correction-classes|editorial]] changes and/or substantive changes approved by the WG, there is no requirement to get an explicit WG resolution. The decision URL is this wiki page, and you can publish using Echidna.
-    - **For LCWD** (last Working Draft before a CR transition request), establish with the WG a deadline (3 weeks minimum, 4 is typical) and a list of other WGs to ask for comments. After publication, send a request for comments to all these groups and make sure that you [[https://www.w3.org/Guide/documentreview/|file all horizontal review requests]] if you haven't already.
+    * **For LCWD** (last Working Draft before a CR transition request), establish with the WG a deadline (3 weeks minimum, 4 is typical) and a list of other WGs to ask for comments. After publication, send a request for comments to all these groups and make sure that you [[https://www.w3.org/Guide/documentreview/|file all horizontal review requests]] if you haven't already.
   - **Prepare Draft -**
-    - Update the Previous Version link at the top to the latest dated URL on /TR (Omit or write "none" if there is none)
+    * Update the Previous Version link at the top to the latest dated URL on /TR (Omit or write "none" if there is none)
-    - [[http://validator.w3.org/|Validate]] Overview.html
+    * [[http://validator.w3.org/|Validate]] Overview.html
-    - [[http://www.w3.org/2009/07/webidl-check|WebIDL check]] Overview.html
+    * [[http://www.w3.org/2009/07/webidl-check|WebIDL check]] Overview.html
-    - [[http://validator.w3.org/checklink|Link-check]] your spec.
+    * [[http://validator.w3.org/checklink|Link-check]] your spec.
-    - run a spellchecker on your spec
+    * run a spellchecker on your spec
-    - 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 -**
-    - **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.
   - **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: