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

modules/update-service-overview: Simplify intro paragraph #26668

Closed
wants to merge 1 commit into from

Conversation

wking
Copy link
Member

@wking wking commented Oct 23, 2020

I'd initially wanted to address "It provides a graph, or diagram that contain" -> "It provides a graph, or diagram, that contains". But the "of component Operators" bit was confusing to me to. So I've reworded to lead with "graph of recommended update(s)", and reduce to a single sentence. I'd also be fine leading with a description of release images, and then introducing the recommended update edges that link them, but that seemed like a bigger refactor. Wording I'm replacing is from 29016d7 (#12880) and 6e1b894 (#14991).

/assign @kalexand-rh

@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Oct 23, 2020
@wking wking changed the title modules/update-service-overview: Simplify into paragraph modules/update-service-overview: Simplify intro paragraph Oct 23, 2020
@wking wking force-pushed the update-graph-or-diagram-nits branch from 82d96d1 to ba1a04a Compare October 23, 2020 05:11
I'd initially wanted to address "It provides a graph, or diagram that
contain" -> "It provides a graph, or diagram, that contains".  But the
"of component Operators" bit was confusing to me to.  So I've
reworded to lead with "graph of recommended update(s)", and reduce to
a single sentence.  I'd also be fine leading with a description of
release images, and then introducing the recommended update edges that
link them, but that seemed like a bigger refactor.  Wording I'm
replacing is from 29016d7 (draft of early 4.0 architecture updates,
2018-11-08, openshift#12880) and 6e1b894 (Initial add of modularized arch
guide content, 2019-05-21, openshift#14991).
@wking wking force-pushed the update-graph-or-diagram-nits branch from ba1a04a to e298686 Compare October 23, 2020 05:11
@openshift-docs-preview-bot

The preview will be available shortly at:

@kalexand-rh
Copy link
Contributor

@jiajliu, will you PTAL?

@jiajliu
Copy link

jiajliu commented Oct 28, 2020

LGTM

Copy link
Contributor

@lbarbeevargas lbarbeevargas left a comment

Choose a reason for hiding this comment

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

A couple of questions/suggestions, but otherwise LGTM!

of the managed cluster components.
updates to both {product-title} and {op-system-first}. It serves a graph of
recommended update _edges_ between {product-title} release image _vertices_ that
specify the intended state of the managed cluster components.
Copy link
Contributor

@lbarbeevargas lbarbeevargas Oct 28, 2020

Choose a reason for hiding this comment

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

Can you clarify what is specifying "the intended state of the managed cluster components?" It's a little confusing as to what "that" is referring to. For example:

It serves a graph of recommended update edges between OpenShift Container Platform release image vertices. The edges specify the intended state of the managed cluster components.

Also, is "provide" or "displays" more localization friendly versus "serves?"

Other than these questions/suggestions, LGTM!

Copy link
Contributor

Choose a reason for hiding this comment

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

The "vertices" specify the intended state of the managed cluster components, and it's important enough that I don't want to diminish it by changing it to "vertices, which..."

@wking, what nuance are you trying to get across with the s/provides/serves? "Serves" is used in the same context in other places in the collection, so I'm inclined to let it stand.

@lbarbeevargas lbarbeevargas added the peer-review-done Signifies that the peer review team has reviewed this PR label Oct 28, 2020
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 26, 2021
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 25, 2021
@openshift-bot
Copy link

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci-robot
Copy link

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.4 branch/enterprise-4.5 branch/enterprise-4.6 branch/enterprise-4.7 lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. peer-review-done Signifies that the peer review team has reviewed this PR size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants