Bug 857008 - qpid-perftest deprecation require changes in Messaging UG
Summary: qpid-perftest deprecation require changes in Messaging UG
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Messaging_Installation_and_Configuration_Guide
Version: Development
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: 3.0
: ---
Assignee: Jared MORGAN
QA Contact: Eric Sammons
URL:
Whiteboard:
Depends On:
Blocks: 789412
TreeView+ depends on / blocked
 
Reported: 2012-09-13 11:23 UTC by Frantisek Reznicek
Modified: 2015-08-10 01:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-22 15:28:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Frantisek Reznicek 2012-09-13 11:23:54 UTC
Description of problem:

There are qpid-perftest lines in Messaging UG (3 matches).
The bug 789412 tracks removal of qpid-perftest and thus document should reflect that change including usage of qpid-*benchmark.


Version-Release number of selected component (if applicable):
qpid-0.14

How reproducible:
N/A

Steps to Reproduce:
N/A
  
Actual results:
qpid-perftest going to be deprecated, documentation still mentiones it.

Expected results:
qpid-perftest going to be deprecated, documentation needs to change to reference qpid-*benchmark + qpid-send/receive instead.

Additional info:
  Bug 789412

Comment 1 Joshua Wulf 2012-12-12 06:25:31 UTC
Per https://bugzilla.redhat.com/show_bug.cgi?id=789412#c11 and comment 12, this will be done through a deprecation notice in the 2.3 release notes, and the component will be removed post-2.3.

Pushing modification of the documentation to 2.4

Comment 2 Joshua Wulf 2013-09-23 07:54:24 UTC
Removed qpid-perftest section from MCIG.

Comment 5 Valiantsina Hubeika 2014-02-03 09:34:01 UTC
Could you please check table 12.1, it contains one reference.

Comment 7 Valiantsina Hubeika 2014-02-05 11:26:21 UTC
checked & verified


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