README.md: Effectively revert deprecation notice #5331
+2
−6
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
It seems to be causing more confusion than help right now. We're going to keep maintaining this project for a long time because people are using it and it's shipped in products. The main original goal of the notice was to ensure people didn't show up out of the blue and start proposing big new changes, but in reality that's unlikely to happen anyways. The "promoting where things are happening" is already done organically by just, well, seeing where things are happening.
jmarrero
approved these changes
Mar 11, 2025
jlebon
reviewed
Mar 11, 2025
| @@ -1,18 +1,14 @@ | |||
| # rpm-ostree: A true hybrid image/package system | |||
|
|
|||
| > [!IMPORTANT] | |||
| > Currently, development focus has shifted to [bootc](https://github.com/containers/bootc), [dnf](https://github.com/rpm-software-management/dnf5/), and the ecosystem around those tools. However, rpm-ostree is widely in use today in many upstream projects and downstream products and **we will continue to support it** for some time with an emphasis on fixing important bugs, especially security-related ones. Some minor enhancements may happen but in general new major features, especially client-side, are unlikely to be prioritized. For more information, see: | |||
There was a problem hiding this comment.
E.g.
Currently, development focus has shifted to bootc, dnf, and the ecosystem around those tools. However, rpm-ostree is widely in use today in many upstream projects and downstream products and continues to be supported. In general, new major features related to bootable containers should land in those projects instead.
And drop the links.
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.
It seems to be causing more confusion than help right now. We're going to keep maintaining this project for a long time because people are using it and it's shipped in products.
The main original goal of the notice was to ensure people didn't show up out of the blue and start proposing big new changes, but in reality that's unlikely to happen anyways. The "promoting where things are happening" is already done organically by just, well, seeing where things are happening.