Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document (sometimes) required metadata for implementation report and CR deadline #2765

Closed
wants to merge 3 commits into from
Closed

Document (sometimes) required metadata for implementation report and CR deadline #2765

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
178fa41
W3C Process requires CR Snapshot to have a deadline, #2644
svgeesus Jan 13, 2024
1784582
Document Implementation Report, #2645
svgeesus Jan 13, 2024
3f1b29d
Generate html as required (needed -f, though)
svgeesus Jan 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion docs/index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1211,7 +1211,7 @@ There are several additional optional keys:
* <dfn>Status Text</dfn> allows adding an additional customized sentence that can be used in the document status section.
* <dfn>Ignored Terms</dfn> accepts a comma-separated list of terms and makes Bikeshed not emit warnings or errors when attempting to autolink those terms. Use this to quiet spurious preprocessor warnings caused by you inventing terms (for example, the Variables spec invents custom properties like 'var-foo'), or as a temporary patch when the spec you want to link to doesn't set up its definitions correctly.
* <dfn>Date</dfn> must contain a date in YYYY-MM-DD format, which is used instead of today's date for all the date-related stuff in the spec. Alternately it can contain the string `now`, which explicitly indicates a date of precisely when the output is generated.
* <dfn>Deadline</dfn> is also a YYYY-MM-DD date, which is used for things like the LCWD Status section, to indicate deadlines.
* <dfn>Deadline</dfn> is also a YYYY-MM-DD date, which is used for things like the LCWD and <a href="https://www.w3.org/pubrules/doc/rules/?profile=CR#reviewEndDate">CR Snapshot</a> Status section, to indicate deadlines.
* <dfn>Expires</dfn> is also a YYYY-MM-DD date,
or can be the string `now` to indicate today's date,
or can be an "ISO Duration" like `P1Y` to indicate "+1 year"
Expand All @@ -1231,6 +1231,11 @@ There are several additional optional keys:
as linked text.
To display WPT results,
see [[#testing]].
* <dfn>Implementation Report</dfn> must contain a link to
an implementation report, either a hand-written document
or just a link to the spec's folder on wpt.fyi.
This is <a href="https://www.w3.org/pubrules/doc/rules/?profile=CR#implReport">required
for W3C Candidate Recommendation Snapshot</a>.
* <dfn>Mailing List</dfn> must contain an email address to be used for mailing lists.
* <dfn>Mailing List Archives</dfn> must contain a link to the list archives.
* <dfn>Issue Tracking</dfn> indicates what and where you track issues,
Expand Down
Loading