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 "Minutes-07-March-08 Summit"
(→Attendees) |
(→Process Discussion) |
||
| Line 20: | Line 20: | ||
== Process Discussion == | == Process Discussion == | ||
| + | |||
| + | === Priority vs. Severity === | ||
The problem we are working on is that "enhancement" is a severity field. Therefore, severity can't be used as a way to declare the priority of the work for enhancements. | The problem we are working on is that "enhancement" is a severity field. Therefore, severity can't be used as a way to declare the priority of the work for enhancements. | ||
| Line 26: | Line 28: | ||
For enhancements, we will use priority only. | For enhancements, we will use priority only. | ||
| − | The dependency management between | + | The dependency management between Bugzilla entries will remain a project management feature. |
| + | |||
| + | === Enhancement verification === | ||
| + | We discussed having an independent verification of enhancements at end of iteration. | ||
| + | |||
| + | We first discussed a developer doing ad hoc testing of other developers' work. This proposal was rejected due to overhead. | ||
| + | |||
| + | We finally settled on having developers present/demo the enhancements they implemented (along with relevant use cases and documentation changes) to their subproject teams. When a developer completes an enhancement, they mark it fixed. The subproject team then decides whether the enhancement should be verified. We decided this would happen on the first day of the test phase. | ||
| + | |||
| + | For i10, we decided we would do this on a pilot basis, having one enhancement presented for each subproject. The volunteers for this pilot are: | ||
| + | * DV: Bill Muldoon | ||
| + | * DC: Hubert Leung | ||
| + | * RM: David Whiteman | ||
Revision as of 10:22, 7 March 2008
Contents
Attendees
- Paul
- Jimmy
- Hubert
- Jagmit
- Martin
- John Todd
- Bill Muldoon
- Srinivas
- Rich Vasconi
- Sheldon Lee Loy
- Don Ebright
- Ruth
- David Whiteman
- Jack Devine
Minutes
Process Discussion
Priority vs. Severity
The problem we are working on is that "enhancement" is a severity field. Therefore, severity can't be used as a way to declare the priority of the work for enhancements.
The solution is that for Defects, we will use the priority and severity fields.
For enhancements, we will use priority only.
The dependency management between Bugzilla entries will remain a project management feature.
Enhancement verification
We discussed having an independent verification of enhancements at end of iteration.
We first discussed a developer doing ad hoc testing of other developers' work. This proposal was rejected due to overhead.
We finally settled on having developers present/demo the enhancements they implemented (along with relevant use cases and documentation changes) to their subproject teams. When a developer completes an enhancement, they mark it fixed. The subproject team then decides whether the enhancement should be verified. We decided this would happen on the first day of the test phase.
For i10, we decided we would do this on a pilot basis, having one enhancement presented for each subproject. The volunteers for this pilot are:
- DV: Bill Muldoon
- DC: Hubert Leung
- RM: David Whiteman