doc: remove misleading warning #5681
Merged
Conversation
This file contains 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
github-actions
bot
added
the
documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Additional Context
tl;dr: documenting downstream bugs rather than filing them against downstream bug trackers is not the best approach.
It may be better to let users use the features that they want to, and if an issue is uncovered direct bug reports to the proper support channels.
This isn't true. No incompatibility with SELinux exists. An SELinux rule just needs to be updated on the affected distro to allow this access.
This is a downstream issue. Why wasn't it reported downstream for them to fix?
It's been around for a while. I'd like to stop calling this experimental.
Related to #3890
Merge type