Zbigniew Jędrzejewski-Szmek
bc97e77ba7
The text implied that the changes may happen randomly at any time. Obviously, they can only happen after an update, but also we're unlikely to do that not on a major release boundary. So town down that part of the message. At the same time, it's important that the change might just happen. For stable features, we also sometimes implement incompatible changes, but this is preceded by announcements and lengthy deprecation periods. So use the phrase "without advance notice". OTOH, the text implicitly promised future stabilization. This might or might not happen, so remind the users that it might not. (cherry picked from commit 96cb6a5c74c8cd64334c48ddcca18e128e9a40ea)
System and Service Manager
Details
Most documentation is available on systemd's website.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release