-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd like to propose the following.
* Develop a list of Rave features that should be tested, put this on the wiki, and update it every time a new feature is added. I'm happy to get this started. Recommendations for tools to automate some of this are welcome. * Regular testing of the above feature list (not just in preparation for releases). We would need a record of this (who tested, when, etc). If we do this manually, we could keep records by updating the wiki, posting to the dev list, etc. Recommendations for better tools are of course welcome. * All features should be tested before release by at least one person. The Release Manager should coordinate this. We could continue to do this as part of the current Release Candidate process, but it may be better to have an intermediate SVN tag that can go through QA before we start an official vote. This would allow us to keep the trunk open for commits while we test and avoid canceled releases. I'm not a QA expert, so comments welcome. Marlon -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPfzueAAoJEEfVXEODPFIDPb0IAJT5Op6iaQbKgO5Jp9wBjsCp oC2Jxk5HrGolbavE8yi0LDAGv8x52mo1U8+m7PfRT6yhQ38ciMMkm8I7W2BYZ2Ei WWX1kerVriICKV4LSfZ3u503OJ77WYlhoOsJwvvZEvxYndKuhroYyxDIZ0PdTsGI GRp7Iu4r9My4AOz+bIh4EaAWE+VKHhS9INoHvfsm6Fb8vxAyvSNfklgtOiZoTSlg g4BxvEPlkxs5Xv3jTFaX/rgGWoKU31LkL8mSLIeW64BWXBqXMscZSTSW/l5Brx/8 dJLnuHUmmSJLjKhzELNaDH68Rntb1WFV+oWsWf8xBqawYKXkVElqNywTh5yOxb8= =1anU -----END PGP SIGNATURE-----
