Bug 860171

Summary: Add location of docs within the zip
Product: [JBoss] JBoss Enterprise Web Server 2 Reporter: Misha H. Ali <mhusnain>
Component: doc-Release-NotesAssignee: Misha H. Ali <mhusnain>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.0.0CC: lfuka
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 854847 Environment:
Last Closed: 2012-11-08 22:11:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 854847    
Bug Blocks:    

Description Misha H. Ali 2012-09-25 07:40:10 UTC
+++ This bug was initially created as a clone of Bug #854847 +++

This bug is set to the Release Note component as a placeholder. Information about the documentation within the EWS zip needs to be explained here.

Note: This bug is a placeholder to ensure that when the Release Notes are drafted, the information in its clone is replicated in the release notes.

Comment 2 Libor Fuka 2012-10-10 12:31:14 UTC
not written yet in Release notes

Comment 3 Misha H. Ali 2012-10-12 04:55:52 UTC
Added duplication of QE'd information in Install Guide for this. This bugs will be set to ON_QA and updated with a link once the contents appear on the stage.

Comment 5 Libor Fuka 2012-10-12 11:45:55 UTC
jboss-ews-docs-2.0.0.zip is not only about mod_ssl documentation but more things.

Its inside cos.zip
httpd/
mod_auth_kerb/
mod_cluster/
mod_jk/
openssl/
tomcat-native/
tomcat6/
tomcat7/

Comment 6 Misha H. Ali 2012-10-13 03:47:47 UTC
Updated to incorporate this information. This bug will be set to ON_QA when this information (duplicated) can be verified in the 2.0.0 Release Notes and the Installation Guide.

Comment 8 Misha H. Ali 2012-11-08 22:11:25 UTC
This bug is set to CLOSED CURRENT RELEASE to indicate that this fix is now released and available at access.redhat.com.