Bug 777835 (SOA-361) - docs directory and release note relocation
Summary: docs directory and release note relocation
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-361
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation
Version: 4.2 CR1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CR2
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-24 00:29 UTC by Joshua Wulf
Modified: 2014-10-19 22:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-06 07:23:43 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 777841 0 medium CLOSED Multiple/different versions of ESB project README first file in RC1 build 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 777994 0 high CLOSED Investigate re-working SOA-P embedded server directory structure so we can "drop-in" EAP updates 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-361 0 None None None Never

Internal Links: 777841 777994

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



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