GeoServer : GSIP 42 - Official testing team
This page last changed on Oct 02, 2009 by aaime.
Extend participation of the user base in the GeoServer evolution by setting up an official testing team.
Hopefully, but not necessarily, in time for GeoServer 2.0.
Choose one of: Under Discussion, In Progress, Completed, Rejected, Deferred
Increasing the GeoServer quality is one of the GeoServer community ongoing concerns. At the moment the Quality Assurance (QA) work is formalized only against the developers work in terms of unit testing and pre-release testing against the official OGC compliance tests.
This proposal recognizes a wide variety of testers working in diverse environments and with specific request and load patterns are necessary to keep up the good quality of a software product and thus opens to the user base providing an official testing role for anybody who is interested in improving the GeoServer release quality.
The key elements of the proposal are the testers, the release procedure changes needed to allow their timely contribution, and how to handle the resulting bug reports.
The testing team is open ended, everybody can participate. Nobody is asked to execute specific manual testing scripts, on the contrary, diversity in testing is encouraged and welcomed.
However, an official testing team will be setup that contains well known members. Those people represent the core testers, the ones that are the most engaged in the activity and that as such will be recognized and will drive the evolution of the testing along with the developers. The initial testing team is formed by:
One week before the release date a freeze is called on the GeoServer repository and no changes are allowed anymore.
During the window of development bugs are normally fixed. Those should be marked as "resolved" and have the user that reported them verify they are actually gone. If there is no such a verification this could be a good target for the testing team to check.
All regressions and critical issues found during the window will be fixed before the release:
Other issues will be scheduled as normal
This section should contain feedback provided by PSC members who may have a problem with the proposal.
There are no backwards compatibility issues
|Document generated by Confluence on May 14, 2014 23:00|