Red Hat Bugzilla – Bug 983894
[Bug in Installation Guide]: Latest EAP version in chapter 12 - upgrade
Last modified: 2015-07-02 20:44:35 EDT
Section Number and Name:
Describe the issue:
Chapter 12 describes upgrade procedure to the latest 5.1.x version, But documentation is now for EAP-5.2.0 so for EAP-5.2.0 is the latest version 5.2.0 obviously, so this chapter needs several rephrases of affected sentences.
Suggestions for improvement:
Use only 'the latest version', not exactly 5.1.x or 5.2.x in sentences.
Each of the EAP 5 documents have entities for version numbers pre-formatted. The entity definitions have been updated in the Installation Guide and the version numbers now read correctly (5, 5.3, 5.3.0).
And updated version is available for review at:
(disregard the legacy version number in the URL)
Current version doesn't make sense... there is a sentence like:
"An in-place upgrade from version 5.3.0 to the latest version is available for customers who have installed the platform using RPM." - we are testing 5.3.0 now, so the latest in the GA will be 5.3.0, this sentence needs to be rewritten.
Title of section 'Upgrade JBoss Enterprise Application Platform 5.3 to the latest 5.3.0 version using RPM' needs to be rewritten as well.
Thanks for the feedback Pavel. I obviously neglected to proofread the section after I'd updated it.
I've adjusted the text so it makes sense now. I reintroduced 5.1 as the base upgrade version as the section was clearly written with that scenario in mind (did an RPM upgrade feature get added in 5.1?)
The changes are available at (1) version 5.3.0-4 or later.
One more update it is needed. Current version is 5.2.0 not, 5.1. as mentioned there.
Pavel, can you point out where the document states that 5.1 is the latest version, as I can't see that it does.
That section in particular is referring to upgrading from 5.1 to the latest version (5.3.0), is that what you're referring to?
If so, the reason it still reads that way is because the section was originally written for upgrades from 5.1 to a later version (probably 5.2). I didn't want to assume that the upgrade would function the same way for later upgrades (5.2 to 5.3, for instance).
If I can get confirmation that the upgrade process is the same across versions post-5.1, I'll be glad to edit references to be more generic so as to to avoid this needing to be reworked every release.
yes, the procedure is still the same, so the para should be more generic in that case.
I've changed the title reference from 5.1 to simply 5. I couldn't see any other references to specific versions.
The content should now be generic enough to not require constant updating but still be useful.
(version 5.3.0-6 or later)