Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

4.7 Component Reorganization

Revision as of 23:14, 1 December 2009 by Unnamed Poltroon (Talk)

  • NOTE: 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.
  • The following component will moved to As-Is:
    • Build to Manage (BtM).
  • 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:
    • 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).


  • The following deprecated Technology Preview components will be retired and removed from the build:
    • Code Coverage
    • Memory Manager
    • X-Ray Profiler
  • The following Technology Preview components will be moved to As-Is and removed from the build:
    • 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 test reports
    • 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 (see bug 219845):
    • 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 will be removed (see bug 219847) since the 'empty' plug-ins will remove the function from 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)


Notes

  • New and existing defects for As-Is components will be returned as WONTFIX with the following comment:
In TPTP 4.7, the <component name> was moved from a <General Availability (GA) or Technology Preview> component to an As-Is component. As-Is components are primarily provided for prior users but imply no support (for example, defects, news group, and mailing lists) or commitment to triage or resolve opened defects. For this defect to be considered, please re-open with an attached patch including code to resolve the symptom and test cases to test the fix.
  • 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:
In TPTP 4.7, the <component name> was moved from a <General Availability (GA) or Technology Preview> component to an As-Is component. As-Is components are primarily provided for prior users but imply no support (for example, defects, news group, and mailing lists).
  • 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
Previously General Availability (GA) or Technology Preview components are primarily provided for prior users but imply no support (for example, defects, news group, and mailing lists). There is no commitment to triage or resolve opened defects. In order to be considered, submitted patches should include code and test cases to support the fix.

Back to the top