Red Hat Bugzilla – Bug 983951
4.1. Step 3 should be similar as in RPM
Last modified: 2014-08-14 11:18:40 EDT
Title: Upgrade the JBoss EAP 6 ZIP Installation
Describe the issue:
Step 3 for ZIP upgrade should be consistent between ZIP and RPM upgrade way. We should not allow our customers to blindly copy their old instance (possible very old - contains e.g. EAP-6.0.0) configuration to new location and replace cfg. files like standalone.xml etc.
Suggestions for improvement:
For our safety, there should be some like this sentence:
Manually merge your changes from previous installation over the new installation directories.
The step 4 contains similar useful (safer) way how to solve the upgrade.
I have altered step 3 to be similar to step 4, with a warning about copying configuration files from previous versions.
Change made to topic 12710 (rev. 548437)
The change will be reflected in the next document build, and the status will be changed to ON_QA when it is ready for review.
Changes are on-stage and ready for review (Revision 2.0-7):
Verified (during EAP 6.2.0 testing cycle).
I appreciate that in this instance we (Docs) provided instructions which were inaccurate. As to discussing such changes with Engineering, which types of changes would you prefer be discussed in advance? I'm happy to have Docs team members refer such changes to an SME as required, as long as we know just which changes ought to be referred.
Thanks. All three criteria are very useful.
As for devel_ack, ideally we don't make documentation changes unless devel_ack is provided. As to whom should provide that ACK, well, that's a good point. I hope this could be raised in an EAP PM meeting.