RE: [PHP-QA] Re: [PHP-DEV] 4.2.3

From: Date: Sat, 17 Aug 2002 19:39:26 +0000
Subject: RE: [PHP-QA] Re: [PHP-DEV] 4.2.3
References: 1  Groups: php.dev php.qa 
Request: Send a blank email to php-dev+get-86969@lists.php.net to get a copy of this message
At 22:28 17/08/2002, Xavier Spriet wrote:
This is quiteconcerning. It appears the PHP release process is not suited to the way PHP is developed anymore and this can lead in severe inconsistencies. What seemed to have happened is that several bugfixes were fixed in CVS instead of the bugfix release which if fine with me... but the bugs in question are pretty important. This seems to be partly due to a lack of communication between developement and QA since this problem was aborded weeks ago already and Sebastian Nohn raised that question on several occasions. The way the developement team and qa can improve the organisation for better communication can be solved easily in the upcoming weeks, however, it seems now we have to face a more important problem. IMHO, it is important that the 64bits architecture related bugs be fixed in the next release as most of the people that will be pissed off if it doesn't, are business users that absolutely need a modern release to work in their environement or will simply stop supporting PHP in their environement/business.
I haven't been following the commits too closely lately, but I don't think that the 64-bit fixes are mandatory for the next bug-fix release. Depending on how far-reaching they are, they may or may not make sense to include in a bug fix release, if we end up having one. If we decide in favour of having a bug-fix release, but against including the 64-bit fixes (for whatever reason), I think that's quite alright. 64-bit support is a major thing, which people, especially businesses, will not really expect to be implemented in a bug-fix release.
Many good suggestions have been made, mine is to find out which bugs were "fixed in CVS" and are important and spend the week on backporting them to the bugfix release, 4.2.3 We can have a RC1 ready for next monday and no doubt we won't need a RC2 and can release later that week. Do you guys think this could be done in an acceptable timeframe ?
I discussed this with several people from #php.bugs. That's pretty much what we arrived to as well. I think 4.2.3 makes perfect sense as long as it gets started immediately, immediately being sometime within the next few days. Zeev

« previous php.dev (#86969) next »