Project/MilestonesHarvest

This page documents the information gathering effort related to W3C specification milestones.

Spreadsheet

The spreadsheet contains a set of columns, which are explained below.

All dates are using one of:

1. for well-defined dates, YYYY-MM-DD
2. for dates in the month range, YYYY-MM
3. for quarters, QN YYYY

Note: Milestone dates should be based on your best/latest knowledge. If those dates differ from the ones in the charter of the Group, add a note to indicate so in the Comments/notes column. If you and your Chair/Group disagree on what those milestones are, use yours and add a note to indicate so in the Comments/notes column.

/TR link

Latest published version of the document in https://www.w3.org/TR/.

If the document hasn't been published yet, use the editor's draft link.

FPWD

(First Public Working Draft)

Only fill this column if you used an editor's link in the /TR link column.

Wide review end

The Process says: The objective (of wide review) is to ensure that the entire set of stakeholders of the Web community, including the general public, have had adequate notice of the progress of the Working Group and were able to actually perform reviews of and provide comments on the specification.

Only fill this column if your document didn't reach PR or beyond.

Do fill this column if you have CR or PER milestones. It must be earlier than the CR or PER date. Keep in mind that asking for horizontal reviews less than one month before your move to CR is considered bad form. The earlier, the better.

This date might be in the past if the wide review already occurred.

CR

Only fill this column if your document isn't at least a Proposed Recommendation.

This is the date of the publication of your first CR publication. Don't use dates of your CR updates here.

This date might be in the past.

Test suite Status

One of:

1. none
2. started
3. medium
4. good
5. other

Good means good enough to make the Director happy and demonstrate adequate implementation experience. It does not mean that the test suite is perfect.

Only use other if you don't plan to use a test suite to demonstrate adequate implementation experience.

PR

(Proposed Recommendation)

The date of the Proposed Recommendation.

This date might be in the past.

PER

(Proposed Edited Recommendation)

The date of the Proposed Edited Recommendation (if applicable).

This date might be in the past.

REC

The upcoming date of the Recommendation.

This date must not in the past since we're not looking at past Recommendation publication in this spreadsheet. Nevertheless, congratulations if you already published a Recommendation in the past!

Comments & notes

If your milestones differ from the ones listed in the charter, please indicate so here (e.g. "these milestones supercedes the charter")

If your milestones are approved by the Working Group and/or the Chair, please indicate so here (e.g. "these milestones are mine and don't reflect consensus").

Comments are welcome in this column since we're looking at adjusting our information harvesting. It may well be that we ought to ask for more information and we aren't...

Critical Dependencies

If your milestones cannot be accomplished until an other document moves forward, please provide the /TR link of the other document(s) here or, if none, a link to the other document(s) wherever that is (e.g. IETF dependency).

Note that "critical" depends on the normative references considerations.

In doubt, provide a link and add a note in the Comments/notes indicating you're not sure.