-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Promoting WASI to tier 2 #223
Comments
The SC decided the process for promoting can just be:
CI is highly desirable (since it's much harder to discover buildbot breakages than CI ones, although with our current Developers-in-Residence that's improving quite a lot), but we don't want to make it a requirement for tier 2 promotion since CI may not be an option for some platforms. The extra things you're suggesting we ask for may be desirable to get to the support level you and the other designated maintainers want to provide, and probably would be necessary to get consensus among core devs for tier 1 support, but as far as we're concerned they're not a requirement for getting to tier 2. |
Thanks so much! I'll still move the docs to the devguide before I update PEP 11. I also still plan to try out a CI solution to see if it can run fast enough to not be a bottleneck. And mostly for the RM, I got a debug build buildbot up and running today. 🙂 |
I would like to find out what the SC would like to see happen to promote WASI support to tier 2? I have tried to simplify the development process via python/cpython#112473 so that anyone needing to debug a failure under WASI can do so (plus the devcontainer for the CPython repo has the tools necessary). Luckily the failures are almost always test assumptions around threading or certain stack sizes existing.
Some possible things to ask of me (beyond the obvious tier 2 requirements):
The text was updated successfully, but these errors were encountered: