Bug 777835 (SOA-361)

Summary: docs directory and release note relocation
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Joshua Wulf <jwulf>
Component: DocumentationAssignee: trev <tkirby>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 CR1CC: lcarlon
Target Milestone: ---   
Target Release: 4.2 CR2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-361
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-06 07:23:43 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:

Description Joshua Wulf 2008-01-24 00:29:57 UTC
Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes
Date of First Response: 2008-01-24 02:48:54
project_key: SOA

Can we put the docs directory and the SOA Release note in the root directory? So it would look something like this:

jboss-soa-p.4.2.0
                      |---jboss-as
                      |---jbpm-jpdl
                      |---seam
                      |---docs
                      |---SOA_Release_Notes.htm
                      |---SOA_Release_Notes.txt


RationaIe for the Release Note relocation: In the Release Notes I am including a brief overview of the included documentation. Putting it here in the directory hierarchy makes it clear that this is the first document to read. Otherwise we have a number of Getting Started and Release note documents, and it's not clear how they relate. This can be the "one ring to rule them all".

Rationale for the docs directory relocation: Since the docs apply to the platform as a whole, and not simply to the jboss-as component, they should go at this level.

Comment 1 Joshua Wulf 2008-01-24 00:42:11 UTC
Same thing for the standalone. At the moment the Release Notes and the ESB Readme.first are at the same level, which can be confusing.

Comment 2 Mark Little 2008-01-24 07:48:54 UTC
Set Component.

Comment 3 Len DiMaggio 2008-01-25 17:17:41 UTC
Link: Added: This issue related SOA-368


Comment 4 Joshua Wulf 2008-02-06 07:23:43 UTC
CR2 has the fix

Comment 5 trev 2009-05-29 08:48:08 UTC
Link: Added: This issue related SOA-521