Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1515003 - [RFE] Review the Upgrade Overview chapter
Summary: [RFE] Review the Upgrade Overview chapter
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Upgrading and Updating Red Hat Satellite
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Russell Dickenson
QA Contact: Melanie Corr
URL:
Whiteboard:
Depends On:
Blocks: 1454572
TreeView+ depends on / blocked
 
Reported: 2017-11-20 00:09 UTC by Andrew Dahms
Modified: 2019-09-26 14:54 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-13 01:01:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Andrew Dahms 2017-11-20 00:09:56 UTC 
The following updates must be made to the Upgrade Overview chapter of the upgrade guide -

* Add one or two lines to the start of the opening paragraph to tell the 
  reader what information the chapter contains.
* Remove the section 'Upgrade Requirements'
* Change the text under 'Following the Progress of the Upgrade' into its own
  section that comes after 'Upgrade Paths'
Comment 1 Andrew Dahms 2017-11-20 00:25:41 UTC 
Assigning to Russell for review.
Note You need to log in before you can comment on or make changes to this bug.