Bugzilla – Full Text Bug Listing
| Summary: | [Trace Project] Create Bugzilla component for trace reports. | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Paul Slauenwhite <paulslau> |
| Component: | TPTP | Assignee: | Alexander N. Alexeev <analexee> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | analexee, apnan, jcayne, jkubasta, sluiman |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 214749 | ||
|
Description
Paul Slauenwhite
before we do this, there seems to once again be confusion over what is platform and what is not. There are at least two issues being noted in this series of similar defects. 1 it is being asserted that the "product" in bugzilla is closely correlated to the "project" in TPTP. This is not the case or the intent. The product is simply a filter criteria created to make it easier for an end user to locate the component of interest. 2 the component name in bugzilla redundantly reflects the project it is part of. This is done to avoid duplicate names when opening defects and to ease sorting. It is a correct reflection of the component and the project it is a part of and as noted above is not correlated to the product name in bugzilla 3 components that are used or expected to be used or depended on by more than one other project in TPTP are defined to be in the platform project. For example many trace views are used by the performance and monitoring projects so are in the platform. This implies that the function is common, even though it may be considered to be a prime function of one project over another. The trace model is in fact intended to be common for all projects. There may be a few components that in hind sight do not need to be in platform, but these need to be considered one by one with the future in mind. Harm, do I understand you correctly what you suggested to make Component name more sensible for end users, who do not worried about internal project structure. If so what we can use? Probably in this case we can add them in "(Platform.UI.Reporting)". Alex. Bottom line for required changes. New component should be added. Component owner: TBD Component: Trace Reporting Bugzilla Component: Trace.UI.Reporting Include plugins: org.eclipse.tptp.trace.report.birt org.eclipse.tptp.trace.report.birt.ui org.eclipse.tptp.trace.report.birt.doc.user (In reply to comment #2) > Harm, do I understand you correctly what you suggested to make Component name > more sensible for end users, who do not worried about internal project > structure. > If so what we can use? Probably in this case we can add them in > "(Platform.UI.Reporting)". > > Alex. > > The Platform.UI.Reporting component contains the common BIRT report integration, which each subproject contributing report wizards and report types/templates in their <project name>.UI.Reporting component. /org.eclipse.hyades.releng.builder/releases/4.5.0/release_4.5.0.xml checked-in to CVS (HEAD) with new component added. resolved as fixed Verified at http://www.eclipse.org/tptp/home/project_info/structure/TPTP_Project_Info.html. Closing. |