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 "WTP Quality"
(→Thoughts on quality for the Web Tools Project) |
(→Thoughts on quality for the Web Tools Project (Work In Progress)) |
||
Line 1: | Line 1: | ||
− | ==Thoughts on | + | ==Thoughts on Quality for the Web Tools Project (Work In Progress)== |
This wiki page should describe how the WTP addresses the issue of Quality. This page is a work in progress, and does not necessarily describe the views of the WTP PMC. | This wiki page should describe how the WTP addresses the issue of Quality. This page is a work in progress, and does not necessarily describe the views of the WTP PMC. | ||
Revision as of 18:46, 19 March 2007
Thoughts on Quality for the Web Tools Project (Work In Progress)
This wiki page should describe how the WTP addresses the issue of Quality. This page is a work in progress, and does not necessarily describe the views of the WTP PMC.
How do we ensure quality in the WTP Project?
- High committer standards
- More than anything else, high quality committers will result in high quality software
- Adequate JUnit tests for components
- Necessary for early bug detection in the lifecycle and future maintainability of the software
- Continuous and Integration Builds
- Releasing early in the dev cycle at predictable intervals
- Focus on bug reports
- Ensure that meaningful bugs from the community are addressed in a reasonable time period
- This is where the community can have an impact on the overall quality of the project through both entering bugs and by fixing them