feature-support: reset M3/M4 support lists#257
Merged
Conversation
I marked all the M3/M4 features as 'TBA', except those M3 features where someone is actively working on them, which are now 'WIP'. Signed-off-by: Alyssa Milburn <amilburn@zall.org>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The support lists for M3/M4 were inaccurate - and since nothing is supported in Fedora Asahi Remix, I'm assuming it doesn't make sense to mark anything as stable/upstream yet. I marked all the M3/M4 features as 'TBA', except those M3 features which work or where I'm aware that someone is actively working on them, which are now 'WIP'. The result is a bit pessimistic (no doubt some of this works already on M4, and I'm sure there are other things which are WIP on M3). Better than nothing..?