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.
OAW Decision on How to process the bug database
Revision as of 16:21, 24 June 2007 by Peter.friese.openarchitectureware.org (Talk | contribs) (New page: '''Question:''' Suggestion: # we look through all bugs after we have released 4.2 and group them into clusters (A – must fix for next release, B – would be nice to fix for next release...)
Question: Suggestion:
- we look through all bugs after we have released 4.2 and group them into clusters (A – must fix for next release, B – would be nice to fix for next release, C – can wait for release after next release, D – won’t be fixed ). We should also eliminate duplicate bugs during that phase
- we ask the sponsor companies (i.e. itemis, b+m, Gentleware, etc.) to name at least one tester who will help us setting up test cases and check if those bugs are real bugs
- the committers start fixing bugs or apply patches that might have been submitted
- test team (see (2)) tests again in order to see if the bug has gone
Result:
Procedure accepted by majority of committers
Start of poll: June 15th, 2007
End of poll: June 18th, 2007
+1 votes: 4