Lukas To move this process forward, is there any chance that you could make a few changes to http://oss.backendmedia.com/ReleaseChecklist?
First add an extra item to 'Getting the Release Candidate out there' saying: Email [EMAIL PROTECTED] to notify the primary testers to get testing. An example email is here: ----------------------- Hello! You are receiving this email because you have volunteered to be a php primary tester. Can you please test the latest PHP release candidate on the platform and with the applications you have volunteered to be responsible for (and also if possible do a make test and allow it to post the results to the php-qa list). For a reminder of what you volunteered to test, check the table at http://www.dialsolutions.com/phil/php/primarytesters.html. Please report back by <some date - maybe a week in the future> to <[EMAIL PROTECTED]> and cc internals@lists.php.net, letting us know what applications you tested, on what platforms and informing us of success or failure. Until we have had sufficient responses from our primary testers to be sure that this RC performs well on a range of applications and platforms, we will not go ahead with the release. Consequently, your input to this process is very important. If you are unable for any reason to test this RC, please notify [EMAIL PROTECTED] as soon as possible so that we can make alternative arrangements this time. If you do not want to receive these heads-up emails, please reply to me personally and I will remove you from the list; but, we hope that you want to actively help us making PHP a better and more stable tool. The first release candidate of PHP N can be found at http://downloads.php.net/somewhere/ . If you know anyone else who would like to be a PHP primary tester, please let me know. regards, <Whoever> PHP <N> Release Manager ----------------------- Then add a new item between 'Getting the Release Candidate out there' and 'Rolling a release' entitled 'Making sure that the Release Candidate is fit to become a release': 1. Await responses from the primary testers, and issue a reminder email to [EMAIL PROTECTED] if responses are slow to come in. 2. Keep an eye on the make test results for the RC posted to the php-qa list looking out for any significant problems. 3. Check that problem-free responses have been received in respect of all the critical applications and platforms listed (with their volunteers) at http://www.dialsolutions.com/phil/php/primarytesters.html (which I am happy to look after, but another wiki page may be more sensible), and if necessary chase up individual volunteers for their results. Please feel free to add/delete/amend as appropriate. Suggestions and volunteers welcome :) -- Phil Driscoll -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
