Skip to content

Conversation

@nigelmegitt
Copy link
Contributor

@nigelmegitt nigelmegitt commented Oct 16, 2024

PLEASE DO NOT MERGE until CR has been published


Closes #268.

  • set specStatus to CR
  • reference implementation report
  • set crEnd
  • Update SoTD to point to implementation report and include exit criteria
  • add acknowledgments

Preview | Diff

@himorin
Copy link
Contributor

himorin commented Oct 18, 2024

just an idea, how about to have a link to WG/CGs?

@nigelmegitt nigelmegitt added the agenda Issue flagged for in-meeting discussion label Nov 5, 2024
@css-meeting-bot
Copy link
Member

The Timed Text Working Group just discussed Prepare for CRS w3c/dapt#269, and agreed to the following:

  • SUMMARY: Rebase as needed and use as the basis of the CRS transition request
The full IRC log of that discussion <nigel> Subtopic: Prepare for CRS #269
<nigel> github: https://github.com//pull/269
<cpn> Nigel: I used the draft PR feature for this, similar to how Pierre does it with IMSC
<cpn> ... Once everything is merged, I'll rebase this, and that will be the bases for the CRS
<cpn> ... No action needed. It changes the spec status, refers to implementation report, etc. End date says 1 January for Proposed Recommendation, may need to adjust
<cpn> ... CR exit criteria us almost the same wording as for IMSC
<cpn> ... I cross-checked the wording against the charter. AFAICT it's compatible with that
<cpn> ... Unless there are comments, I'll assume it's ok
<cpn> (nothing)
<cpn> ... Please LMK if anyone should be added to Acknowledgements
<nigel> SUMMARY: Rebase as needed and use as the basis of the CRS transition request

@nigelmegitt nigelmegitt force-pushed the issue-0268/prepare-crs branch 2 times, most recently from e2cf96e to 49786a5 Compare November 14, 2024 09:22
@nigelmegitt nigelmegitt force-pushed the issue-0268/prepare-crs branch from 49786a5 to 5164943 Compare November 21, 2024 17:20
@nigelmegitt nigelmegitt removed the agenda Issue flagged for in-meeting discussion label Dec 2, 2024
@nigelmegitt nigelmegitt marked this pull request as ready for review December 2, 2024 11:34
@nigelmegitt
Copy link
Contributor Author

As discussed in yesterday's TTWG call, I plan to rebase this when other PRs get merged so that the version we put out as CR is as up to date as possible. #278 is currently the only substantive (class 3) PR - currently all the others are class 1 or 2 changes.

* set specStatus to CR
* reference implementation report
* set crEnd
* Update SoTD to point to implementation report and include exit criteria
* add acknowledgments
As agreed during the TTWG call 2024-11-21
@himorin
Copy link
Contributor

himorin commented Mar 7, 2025

note, parameter used for /TR/ is dapt/?specStatus=CR&publishDate=2025-03-11&crEnd=2025-04-08

@nigelmegitt
Copy link
Contributor Author

Are there any other changes we should make here to reflect the CR version, @himorin ?

@himorin
Copy link
Contributor

himorin commented Mar 11, 2025

Are there any other changes we should make here to reflect the CR version, @himorin ?

All changes I have made are raised as PR, except for parameter supplied to respec. So, I believe I don't have anything else.

@nigelmegitt nigelmegitt merged commit 8939628 into main Mar 21, 2025
2 checks passed
@nigelmegitt nigelmegitt deleted the issue-0268/prepare-crs branch March 21, 2025 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Prepare CR draft ready for publication

5 participants