Community
Participate
Working Groups
Targeted to 4.0 by the requirements team. Please create a description document in CVS.
This enhancement is still committed for 4.0 but API needs to be marked as provisional. this means the API should still be stabilized in the 4.0 ship cycle but allows for minor adjustments as 4.1 is executed.
This is needed for 4.1
Please retarget to version 4.2 - still a P1
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
This should be considered for 4.2 release.
I don't know if a description doc exists elsewhere for this. I'm adding the following details which match a known enhancement need, although I'm not sure if it matches the original intent. Provide following at the level the RAC has: - SSL (6w) - User Authentication (2w) - Host-based authentication (1w) This info (including effort estimates) came from Sept '05 F2F discussion of data collections framework committers.
This for new API only. Backward compatibility will support this in 4.2.
Transferring ownership of new agemt controller issues with no specific target date to Mikhail for consideration in future releases.
*** This bug has been marked as a duplicate of bug 195644 ***
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.