Community
Participate
Working Groups
Native Common Base Event implementation XML serialization APIs should return required size instead of -1. When users call the native Common Base Event implementation XML serialization APIs with a buffer of a predefined size, if the buffer is too small, the API should return the required size as a performance improvement instead of forcing the user to recall the API continuously with a larger buffer until sufficient space is required. Alternatively, a convenience API that walked the Common Base Event struct to determine the estimated XML serialized size.
Now that we have a "3.3" Version in bugzilla, updating bugzillas targeted to 3.3 or a 3.3 iteration so that their Version matches their Target. "future", "unspecified", "4.0", and "4.1" Versions will not be updated.
Sizing: 1 PW
Created attachment 20591 [details] Partial fix.
Deferring from 4.1 as per the official 4.1 enhancement plan. http://eclipse.org/tptp/home/project_info/featureplans/features.php?source=All&project=All&release=4.1&file=TPTPFeatures_4.1.xml
P2 Highly desirable and planned for this release, but not stop ship
Theme(s) for this enhancement: -Simple to Use
Batch update of all TPTP platform enhancements that are not part of 4.2 approved plan. Set version to "future" and target milestone to "--".
Transitioning to new component owner (Cindy Jin).
Due to lack of resources this enhancement request is resolved as WONTFIX. Please feel free to reopen if you consider it's a required enhancement.
Closing.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html).
