Difference between revisions of "4.7 Component Reorganization"

Revision as of 15:00, 8 December 2009

DISCLAIMER: The following is the proposed TPTP 4.7 component reorganization. It has not been approved by the PMC yet. It is still Work in Progress.

Refer to 4.5 Component Reorganization for component reorganization that took place in TPTP 4.5.0.

Component Classifications

• General Availability (GA): Core components for use by the user community and/or adoption by consuming products.
  • Compatibility: See the TPTP API Contract.
  • Testing: Full test coverage per iteration and maintenance release. See the TPTP Test Pass Criteria.
  • Support: Enhancements, defects and community support (e.g. news group and mailing list posts).

• Technology Preview: Incubator components for evaluation and experimentation by the user community and consuming products.
  • Compatibility: See the TPTP API Contract.
  • Testing: Smoke test coverage per iteration and maintenance release. See the TPTP Test Pass Criteria.
  • Support: As with GA components but at a lower priority.

• As-Is: Previously GA or Technology Preview components no longer supported.
  • Compatibility: None.
  • Testing: None.
  • Support: None.

Component Organization

• The following component will moved to As-Is:
  • Build to Manage (BtM) (see bug 297134).
    • ARM
    • Managed Agent Explorer
    • Monitoring Instrumentation
    • MX4J

• The following components will stay in As-Is but will remain in the build:
  • BIRT Reports (test and trace).
  • Automated GUI Recording (AGR) (recorder, test type, and runner)

• The following As-Is components will be removed from the build (see bug 297132):
  • Perfmon (monitoring agent and statistical views).
  • Manual Test (test type, runner, and Manual Test View).
  • BIRT Reports (log, and statistical BIRT report generators).
  • RCP Log Analyzer and Symptom Catalog Editor (see bug 209057 and bug 212788).
  • Log and Trace Analyzer.

• The following deprecated Technology Preview components will be retired and removed from the build (see bug 297131):
  • Code Coverage
  • Memory Manager
  • X-Ray Profiler

• The following Technology Preview components will be moved to As-Is and removed from the build (see bug 297131):
  • API Recorder Framework
  • Build-to-Manage Toolkit for .NET
  • C/C++ Code Review Provider

• All other components are GA components.

Building and Packaging

• The As-Is components will not be built or packaged. The only exceptions are:
  • BIRT Reports (test and trace).
  • AGR

• For the following GA components that has move to As-Is components, the features and plug-ins will continue to be packaged in the TPTP 4.7 release, except the plug-ins will be 'empty', containing only a manifest file:
  • Build to Manage

• When existing users of TPTP and consuming products update their TPTP 4.6.2 or below installation to 4.7 using either the Update Manager or downloaded ZIPs, the empty plug-ins will be loaded by Eclipse since they have a newer version number, thereby removing the function from the installation.

• In TPTP 4.7, the 'empty' plug-ins and associated features for the following components that had moved to As-Is in TPTP 4.5 will be removed (see bug 219847) since the 'empty' plug-ins will remove the function from TPTP 4.5+ updates:
  • Perfmon (monitoring agent and statistical views)
  • Manual Test (test type, runner, and Manual Test View)
  • BIRT Reports (test, log, trace, and statistical BIRT report generators)

• In TPTP 4.8, the 'empty' plug-ins and associated features for the following components that had moved to As-Is in TPTP 4.7 will be removed (see bug 219847) since the 'empty' plug-ins will remove the function from TPTP 4.7+ updates:
  • Build to Manage

Notes

• New and existing defects for As-Is components will be returned as WONTFIX with the following comment:

• New news group and mailing list posts on As-Is components that cannot be easily answered (for example, configuration problems, installation issues, etc.) will be answered with the following reply:

• Re-activation and contribution will be considered if there is community support.

• Preferably only GA and Technology Preview components should be promoted and presented at conferences, during webinars, and on the TPTP web site.

• The As-Is section on the TPTP download site will contain the following disclaimer