Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "COSMOS data reporting"

(Agenda)
(Agenda)
Line 42: Line 42:
 
** Graph Response Viewer pop-up dialog feature
 
** Graph Response Viewer pop-up dialog feature
 
** Partial Registration/Partial Deregistration [Done]
 
** Partial Registration/Partial Deregistration [Done]
*i11 Planning Spreadsheet
+
*i11 Planning Spreadsheet - [[Media: I11BugandErs.zip]]
 
** The following are themes used to categorize bugs and enhancements
 
** The following are themes used to categorize bugs and enhancements
 
***Stability - bugs that will improve the stability of the driver
 
***Stability - bugs that will improve the stability of the driver

Revision as of 15:18, 29 April 2008

COSMOS Main Page


Data Reporting

Meeting Title: Standing Conference Call on COSMOS Data Reporting
Link to information on Wiki: CosmosDataReportingDesign
Day & Time: Wednesday, 930 EST / 9:30am EST
Toll-free Dial-in number: +1 (866) 245-5059
Local Dial-in number: +1 (416) 343-2607
International Dial-in: +1 (800) 4444-1010
Passcode: 2771920

Contact

Email [Sheldon Lee-Loy] Phone +1 (905) 413-2610

Agenda

  • i10 open Data Visualization bugs
  • Owners of subcomponents outlined under http://wiki.eclipse.org/COSMOS_Roles_and_Responsibilities will make sure their component has appropriate junit and manual test coverage.
    • Missing registration/deregistration junit tests
    • Should move graph response manual test to /org.eclipse.cosmos.dr.tests/manual/DataVisualization.UI.Core.testsuite
  • Documentation Verification. Status
  • Need to update new features in document
    • Graph Response Viewer pop-up dialog feature
    • Partial Registration/Partial Deregistration [Done]
  • i11 Planning Spreadsheet - Media: I11BugandErs.zip
    • The following are themes used to categorize bugs and enhancements
      • Stability - bugs that will improve the stability of the driver
      • Cleanup -bugs that will help meet 1.0 release guidelines and help cleanup code
      • Improve Usability - bugs that will improve existing tooling usability
      • Framework Improvements - bugs that will improve the core ui framework
      • Improve Tooling - enhancements that will provide additional tooling to manage, visualize and query MDRs
    • Bugs and ERs were given P2,P3 or P4 priorty.
      • P1 - This is a must-have enhancement OR this enhancement blocks another enhancement that has a priority of P1 or P2.
      • P2 - This is a high priority enhancement, key to satisfying the goals of the iteration.
      • P3 - This is a medium priority enhancement that can be moved to a future iteration with minimal impact to the goals of the current iteration.
      • P4 & P5 - This is a low priority enhancement that will be addressed as time and resources permit.
    • The intentions is to fix P2, P3 bugs and fix P3 enhancements if possible
    • Bugs and ERs were given a rough sizing
      • Low - takes 1-3 days
      • Medium - takes a week
      • High - takes more than a week

Minutes of prior meetings

Back to the top