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 (Work In Progress)) |
(→How do we ensure quality in the WTP Project?) |
||
Line 9: | Line 9: | ||
*'''Continuous and Integration Builds''' | *'''Continuous and Integration Builds''' | ||
*'''Releasing early in the dev cycle at predictable intervals''' | *'''Releasing early in the dev cycle at predictable intervals''' | ||
+ | **Among other things, this allows users to test functionality and find bugs before the software is released | ||
*'''Focus on bug reports''' | *'''Focus on bug reports''' | ||
**Ensure that meaningful bugs from the community are addressed in a reasonable time period | **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 | + | **This is another place where the community can have an impact on the overall quality of the project through both entering bugs and by fixing them |
− | + | ||
===Related Bug Reports=== | ===Related Bug Reports=== | ||
[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Total Bugs by Severity] | [https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Total Bugs by Severity] |
Revision as of 18:50, 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
- Among other things, this allows users to test functionality and find bugs before the software is released
- Focus on bug reports
- Ensure that meaningful bugs from the community are addressed in a reasonable time period
- This is another place where the community can have an impact on the overall quality of the project through both entering bugs and by fixing them