Getting Team verification for a new W3C maturity level (aka transition requests)

For all requests to advance a specification to a new maturity level other than [Note](), the Working Group must obtain Team verification. This is a repository for managing the verification workflow when advancing on the W3C Recommendation track. It contains the transition requirements document, available from Organize a Technical Report Transition, and an issues tracker for managing transition requests. Tags are used to manage the transitions, keeping track of who has the “ball”. Notifications are sent by email to various mailing lists, include public-transition-announce and chairs.

Select one of the transition templates below:

• First Public Working Draft: FPWD transition
• Ordinary Working Draft: no Director's approval needed, just use Echidna.
• Transitioning to Candidate Recommendation: CR transition
• Publishing a Candidate Recommendation Draft: no Team verification needed, just use Echidna.
• Updating a Candidate Recommendation Snapshot: Updated CR transition
• Proposed Recommendation: PR transition
• Proposal to Supersede a Recommendation: Superseded transition
• Proposal to Obsolete a Recommendation: Obsoleted transition
• Recommendation: Due to the need to look at the AC Review comments, those transitions are done by the Team separately. But the Team does still track those requests in transition issues.
• Recommendation with new candidate amendments: no Team verification needed, send publication request to webreq@w3.org.
• Recommendation with new proposed amendments: Update a Recommendation.
• Recommendation that is making proposed amendments normative: Recommendation Track - Update a Recommendation
• First Public Draft Note: First publication of a Group Note or Draft Group Note
• Ordinary Draft Group Note: no Team verification needed, just use Echidna.
• First Public Note: First publication of a Group Note or Draft Group Note
• Ordinary Group Note: no Team verification needed, just use Echidna.
• Statement with new candidate amendments: no Team verification needed, send publication request to webreq@w3.org.
• Statement with new proposed amendments: no Team verification needed, send publication request to webreq@w3.org.
• Statement that is making proposed amendments normative: Updating a W3C Statement
• Statement: W3C Statement
• First Draft Registry: First publication of a Draft Registry
• Ordinary Draft Registry: no Team verification needed, just use Echidna.
• Transitioning to Candidate Registry: Candidate Registry
• Transitioning to Registry: Registry
• Updating a Candidate Registry Snapshot: Candidate Registry Snapshot
• Registry with new candidate amendments: no Team verification needed, send publication request to webreq@w3.org.
• Registry with new proposed amendments: no Team verification needed, send publication request to webreq@w3.org.
• Registry that is making proposed amendments normative: Updating a W3C Registry

For the Note and Registry tracks, use these templates

If you're not sure what transition template to use, check out our next step finder to see your choices.

Further Guidance

• Start with Organize a Technical Report Transition for more detailed guidance on how to complete the templates.
• If you need to convey Member-confidential information, start a thread on w3c-archive@w3.org and link it from your issue; lists.w3.org's access control will manage permissions. Use w3t-archive@w3.org instead for Team-confidential infos.
• Assign your editor(s) and staff contact(s) to the transition request issue to facilitate automatic pestering.
• Untag "Awaiting ..." if you intend to continue editing the issue before requesting action; you will need to add these back later.
• Issues get closed once publication is complete and relevant announcements are posted.

How does the monitoring work?

You may add your own hook to get those notifications.

This repository is monitored using transition-issues-bot.