Some feedback on this one ...
- I am keen to give it a go (obvious since I volunteered to help test).
- Can we use the "Resolved" status a request for testers to review; and then can mark an issue "Closed" when verified.
On 18/09/2009, at 7:29 PM, Andrea Aime wrote:
Hi all,
I've put togheter a more official proposal about
an official testing team and crowdsourcing testing here:
http://geoserver.org/display/GEOS/GSIP+42+-+Official+testing+team
Things I'm not so sure about:
- the testing window length. One week over a monthly release cycle seems
a bit long for the developers, but I guess it's just right
for the testing team
I week does seem long for something like a stable release; and it almost seems to short for a release candidate where there are new features to check.
- handling the freeze: shall we freeze the branch or tag and fix any
bug against the tag too (treating the tag as a short lived branch
for a little while?)
I would freeze the branch; this is supposed to be an all hands on deck affair right?
- official testing team power: atm the official team gets recognition
and the ability to discuss (vote?) what a critical issue is.
I don't want people voting for a feature; without volunteering to test that feature (not sure if that can be arranged). For our uDig QA sprint we ignored votes and went with what our testers were willing to verify in order to make best use of resources.
Can we offer more? Should we ask more? (like, try to participate in the testing of every release... thought I fear this
will end up scaring away people, whilst we want as much testing as possible)
We are offering a heck of a lot right now (a week of trunk being frozen); collaboration with a developer if you are part of the testing team; ability to get a patch reviewed right then and there ... and by the same token we are asking a lot (download geoserver each day; be very careful in reproducing the steps exactly; send an error log; sign up for jira etc...
So let us try to make it as easy to take part as possible; and adjust based on how the first one goes.
Jody