-
Notifications
You must be signed in to change notification settings - Fork 22
Add more information about how clones are promoted #459
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
bsc#1253010 jsc#DOCTEAM-2014
gao-yan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the good addition, @tahliar
|
Thanks @gao-yan! I've revised the text a bit using your suggestions. Let me know if there's anything else I should clarify. |
gao-yan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks perfect. Thanks, @tahliar !
dariavladykina
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
* Add more information about how clones are promoted bsc#1253010 jsc#DOCTEAM-2014 * Updated revision date * Update from tech review
* Add more information about how clones are promoted bsc#1253010 jsc#DOCTEAM-2014 * Updated revision date * Update from tech review
* Add more information about how clones are promoted bsc#1253010 jsc#DOCTEAM-2014 * Updated revision date * Update from tech review
* Add more information about how clones are promoted bsc#1253010 jsc#DOCTEAM-2014 * Updated revision date * Update from tech review
PR creator: Description
I've added more info about how promotable clones are promoted, with some links to the in-depth Pacemaker doc.
(Updated Nov 27)

PR creator: Are there any relevant issues/feature requests?
PR creator: Which product versions do the changes apply to?
When opening a PR, check all versions of the documentation that your PR applies to.
main, no backport necessary)PR reviewer: Checklist
The doc team member merging your PR will take care of the following tasks and will tick the boxes if done.
<revision><date>YYYY-MM-DD</date>of chapter, part and book (if the change warrants it - for criteria, see https://documentation.suse.com/style/current/html/style-guide-db/sec-structure.html#sec-revinfo)