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

OTA-472: Reorganizing upgrade section and adding new chapter #39609

Closed
wants to merge 1 commit into from

Conversation

sagidlow
Copy link
Contributor

@sagidlow sagidlow commented Dec 7, 2021

Applies to 4.6+
JIRA Link: https://issues.redhat.com/browse/OTA-472
QE ack received on original PR (#36015). SME ack needed.
The remaining sections have been updated to remove the redundancy.

@netlify
Copy link

netlify bot commented Dec 7, 2021

✔️ Deploy Preview for osdocs ready!

🔨 Explore the source changes: 9083e19

🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/61af7e2d099b180008763a57

😎 Browse the preview: https://deploy-preview-39609--osdocs.netlify.app

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Dec 7, 2021
@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Dec 7, 2021
@sagidlow sagidlow force-pushed the sagidlow_OTA-472 branch 2 times, most recently from 329d4d9 to 68964e6 Compare December 7, 2021 15:23
@sagidlow sagidlow closed this Dec 7, 2021
@sagidlow sagidlow deleted the sagidlow_OTA-472 branch December 7, 2021 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.6 branch/enterprise-4.7 branch/enterprise-4.8 branch/enterprise-4.9 branch/enterprise-4.10 peer-review-needed Signifies that the peer review team needs to review this PR size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant