- From: Atsushi Shimono (W3C Team) <atsushi@w3.org>
- Date: Thu, 1 May 2025 02:24:13 +0900
- To: "public-tt@w3.org" <public-tt@w3.org>
- Message-ID: <91825499-8029-4275-aeb4-a36bb69868b3@w3.org>
hi, sorry for late catch, due to overflow... On 2025/03/28 1:15, Nigel Megitt wrote: > DAPT > CRD auto-publication > Cyril: No problem pushing changes - does it impact the earliest > CR exit date? > Nigel: No it doesn't. > … However it's a good question, will check offline. Could be > that we can > … only request CR exit from a CRS, and if a CRS requires a new > exit date then it might have that impact. CRD is similar one to WD by means having draft state, and does not have an official state on publication process. So, the only formal step is CRS but not CRD, and "no substantive change requirement from last CRS" is placed to advance into next step: https://www.w3.org/policies/process/20231103/#transition-pr > must not have made any substantive changes to the document since the most > recent Candidate Recommendation Snapshot, other than dropping features > identified at risk. Also a diagram in rec-track shows CRD can only transition into CRS (except for hard condition - no substantive change made). https://www.w3.org/policies/process/20231103/#rec-track So, simplicially saying, publishing as CRD at /TR/ is just a copy of ED into /TR/, without any new formal stage.
Received on Wednesday, 30 April 2025 17:24:19 UTC