Bug 886357

Summary: [Release Notes] Deprecate version 1 of the QMF API
Product: Red Hat Enterprise MRG Reporter: Cheryn Tan <chetan>
Component: Release_NotesAssignee: Joshua Wulf <jwulf>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matousek <pematous>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.3CC: jross, lcarlon, lzhaldyb, pematous, rlandman, tross
Target Milestone: 2.3   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 885205 Environment:
Last Closed: 2013-03-19 16:38:16 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: 885205    
Bug Blocks:    

Description Cheryn Tan 2012-12-12 06:21:14 UTC
+++ This bug was initially created as a clone of Bug #885205 +++

QMF 1 is now superceded by the QMF 2 API.  QMF 1 is not ABI-stable, and no one should use it.

--- Additional comment from Justin Ross on 2012-12-08 05:19:01 CST ---

Ted, what are the namespaces of the QMF 1 APIs?

--- Additional comment from Ted Ross on 2012-12-08 05:23:15 CST ---

(In reply to comment #1)
> Ted, what are the namespaces of the QMF 1 APIs?

qpid::management
qpid::console

Note that internal to the qpid broker, there are some definitions in qpid::management that are not to be deprecated as they support both v1 and v2 protocols.

Comment 3 Petr Matousek 2013-02-25 08:55:10 UTC
Deprecation info provided. Content approved.

Documentation used for verification:
Release Notes for the Red Hat Enterprise MRG 2 
Revision 1-12