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.
COSMOS data reporting
Revision as of 13:04, 30 April 2008 by Unnamed Poltroon (Talk)
Contents
Data Reporting
Meeting Title: | Standing Conference Call on COSMOS Data Reporting |
Link to information on Wiki: | CosmosDataReportingDesign |
Day & Time: | Wednesday, 1030 EST / 10: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 Status
- i10 open Data Visualization bugs
- i10 bug verification [Owners will verify bugs with i10 candidate builds]
- 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 [Leonard will create new manual tests]
- Should move graph response manual test to /org.eclipse.cosmos.dr.tests/manual/DataVisualization.UI.Core.testsuite [Martin will do this]
- Documentation Verification. Status
- Need to update new features in document
- Graph Response Viewer pop-up dialog feature [Martin will complete this week. Sheldon will talk with Richard how to get him the update]
- Partial Registration/Partial Deregistration [Done]
i11 Planning
- 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
- The following are themes used to categorize bugs and enhancements
Minutes of prior meetings
- COSMOS Data Reporting 15-Mar-2007
- COSMOS Data Reporting 01-Mar-2007
- COSMOS Data Reporting 15-Feb-2007
- COSMOS Data Reporting 08-Feb-2007
- COSMOS Data Reporting 01-Feb-2007
- COSMOS Data Reporting 18-Jan-2007
- COSMOS Data Reporting 04-Jan-2007
- December 04, 2006
- COSMOS Data Reporting 11-Oct-2007
- COSMOS Data Reporting 18-Oct-2007
- COSMOS Data Reporting 25-Oct-2007
- COSMOS Data Reporting 3-Nov-2007
- COSMOS Data Reporting 9-Nov-2007 cancel due to F2F meeting
- COSMOS Data Reporting 16-Nov-2007
- COSMOS Data Reporting 22-Nov-2007 cancel due to Thanksgiving holiday
- COSMOS Data Reporting 29-Nov-2007
- COSMOS Data Reporting 6-Dec-2007
- COSMOS Data Reporting 13-Dec-2007
- COSMOS Data Reporting 20-Dec-2007
- COSMOS Data Reporting 3-Jan-2008
- COSMOS Data Reporting 10-Jan-2008
- COSMOS Data Reporting 17-Jan-2008 repurposed to discuss i8 build integration issues.
- COSMOS Data Reporting 24-Jan-2008
- Meetings after Jan 24th and before April 2nd 2008 are covered under the Architecture Meetings
- COSMOS Data Reporting 2-Apr-2008
- COSMOS Data Reporting 9-Apr-2008
- COSMOS Data Reporting 16-Apr-2008
- COSMOS Data Reporting 23-Apr-2008
- COSMOS Data Reporting 30-Apr-2008