Bug 1044601 - Installer is the 'suggested' installation method for users - remove terminology from ZIP
Summary: Installer is the 'suggested' installation method for users - remove terminolo...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: post-GA
: EAP 6.3.0
Assignee: sgilda
QA Contact: Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-18 16:15 UTC by Catherine Robson
Modified: 2014-11-23 23:16 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Build Name: 14873, Installation Guide-6.2-1 Build Date: 10-12-2013 13:55:18 Topic ID: 13004-545631 [Specified]
Last Closed: 2014-11-23 23:16:31 UTC
Type: Bug


Attachments (Terms of Use)

Description Catherine Robson 2013-12-18 16:15:01 UTC
Title: Download JBoss EAP 6 (Zip Installation)

Describe the issue:
We need to start pushing the Installer as the suggested installation method for users.  This is, for new users unfamiliar with EAP, the best method to download and get EAP running without knowing anything about how JBoss works.

For people familiar with JBoss, we should allow them to grab the zip as it might be "faster" - but if you don't understand JBoss it feels confusing.  This is especially true for those users coming to JBoss from our competitors.



Suggestions for improvement:

Remove the terminology "is the preferred way to install JBoss EAP 6 on all supported platforms"

Either leave this out completely - or add this terminology to the Installer section instead of the ZIP section.

Comment 2 Catherine Robson 2014-08-13 11:17:34 UTC
I think your update makes sense.  I'm happy to move forward with that terminology.

Comment 3 sgilda 2014-08-13 12:34:50 UTC
I just want to mention I created a new version of this topic for the 'Getting Started Guide' to use with the new jboss.org web site: 

        Download JBoss EAP 6 (ZIP Installation) [26696]

This is the topic rendered in the guide:

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Getting_Started_Guide/index.html#Download_JBoss_EAP_6_Zip_Installation

It describes both the Full Red Hat JBoss Commercial Program and Red Hat JBoss Developer Program. It also does not say anything about the preferred method of installation.

Do we want to replace the version of the topic in the Installation Guide with this one? 

Catherine and Tom Wells, what do you think?

Comment 5 sgilda 2014-09-08 14:00:09 UTC
Catherine, 

As I mentioned in Comment 3, I can replace the text currently in the Installation Guide with the following:

    "The JBoss EAP 6 ZIP file is available from the Red Hat Customer Portal. The ZIP file is platform-independent and can be installed on any of the supported platforms. This topic covers the steps to download the archive."

Or, I can replace the entire topic [1] with the one used the Getting Started Guide [2].

[1] https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Installation_Guide/index.html#Download_JBoss_Enterprise_Application_Platform_6_Zip_Installation

[2] https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Getting_Started_Guide/index.html#Download_JBoss_EAP_6_Zip_Installation

Replacing the topic will be a little more disruptive because the title is slightly different (Zip versus ZIP) and I would have to add the License Agreement topic to the Installation Guide. I'm not sure how much we want to change the guides in the patch updates.

Let me know your preference.

Thanks,
Sande

Comment 6 Catherine Robson 2014-09-22 11:28:12 UTC
I think just replacing the text will be fine so that we can keep it as simple of a change as possible.

Comment 9 Nikoleta Hlavickova 2014-09-26 10:23:33 UTC
Verified in revision 6.3.0-35.


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