-
Notifications
You must be signed in to change notification settings - Fork 32
Adds tier policy document #341
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
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
8a597c2
adds tier policy document
ederc c8a74a2
fixes typo
ederc ab9301f
adds macos intel runner
ederc 24583b6
Update doc/tier-policy.md
ederc 5c1db1c
adds arm for linux in tier 2
ederc 7a81dc1
Update doc/tier-policy.md
ederc File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,37 @@ | ||
| # Tier policy | ||
|
|
||
| ## Tiers | ||
|
|
||
| msolve provides three tiers of target support: | ||
|
|
||
| - msolve provides no guarantees about tier 3 targets; they exist in the codebase, but may or may not build. | ||
| - msolve expects that tier 2 targets will always build, but they may or may not pass tests. | ||
| - msolve's continuous integration checks that tier 1 targets will always build and pass tests. | ||
|
|
||
| Adding a new tier 3 target imposes minimal requirements; we focus primarily on avoiding disruption to other ongoing msolve development. | ||
|
|
||
| Tier 2 and tier 1 targets place work on msolve project developers as a whole, to avoid breaking the target. Thus, these tiers require commensurate and ongoing efforts from the maintainers of the target, to demonstrate value and to minimize any disruptions to ongoing msolve development. | ||
|
|
||
| This policy defines the requirements for accepting a proposed target at a given level of support. | ||
|
|
||
| ## Software platforms | ||
|
|
||
| ### Tier 1 | ||
| - x86_64 Linux | ||
| - x86_64 macOS | ||
| - ARM64 macOS | ||
|
|
||
| ### Tier 2 | ||
| - ARM64 Linux | ||
| - ARMv6 Linux | ||
| - ARMv7 Linux | ||
| - i686 Linux | ||
| - PPC64le Linux | ||
| - RISCV64 Linux | ||
| - x86_64 FreeBSD | ||
| - ARM64 FreeBSD | ||
|
|
||
| ### Tier 3 | ||
| - ARM64 Windows | ||
| - x86_64 Windows | ||
| - ARM64 Android | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI x86_64 macOS has been downgraded to Tier 2 platform for Rust in 2025 (see https://blog.rust-lang.org/2025/08/19/demoting-x86-64-apple-darwin-to-tier-2-with-host-tools/). Will we have to do the same soon?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, currently x86_64 is supported by macOS, but once it is no longer officially supported, yes, it has to become tier 2.