Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "4.5 Component Reorganization"
(New page: == Introduction == As discussed at the [http://wiki.eclipse.org/TPTP_Sep_07_face_to_face#Potential_TPTP_4.5_Feature_Removals TPTP F-2-F], we have proposed to reorganize several components...) |
|||
| Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
| − | As discussed at the [http://wiki.eclipse.org/TPTP_Sep_07_face_to_face#Potential_TPTP_4.5_Feature_Removals TPTP F-2-F], we | + | As discussed at the [http://wiki.eclipse.org/TPTP_Sep_07_face_to_face#Potential_TPTP_4.5_Feature_Removals TPTP F-2-F], we are reorganizing several components to accommodate the change in resources for 4.5. |
The reorganization will be completed in 4.5 I4 (see [http://www.eclipse.org/tptp/home/project_info/releaseinfo/4.5/schedule.html 4.5 Schedule]). | The reorganization will be completed in 4.5 I4 (see [http://www.eclipse.org/tptp/home/project_info/releaseinfo/4.5/schedule.html 4.5 Schedule]). | ||
| Line 7: | Line 7: | ||
== Component Classifications == | == Component Classifications == | ||
| − | * General Availability: | + | * General Availability (GA): Core components for use by the user community and/or adoption by consuming products. |
| − | * | + | ** '''API Compatibility:''' See the [http://www.eclipse.org/tptp/home/documents/process/development/api_contract.html TPTP API Contract]. |
| − | * | + | ** '''Testing:''' Full test coverage per iteration and maintenance release. See the [http://www.eclipse.org/tptp/home/documents/process/test/test_pass_criteria.html 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. |
| − | ** | + | ** '''API Compatibility:''' See the [http://www.eclipse.org/tptp/home/documents/process/development/api_contract.html TPTP API Contract]. |
| − | ** | + | ** '''Testing:''' Smoke test coverage per iteration and maintenance release. See the [http://www.eclipse.org/tptp/home/documents/process/test/test_pass_criteria.html TPTP Test Pass Criteria]. |
| − | ** | + | ** '''Support:''' Defects and reduced community support (e.g. news group and mailing list posts). |
| − | + | * As-is: Previously GA or Technology Preview components no longer supported. | |
| + | ** '''API Compatibility:''' None. | ||
| + | ** '''Testing:''' None. | ||
| + | ** '''Support:''' None. | ||
| − | * The following components will move | + | == Proposed Component Organization == |
| + | |||
| + | * The following GA components will move to As-is: | ||
** Manual Test (test type, runner, and Manual Test View) | ** Manual Test (test type, runner, and Manual Test View) | ||
** BIRT Reports (test, log, and trace BIRT report generators) | ** BIRT Reports (test, log, and trace BIRT report generators) | ||
| + | ** RCP Log Analyzer | ||
| + | ** RCP Symptom Catalog Editor | ||
| + | |||
| + | * The following Technology Preview components will move to As-is: | ||
| + | ** Automated GUI Recording (AGR) (recorder, test type, and runner) | ||
| + | |||
| + | * The following deprecated Technology Preview components will be retired: | ||
| + | ** Code Coverage | ||
| + | ** Memory Manager | ||
| + | ** X-Ray Profiler | ||
| + | |||
| + | == Notes == | ||
| + | |||
| + | * Only GA and Technology Preview components should be promoted and presented at conferences, during webinars, and on the [http://www.eclipse.org/tptp/ 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 provided for existing users with no support (for example, defects, news group, and mailing lists). Any defects must be accompanied with fully implemented and tested patches. | ||
Revision as of 15:51, 21 November 2007
Introduction
As discussed at the TPTP F-2-F, we are reorganizing several components to accommodate the change in resources for 4.5.
The reorganization will be completed in 4.5 I4 (see 4.5 Schedule).
Component Classifications
- General Availability (GA): Core components for use by the user community and/or adoption by consuming products.
- API 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.
- API Compatibility: See the TPTP API Contract.
- Testing: Smoke test coverage per iteration and maintenance release. See the TPTP Test Pass Criteria.
- Support: Defects and reduced community support (e.g. news group and mailing list posts).
- As-is: Previously GA or Technology Preview components no longer supported.
- API Compatibility: None.
- Testing: None.
- Support: None.
Proposed Component Organization
- The following GA components will move to As-is:
- Manual Test (test type, runner, and Manual Test View)
- BIRT Reports (test, log, and trace BIRT report generators)
- RCP Log Analyzer
- RCP Symptom Catalog Editor
- The following Technology Preview components will move to As-is:
- Automated GUI Recording (AGR) (recorder, test type, and runner)
- The following deprecated Technology Preview components will be retired:
- Code Coverage
- Memory Manager
- X-Ray Profiler
Notes
- 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 provided for existing users with no support (for example, defects, news group, and mailing lists). Any defects must be accompanied with fully implemented and tested patches.