Skip to content
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

README.md: Effectively revert deprecation notice #5331

Merged
merged 1 commit into from
Mar 18, 2025

Conversation

cgwalters
Copy link
Member

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 jmarrero enabled auto-merge March 11, 2025 14:22
Copy link
Member

@jlebon jlebon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK with this, though an alternative is to just soften the IMPORTANT message to make it less "deprecation-y". It's such an important shift that it feels odd to not be very explicit about it either.

The deprecation warning 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.

While we're here, switch the manual ASCII art to mermaid.js and
add bootc at the toplevel to it, peering with ostree.
@cgwalters
Copy link
Member Author

/override ci/prow/fcos-e2e
(Doesn't run on doc only changes)

Copy link

openshift-ci bot commented Mar 18, 2025

@cgwalters: Overrode contexts on behalf of cgwalters: ci/prow/fcos-e2e

In response to this:

/override ci/prow/fcos-e2e
(Doesn't run on doc only changes)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@jmarrero jmarrero merged commit 0f7109c into coreos:main Mar 18, 2025
18 checks passed
@cgwalters
Copy link
Member Author

This change is live now https://github.com/coreos/rpm-ostree - I think it looks decent but if anyone has followup suggestions/tweaks, now is probably a good time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants