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 a little FCP to-do list to the tickyboxes comment #33

Open
3 tasks
anoadragon453 opened this issue Apr 3, 2023 · 2 comments
Open
3 tasks

Add a little FCP to-do list to the tickyboxes comment #33

anoadragon453 opened this issue Apr 3, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@anoadragon453
Copy link
Member

To transparently tell people what exactly needs to happen in order for FCP to start. The checklist would be slightly different depending on the FCP disposition (merge, close, postpone). For merge, you would have something like:

  • This MSC has one or more implementation(s), or does not need one.
  • There are no open concerns.
  • At least 75% of the Spec Core Team members have approved this MSC.

Existing FCP comments can be updated with this list when they are edited.

@anoadragon453 anoadragon453 added the enhancement New feature or request label Apr 3, 2023
@kegsay
Copy link
Member

kegsay commented May 14, 2024

I would add to this:

  • If this MSC touches sensitive parts of the specification they have tests to assert correctness.
  • If this MSC depends on another MSC, or is depended on by another MSC, both MSCs are ready to merge.

@anoadragon453
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants