Bugzilla – Full Text Bug Listing
| Summary: | Additionnal node in the profiling monitor | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Stephane Moline <molinest> |
| Component: | TPTP | Assignee: | Valentina Popescu <popescu> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | cheryladams, ewchan, gridings, sylvain.duguet, who |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | housecleaned460 | ||
| Bug Depends on: | |||
| Bug Blocks: | 58385 | ||
|
Description
Stephane Moline
Wayne, can you comment on this one? It's related to the explicit merge feature. We need to come up with the right terminology and make things simple and easy to understand. Stephane, do you need anything to be added to the model to enable agents mergeing? If yes then open a feature against the model also. If you need this for 4.0, you need to go (ASAP) through the requirments process (send a note to Serge or Harm) and get approval for this feature(s). Also the priority should be P1 if you want it to be done. 4.0 plan is already closed The 4.1 plan is closing this Friday so this cna be reviewed for 4.1 This bug does seem related to Bug 58385 on providing an explicit merge in the Profiling Monitor view. Bug 58385 describes the use of a folder to hold the merged objects, as well as an action (toolbar and context menu action) to perform the merge. I agree that we need to come up with good terminology. Stephane, would you consider this a duplicate or are there addition features you require? Once we understand the requirements (if there are additional ones) from this bug we can brainstorm some terminology ideas. I need this feature for 4.1 The explicit merge (Bug 58385) is a part of my requirements, also I need to add a new Profiling Monitor node to compare runs. These two features can be made by adding folders and "link" nodes in the Profiling Monitor. Regarding the model, I don't know if these changes affect it. If the explicit log correlations in the log navigator required model changes, then I'm guessing this one will probably require some too, as they are quite similar. Along the same line, we should be careful to make these two things (correlating logs & merging traces) consistent in terms of user experience. Do you still have any need for the monitor node, or can we remove this one? Modeling wise they are different, correlating means linking (by building association objects) and mergeing means combining. Of course the UI should have a consistent way of presenting these concepts. You will need a way to tag the merged resources, so they will show up correctly in the UI, also a way to identify the agents/resources involved in the merge operation. This feature will be used to create a diff capabilitiy for the profiling/logging data. The user should be able to select two ( possibly more ) traces and open a view to show the difference between them. Some of the existing views can be used ( the statistical view has a delta capability, but this is thighly linked with showing delta between consecutive refreshes on the same trace file ). Ideally, a generic viewer similar with the Eclipse Team Support compare viewer might be used to visualize tabular data. 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 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 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 As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html). As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html). Done |