Bug 1517963 - [RFE] RHEL6 -> RHEL7 Migration: Extract section 1.3 from 6.3 upgrade docs and include in 6.2 docs
Summary: [RFE] RHEL6 -> RHEL7 Migration: Extract section 1.3 from 6.3 upgrade docs and...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Install Guide
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Melanie Corr
QA Contact: Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks: GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker
TreeView+ depends on / blocked
 
Reported: 2017-11-27 18:24 UTC by Mike McCune
Modified: 2019-09-26 16:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-22 04:30:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mike McCune 2017-11-27 18:24:33 UTC
We need to release the guide on how to migrate from RHEL6 to RHEL7 before the 6.3 GA of 6.3 so we can start customers migrating from RHEL6 to RHEL7 sooner than later.

This is a request to see if we can take the content from Section 1.3 from the 6.3 Upgrade Guide:

"1.3. MIGRATING FROM RED HAT ENTERPRISE LINUX 6 TO RED HAT
ENTERPRISE LINUX 7"

and release that in a new section in perhaps the CHAPTER 6 of the 6.2 Upgrade Guide so customers can start migrating *now* vs later.

Since migration is from 6.2 -> 6.2 we don't need to tie this to the 6.3 release and is an operation that takes place purely within the scope of 6.2.

Comment 2 Andrew Dahms 2017-11-28 12:58:12 UTC
Assigning to Melanie for review.

Comment 3 Andrew Dahms 2017-11-28 13:10:11 UTC
Melanie - I'm not quite sure what the best place for this content would be, but as a section of the upgrade content in the Installation Guide might be our best bet. No need for us to talk about this as part of upgrades as such; only as a way to move from RHEL 6 to RHEL 7 in preparation for future upgrades if necessary.

Let me know what you think.


Note You need to log in before you can comment on or make changes to this bug.