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.
Difference between revisions of "Equinox/p2/Meetings/20080915"
Line 24: | Line 24: | ||
* p2 get together | * p2 get together | ||
** Should we have a p2 face-to-face meeting to coincide with the [[Build Workshop 3: Build Hard With A Purpose]]? | ** Should we have a p2 face-to-face meeting to coincide with the [[Build Workshop 3: Build Hard With A Purpose]]? | ||
+ | ** Focus would be on designing/implementing items on the Galileo plan, not gathering new requirements or exploring new directions. | ||
+ | ** Pascal to send a note to gauge community interest | ||
* Testing/Robustness | * Testing/Robustness | ||
** 3.5 M2 has quality problems, regressions from 3.4. | ** 3.5 M2 has quality problems, regressions from 3.4. | ||
Line 30: | Line 32: | ||
** Currently we have roughly 33% test coverage, should aim for 50-60% as an initial improvement target | ** Currently we have roughly 33% test coverage, should aim for 50-60% as an initial improvement target | ||
** We will also revise manual p2 UI test scripts | ** We will also revise manual p2 UI test scripts | ||
+ | ** Need to explore how to set up tests for transport problems, server failures. | ||
* 3.4.1 status: ship it | * 3.4.1 status: ship it | ||
* Wiki update | * Wiki update |
Revision as of 11:47, 15 September 2008
Agenda
- Galileo plan
- Testing/Robustness
- 3.4.1 status
- Wiki update
Attendees
- Andrew Cattle
- Andrew Niefer
- DJ Houghton
- Jeff McAffer
- John Arthorne
- Pascal Rapicault
- Simon Kaegi
- Susan McCourt
Minutes
- Galileo plan
- p2 get together
- Should we have a p2 face-to-face meeting to coincide with the Build Workshop 3: Build Hard With A Purpose?
- Focus would be on designing/implementing items on the Galileo plan, not gathering new requirements or exploring new directions.
- Pascal to send a note to gauge community interest
- Testing/Robustness
- 3.5 M2 has quality problems, regressions from 3.4.
- Need to focus more on testing and verification to prevent embarrassing regressions
- This week we will try a testing week where everyone focuses on testing and authoring p2 tests
- Currently we have roughly 33% test coverage, should aim for 50-60% as an initial improvement target
- We will also revise manual p2 UI test scripts
- Need to explore how to set up tests for transport problems, server failures.
- 3.4.1 status: ship it
- Wiki update