-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
Prepare for CRS #269
Draft
nigelmegitt
wants to merge
2
commits into
main
Choose a base branch
from
issue-0268/prepare-crs
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Prepare for CRS #269
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5 tasks
nigelmegitt
force-pushed
the
issue-0268/prepare-crs
branch
from
October 17, 2024 16:10
414704e
to
f134e4d
Compare
just an idea, how about to have a link to WG/CGs? |
cconcolato
approved these changes
Oct 18, 2024
The Timed Text Working Group just discussed
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
force-pushed
the
issue-0268/prepare-crs
branch
2 times, most recently
from
November 14, 2024 09:22
e2cf96e
to
49786a5
Compare
* set specStatus to CR * reference implementation report * set crEnd * Update SoTD to point to implementation report and include exit criteria * add acknowledgments
nigelmegitt
force-pushed
the
issue-0268/prepare-crs
branch
from
November 21, 2024 17:20
49786a5
to
5164943
Compare
As agreed during the TTWG call 2024-11-21
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #268.
Preview | Diff