search

w3c / imsc-hrm

IMSC Hypothetical Render Model
https://w3c.github.io/imsc-hrm/spec/imsc-hrm.html
Other
1 stars 6 forks source link

Proposed Recommendation #77

Closed palemieux closed 6 months ago

palemieux commented 7 months ago

Preview | Diff

nigelmegitt commented 7 months ago

Should we still include the CR exit criteria in the PR, or should those be removed (from the SOTD section)?

himorin commented 7 months ago

Should we still include the CR exit criteria in the PR, or should those be removed (from the SOTD section)?

In short, yes.

By testing locally, I've got respec error message for specStatus=PR without crEnd. Also a sentence like,

Note that substantive technical comments were expected during the Candidate Recommendation review period that ended XX XXX 202X.

seems to be mandatory for PR publication.

nigelmegitt commented 7 months ago

Thanks for that @himorin, then we should keep it. Looking at this text in the SOTD:

The W3C Membership and other interested parties are invited to review the document and send comments through 11 January 2024. Advisory Committee Representatives should consult their WBS questionnaires. Note that substantive technical comments were expected during the Candidate Recommendation review period that ended 20 July 2023.

the 11 January 2024 date is the one we need to fix up when we know the publication date, though I understand it might be generated automatically based on a specified publication date + fixed period.

himorin commented 7 months ago

Yes. Fixed period is at least 28days (for AC review).

nigelmegitt commented 7 months ago

Change made to close #78 - ideally this needs (re-)approvals @himorin , @andreastai , @palemieux if you agree with this change.

himorin commented 7 months ago

Change made to close #78 - ideally this needs (re-)approvals @himorin , @andreastai , @palemieux if you agree with this change.

changed statuses as r? from r+, but seems impossible to add @palemieux ...

nigelmegitt commented 7 months ago

seems impossible to add @palemieux ...

It's because he's the author of the PR. A comment from @palemieux about the change will be enough.

palemieux commented 7 months ago

@himorin @nigelmegitt Ok to merge?

himorin commented 7 months ago

@himorin @nigelmegitt Ok to merge?

publishDate (and prEnd) have not been fixed yet. see also #78

palemieux commented 7 months ago

publishDate (and prEnd) have not been fixed yet. see also https://github.com/w3c/imsc-hrm/issues/78

Can you provide dates?

himorin commented 7 months ago

as the same as last time you questioned, there is no solid answer but per best assumption: if CfC ends at 2024-02-12, transition request will be discussed and approved if there is no issue (e.g. IR as we discussed during call) around 2024-02-16, next publication slot is 2024-02-20. with 4 weeks, prEnd at 2024-03-19.

nigelmegitt commented 7 months ago

@himorin @nigelmegitt Ok to merge?

Apologies, I don't think so, due to the late change 0114dfb and related CfC about allowing updates. When we know that's good and the transition request is modified and approved, we will know the dates and can update and merge this PR and make a release, to match the published Proposed Rec.

palemieux commented 7 months ago

Ok. Just let me know. LGTM so far.

nigelmegitt commented 6 months ago

CfC period for 0114dfb has now expired with no objections; as Chair, I declared Consensus to proceed with this as an updateable Rec in this email.

himorin commented 6 months ago

please use following lines (tentatively - could need to be updated per transition request discussion):

publishDate: "2024-02-20"
prEnd: "2024-03-19"
nigelmegitt commented 6 months ago

See https://github.com/w3c/transitions/issues/590#issuecomment-1952008597