On 11. 03. 22 0:35, Brett Cannon wrote:
I brought this up on python-dev at https://email@example.com/thread/ZPBSHENP3... https://firstname.lastname@example.org/thread/ZPBSHENP3V7KHNPYWE6BEQD5ASES2NLV/ , and the feedback seemed supportive. As such, I am bringing a draft of what I'm thinking will go into PEP 11 with a bunch of
XXXplaceholders for people to help me fill in to see how this will look overall.
For any platform(s) you support, please reply with any relevant details that should be added to the relevant tables below. Once I have these details I will loop back with the proposed update to PEP 11 and make sure everyone is still on board with the proposal.
===== Tiers =====
- `Test suite failures
- Changes which would break the
mainbranch are not allowed to be
merged; any breakage may be reverted immediately.
- All core developers are responsible to keep these platforms working.
What does this mean? I can not merge a change if it doesn't pass macOS CI, but I don't have a macOS system, so I can't really diagnose and fix macOS bugs.
- Promotion of this tier requires consensus/SC approval.
=================== ===== Target Triple Notes =================== ===== i686-windows-msvc
What's the supported version of Windows?
x86_64-windows-msvc x86_64-apple-darwin macOS 11 x86_64-linux-gnu glibc 2.31 |ubuntu-20_01|_
Would it be better to say “whatever GitHub Actions has” in the long-term docs, and put the specific version in the docs rather than in the PEP?
[...]> All other platforms
- Only code which either supports a higher-tier platform or is a general
improvement may be checked in.
I'm worried about going from this to tier 3. How do you get to a platform's buildbot being stable if you can't merge code for it?