Uh oh!
There was an error while loading. Please reload this page.
Add tier labels corresponding to PEP 11 - #326
Conversation
pablogsal
commented
Jun 4, 2022
Thanks @brettcannon! ❤️ |
pablogsal
commented
Jun 4, 2022
I merged so we have a baseline for tier support tags, but I noticed there are a bunch of Linux buildbots that are tagged as |
vstinner
commented
Jun 6, 2022
Great :-) |
brettcannon
commented
Jun 6, 2022
I purposefully overlooked them as PEP 11 specifies the platforms run by CI as tier 1 and purposefully doesn't mention buildbots for that tier (hence why there isn't a single tier 1 buildbot 😁). That way the "Changes which would break the main branch are not allowed to be merged" requirement can be met since buildbots don't run on PRs. If people think that's too strict of an interpretation and want to add tier 1 buildbots I'm fine with it. |
* Initial WASM/Cross build code * Changes to use HOSTRUNNER instead of RUNSHARED * Add 3.11 branches (#323) * Add tier labels corresponding to PEP 11 (#326) * Add environment variable to set settings path (#328) * Split WASM build factories * use config.guess directly * Fix pkg-config cross build, add suffix to create unique workers Co-authored-by: Brett Cannon <brett@python.org> Co-authored-by: Christian Heimes <christian@python.org> Co-authored-by: Ethan Smith <ethan@ethanhs.me> Co-authored-by: Pablo Galindo Salgado <Pablogsal@gmail.com> Co-authored-by: Zachary Ware <zach@python.org>
No description provided.