Skip to content
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

Add CR Plan for V1 #1242

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add CR Plan for V1 #1242

wants to merge 1 commit into from

Conversation

jungkees
Copy link
Collaborator

@jungkees jungkees commented Dec 7, 2017

This is a CR plan with a WIP table that maps WPT tests to each spec feature.

@ylafon @jakearchibald @jatindersmann - I'd like to discuss if this format and the information (that will be filled in the table) will meet the requirement to proceed and exit CR.

FYI, I asked @tabatkins if Bikeshed will support some feature to annotate the WPT status directly in the spec, and the answer was yes with no concrete schedule yet - at the end of the year at the earliest.

Until then, I plan to continue with this work. WDYT?

@ylafon
Copy link
Member

ylafon commented Dec 8, 2017

Good work,
Note that annotating the spec with WPT status would be useful for v2 and beyond, not for v1 as we reach CR now.
Note also that per charter, the exit criteria for CR is to have two implementation for each feature.

The format you propose for the table is good, needed for exiting CR, but not needed at all for entering it. For that we just need ot state the exit criteria and link to a report page that can be this CR Plan (but it can even be empty, at publication time, as it just needs to be complete when we exit).
Also, it would be good to identify the features at risk (we can even use a blanket statement that they are all at risks if implemented, but we can also list the ones that don't qualify as of today).

We basically just need to prepare the v1 CR doc and add in the SoTD that information (I can take care of that once the doc is ready)
Thanks,

@jungkees
Copy link
Collaborator Author

@jakearchibald @ylafon, let's publish a CR. I think we can use this PR document to track CR progress (test coverage and compat) after we publish the first CR version.

@jakearchibald, please take a look at the following PRs. I'd like to merge them to publish a CR.

#1151 (Approved, I’m checking if we need a separate test for SW.)
#1293
#1329
#1332
#1354

From the V1 issue list, #732 will be closed by merging #1329. I'd like to move other issues to V2. They are dependent to works in HTML and DOM.

@ylafon
Copy link
Member

ylafon commented Sep 14, 2018

As discussed on irc, we also need to select the test relevant to V1 only.
and strong +1 to move remaining issues to V2 (and add an editors' note if needed)

@mfalken
Copy link
Member

mfalken commented Mar 13, 2019

@jungkees @jakearchibald I think this PR is probably obsolete now?

@jungkees
Copy link
Collaborator Author

@mattto, the content of the PR seems outdated. The purpose of the PR is to track the process of entering CR. So, either using this PR by updating the content or putting together a new document would be fine.

/cc @aliams

Base automatically changed from master to main February 4, 2021 19:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants