Bug 1004638

Summary:	It's instead of its
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Misty Stanley-Jones <misty>
Component:	Documentation	Assignee:	Misha H. Ali <mhusnain>
Status:	CLOSED WONTFIX	QA Contact:	Russell Dickenson <rdickens>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1.1	CC:	lcarlon, nziakova, smumford
Target Milestone:	GA	Keywords:	Documentation, EasyFix, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-06 01:49:36 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:

Description Misty Stanley-Jones 2013-09-05 06:33:16 UTC

"JBoss Transactions can now be configured to use a JDBC database as it's store. "

In "New Features"

First. :)

Comment 2 Scott Mumford 2014-02-26 05:14:41 UTC

Moving to ON_QA.

The changes should be available for review on the documentation stage within an hour or so from this comment.

http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/

Comment 3 Scott Mumford 2014-02-26 05:16:12 UTC

Moving to ON_QA.

The changes should be available for review on the documentation stage within an hour or so from this comment.

http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/

Comment 4 Nikoleta Hlavickova 2014-03-04 15:44:59 UTC

Where can I find he fix? I am looking at [1] and it is not fixed here.

[1] https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.1/html-single/6.1.1_Release_Notes/index.html

Comment 5 Misty Stanley-Jones 2014-03-06 01:49:36 UTC

Sorry for the confusion. We do not re-build old release notes for such small errors, though we will try to be careful not to make this mistake in the future. This bug was filed against the 6.1.1 Release Notes, which are over 6 months old.