RE: [PHP-DEV] 4.0.4

James Moore wrote:

Zak said he wouldnt be around for a few weeks so Ill try and do some of the organising zak has done for the last releases, including finishing the build tracker if he has not already done so. I also think that perhaps we should have a separate bug system for the QA'ers when doing QA work which are viewable by the developers specifically so that they know the problems we have. Unfortunatly none of the QA team is full time or avalible all the time so not every system we have avalible to us gets built on and also tested fully. If you have a system that is not listed on qa.php.net as avalible for testing and are WILLING to do some serious testing with the next release then please sign up or send an email to the qa list and we can add you too the testing pool.

Hi James, Thanks for picking up the torch! I hope to be back to my previous schedule in about 2-3 weeks. Most of the work on the build tracker should be committed to the qaweb cvs -- however, if you have any questions, please let me know. I will try still try building the RCs - this does not (usually) take a great amount of time. --zak

Hopefully then we can catch any major problems. I think that the problem we had with 4.0.3 was that the release process dragged on with various RC's and by the time you have spent a couple of hours testing one RC you dont want to have to totally retest a new RC as happened last time. The time gap inbetween the two RC's IMHO was too great enabling too many changes to be added to the CVS repository. I know we have had this argument before but I think that there are serious benifits in branching at RC1 and then not remerging but applying patches to both trees. Then we, as the QA team can help track down problems without new ones appearing before the release. I know there is a lot of opposition to branching but I thinks that it would help us avioud another pl release.