This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
spec:publish [2018/05/09 22:11] – florian | spec:publish [2020/06/03 16:09] – [START HERE] chrisl | ||
---|---|---|---|
Line 2: | Line 2: | ||
Note! There have been changes to the module template since it was written! Check the [[http:// | Note! There have been changes to the module template since it was written! Check the [[http:// | ||
+ | |||
+ | ===== START HERE ===== | ||
+ | |||
- **Summarize Changes -** Make a Changes section summarizing the major changes since the last publication. (" | - **Summarize Changes -** Make a Changes section summarizing the major changes since the last publication. (" | ||
+ | - If there have been only [[https:// | ||
- **CSSWG Resolution -** Get an official CSSWG Resolution to publish. Make any changes requested. | - **CSSWG Resolution -** Get an official CSSWG Resolution to publish. Make any changes requested. | ||
- | - **For LCWD**, establish with the WG a deadline (3 weeks minimum, 4 is typical) and a list of other WGs to ask for comments. Let a chair or staff contact inform those WGs, and all other WGs (via chairs@w3.org) of the upcoming last call and give them a few days to ask for a different deadline. | + | |
+ | | ||
- **Prepare Draft -** | - **Prepare Draft -** | ||
- Update the Previous Version link at the top to the latest dated URL on /TR (Omit or write " | - Update the Previous Version link at the top to the latest dated URL on /TR (Omit or write " | ||
Line 14: | Line 19: | ||
- Optional: If you feel so inclined, you can use [[https:// | - Optional: If you feel so inclined, you can use [[https:// | ||
- **Request Publication -** | - **Request Publication -** | ||
- | - **For regular Working Drafts** on Bikeshed-formatted specs, you can use the '' | + | - **For regular Working Drafts** on Bikeshed-formatted specs, you can generally |
- | | + | - **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:// |
- | - **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 CR, etc.** See [[https:// |
- **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 -** Post an announcement of your new spec to [[mailto: | + | - **Announce Your Spec -** If there were substantial changes since the previous draft, post an announcement of your new spec to [[mailto: |
* A link to the spec | * A link to the spec | ||
* An explanation of what's new, what's cool, what's changed, maybe what to expect going forward, but most importantly what you would especially like feedback on. | * An explanation of what's new, what's cool, what's changed, maybe what to expect going forward, but most importantly what you would especially like feedback on. | ||
Line 108: | Line 113: | ||
Disposition of comments: | Disposition of comments: | ||
| | ||
- | !!!http:// | + | !!!http:// |
| | ||
Please review the draft, and send any comments to this mailing list, | Please review the draft, and send any comments to this mailing list, |