-
Notifications
You must be signed in to change notification settings - Fork 21
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
WIP: Expand non-quick installation content #410
Draft
tahliar
wants to merge
42
commits into
main
Choose a base branch
from
PED-2842-full-install-guide
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tahliar
force-pushed
the
PED-2842-full-install-guide
branch
from
September 19, 2024 03:36
f0c2eb9
to
18d2861
Compare
tahliar
changed the title
WIP: Full install guide
WIP: Expand non-quick installation content
Sep 20, 2024
tahliar
force-pushed
the
PED-2842-full-install-guide
branch
from
October 2, 2024 07:14
99fc267
to
8a95d11
Compare
tahliar
force-pushed
the
PED-2842-full-install-guide
branch
from
October 10, 2024 06:30
f91880c
to
79f6ac1
Compare
tahliar
force-pushed
the
PED-2842-full-install-guide
branch
from
October 24, 2024 06:47
91baf0c
to
1a27bea
Compare
jsc#PED-2842
jsc#PED-2842
It's no longer in the same guide, and the weirdly the xref resulted in a blank space instead of the Admin Guide's title
Oops I changed my mind
Will expand to be more detailed
For SLE 15, it just isn't viable to have a new guide. A lot of the content is already in the Admin Guide and would need to be either duplicated or linked to. Reusing content is currently not simple. For SLE 16, we can revisit having a separate guide.
tahliar
force-pushed
the
PED-2842-full-install-guide
branch
from
October 30, 2024 02:46
1a27bea
to
eef8b5d
Compare
tahliar
force-pushed
the
PED-2842-full-install-guide
branch
from
November 27, 2024 03:23
99fc829
to
93151d1
Compare
tahliar
force-pushed
the
PED-2842-full-install-guide
branch
from
November 29, 2024 06:02
93151d1
to
add6e76
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR creator: Description
Adding a full deployment guideExpanding the Admin Guide installation content so that all the options are clear. This is a long-term project and is currently a WIP.Opening a PR just for easier viewing of progress. It will need to be rebased regularly, so the commit dates in this PR do not reflect reality.
I originally kept track of the relevant product changes for each SP, but I've decided that it doesn't make sense to backport this, both because of complexity and to avoid issues with the localised content in earlier versions.
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 only: Have all backports been applied?
The doc team member merging your PR will take care of backporting to older documents.
When opening a PR, do not set the following check box.