Skip to content

docs(upgrade): clarifies how upgrade/downgrade paths work #11290

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 3 commits into from
Mar 27, 2025
Merged

docs(upgrade): clarifies how upgrade/downgrade paths work #11290

merged 3 commits into from
Mar 27, 2025

Conversation

PaulRMellor
Copy link
Contributor

@PaulRMellor PaulRMellor commented Mar 25, 2025 •
edited
Loading

Documentation

Update to the descriptions of the upgrade and downgrade paths to make it clear how they operate.

Checklist

Please go through this checklist and make sure all applicable tasks have been done

  • Write tests
  • Make sure all tests pass
  • Update documentation
  • Check RBAC rights for Kubernetes / OpenShift roles
  • Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
  • Reference relevant issue(s) and close them after merging
  • Update CHANGELOG.md
  • Supply screenshots for visual changes, such as Grafana dashboards

@PaulRMellor PaulRMellor added this to the 0.46.0 milestone Mar 25, 2025
@PaulRMellor PaulRMellor requested a review from ppatierno March 25, 2025 16:21
@PaulRMellor PaulRMellor self-assigned this Mar 25, 2025
@PaulRMellor PaulRMellor requested a review from kyguy March 25, 2025 16:28
@PaulRMellor PaulRMellor changed the title docs(upgrade): clarifies how upgrade paths work docs(upgrade): clarifies how upgrade/downgrade paths work Mar 25, 2025
fvaleri
fvaleri approved these changes Mar 25, 2025
View reviewed changes
Copy link
Contributor

@fvaleri fvaleri left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks.

@PaulRMellor
Copy link
Contributor Author

PaulRMellor commented Mar 26, 2025 •
edited
Loading

Thanks for the feedback @scholzj .
The original wording aimed to clarify that not all downgrade paths are tested or guaranteed to work. Earlier reviews suggested that the wording would be acceptable, even though there isn’t a clear definition of what “support” means in this context.
I’ve revised the text to better reflect the perspective.
Let me know if any further changes would help strike the right balance.

@PaulRMellor PaulRMellor merged commit 35e3d84 into strimzi:main Mar 27, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@fvaleri fvaleri fvaleri approved these changes

@scholzj scholzj scholzj approved these changes

@ppatierno ppatierno ppatierno approved these changes

@kyguy kyguy kyguy approved these changes

@im-konge im-konge im-konge approved these changes

Assignees

@PaulRMellor PaulRMellor

Labels
documentation
Projects
None yet
Milestone
0.46.0
Development

Successfully merging this pull request may close these issues.
6 participants
@PaulRMellor @scholzj @ppatierno @kyguy @fvaleri @im-konge