-
Notifications
You must be signed in to change notification settings - Fork 1.9k
issue 13527 removed xPaaS image links #13567
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
Conversation
|
Well, there's a lot of xrefs that need correcting. Thanks, Travis. I'm a little unclear on the scope of the issue; do we want to remove all mentions (and xrefs) of xPaaS? More descriptively, how far do we want to go with xPaaS removal? For example, in the Does the whole section need to be deleted in this case? |
|
When I looked, I found these: |
|
My suspicion is that those references can be removed from the docs as well, but I'd also want confirmation if it was me. Based on the text, it seems reasonable that each entire line or block speaking about xPaaS images can be excised though. |
|
Thanks so much @jboxman . Just wanted to make sure I wasn't crazy! |
|
sigh This has gotten complex. :) @sheriff-rh just take out the links to the xPaaS sections which are causing the build to fail. While the docs haven't been updated since 3.6 because the downstream was disbanded, the upstream GitHub repo containing these images seems to be still updated as late as Dec 2018. cc: @aheslin |
issue-13527 amended xPaaS changes
bbb9f53 to
e374efc
Compare
|
The preview will be availble shortly at: |
|
Squashed commits to remove xrefs. All checks have passed. @openshift/team-documentation peer review please! |
|
LGTM |
|
/cherrypick enterprise-3.11 |
|
@sheriff-rh: #13567 failed to apply on top of branch "enterprise-3.11": DetailsIn response to this:
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/test-infra repository. |
fixes #13527
@jboxman would you please review?
@vikram-redhat I'll merge this PR from 3.7 onwards if it looks good to you.