Re: [PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] 4.2.3
On Sun, 18 Aug 2002, Edin Kadribasic wrote: Exactly right. During the last release cycle, Derick made elaborate test cases, etc. but the result was not very promising. Very few people actually took part in the QA process and as a result 4.2.0 was released with some serious bugs in it. I believe that 4.2.3 should be released, and that it should be very fast. If Derick has no time for the release, and Zeev volunteers to do it, I really see no point in delaying it further. Especially since 4.3.0 release doesn't seem to be very near. I'd like to hear Stig's opinion on 4.3.0 first, and I tend to agree that we need a 4.2.3 too. I can even find time to do the release process and manage QA, providing there is any feedback to the RC. Derick --- Did I help you? http://www.derickrethans.nl/link.php?url=giftlist Frequent ranting: http://www.derickrethans.nl/ --- PHP: Scripting the Web - [EMAIL PROTECTED] All your branches are belong to me! SRM: Script Running Machine - www.vl-srm.net --- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] 4.2.3
At 10:12 19/08/2002, [EMAIL PROTECTED] wrote: I'd like to hear Stig's opinion on 4.3.0 first, and I tend to agree that we need a 4.2.3 too. I can even find time to do the release process and manage QA, providing there is any feedback to the RC. I would actually like to do that once, if you don't mind :) Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] 4.2.3
On Mon, 19 Aug 2002, Zeev Suraski wrote: At 10:12 19/08/2002, [EMAIL PROTECTED] wrote: I'd like to hear Stig's opinion on 4.3.0 first, and I tend to agree that we need a 4.2.3 too. I can even find time to do the release process and manage QA, providing there is any feedback to the RC. I would actually like to do that once, if you don't mind :) I don't mind at all... but what is the reason for this? :) Derick --- Did I help you? http://www.derickrethans.nl/link.php?url=giftlist Frequent ranting: http://www.derickrethans.nl/ --- PHP: Scripting the Web - [EMAIL PROTECTED] All your branches are belong to me! SRM: Script Running Machine - www.vl-srm.net --- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] 4.2.3
At 10:15 19/08/2002, [EMAIL PROTECTED] wrote: I would actually like to do that once, if you don't mind :) I don't mind at all... but what is the reason for this? :) Well, first it's been a while since I did, but I'd also like to see it working in the 'new way' once, with the automated QA... Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] 4.2.3
On Mon, 19 Aug 2002, Zeev Suraski wrote: At 10:15 19/08/2002, [EMAIL PROTECTED] wrote: I would actually like to do that once, if you don't mind :) I don't mind at all... but what is the reason for this? :) Well, first it's been a while since I did, but I'd also like to see it working in the 'new way' once, with the automated QA... Since when do we have automated QA? :) To what are you referring here? Derick --- Did I help you? http://www.derickrethans.nl/link.php?url=giftlist Frequent ranting: http://www.derickrethans.nl/ --- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] 4.2.3
At 10:22 19/08/2002, [EMAIL PROTECTED] wrote: On Mon, 19 Aug 2002, Zeev Suraski wrote: At 10:15 19/08/2002, [EMAIL PROTECTED] wrote: I would actually like to do that once, if you don't mind :) I don't mind at all... but what is the reason for this? :) Well, first it's been a while since I did, but I'd also like to see it working in the 'new way' once, with the automated QA... Since when do we have automated QA? :) To what are you referring here? Well, semi-automatic... Those 'PHP Test Results' letters don't appear to be human generated :) Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] 4.2.3
-Original Message- From: Zeev Suraski [mailto:[EMAIL PROTECTED]] Sent: Monday, August 19, 2002 9:20 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] 4.2.3 At 10:22 19/08/2002, [EMAIL PROTECTED] wrote: On Mon, 19 Aug 2002, Zeev Suraski wrote: At 10:15 19/08/2002, [EMAIL PROTECTED] wrote: I would actually like to do that once, if you don't mind :) I don't mind at all... but what is the reason for this? :) Well, first it's been a while since I did, but I'd also like to see it working in the 'new way' once, with the automated QA... Since when do we have automated QA? :) To what are you referring here? Well, semi-automatic... Those 'PHP Test Results' letters don't appear to be human generated :) They are. http://qa.php.net/buildtest-submit.php ;) Regards, Sebastian Nohn -- +49 170 471 8105 - [EMAIL PROTECTED] - http://www.nohn.net/ PGP Key Available - Did I help you? Consider a gift: http://www.amazon.de/exec/obidos/wishlist/3HYH6NR8ZI0WI/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] 4.2.3
As long as there is momentum on the development process and on the QA process when needed, I don't think release momentum matters that much. It is important to keep up with the current development for 4.3.0 and also for future implementation of ze2, which I think probably takes some time. However, a bugfix release is probably expected any time now, and yeah... maybe the qa process for a 4.2.3 RC could start in the next few days, I'm willing to provide as much time as I have available if it does. I still believe backporting as many bugfixes as possible would make the transition from 4.2.3 to 4.3.0 much better for everyone. -Original Message- From: Zeev Suraski [mailto:[EMAIL PROTECTED]] Sent: Sun 18/08/2002 2:35 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [PHP-QA] Re: [PHP-DEV] 4.2.3 I did not intend to reply to that, but generally, the reasons I think 4.2.3 should either be released in the immediate future or not released at all are (a) clashing with the 4.3.0 release process (b) momentum. The most serious problem PHP releases have suffered from, in my opinion, ever sense v4.1.0 (inclusive), is lost momentum. I was (am) willing to coordinate the release of 4.2.3 provided it gets ignited within a couple of days. Zeev At 03:16 18/08/2002, [EMAIL PROTECTED] wrote: On Sat, 17 Aug 2002, Sascha Schumann wrote: I think 4.2.3 makes perfect sense as long as it gets started immediately, immediately being sometime within the next few days. Is there some event I'm not aware of that a few days matter to you? If not, I don't see any problem with merging all important fixes and commencing the QA process afterwards. I agree with that. Derick --- Did I help you? http://www.derickrethans.nl/link.php?url=giftlist Frequent ranting: http://www.derickrethans.nl/ --- PHP: Scripting the Web - [EMAIL PROTECTED] All your branches are belong to me! SRM: Script Running Machine - www.vl-srm.net --- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Quality Assurance Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] 4.2.3
At 22:20 18/08/2002, Xavier Spriet wrote: As long as there is momentum on the development process and on the QA process when needed, I don't think release momentum matters that much. Right. Since the first part of the sentence does not stand in reality, the direct result is that momentum matters, a lot :) Lack of momentum is the main reason PHP releases are taking several weeks now. It's not as if people are testing it thoroughly for weeks and weeks... Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] 4.2.3
Lack of momentum is the main reason PHP releases are taking several weeks now. It's not as if people are testing it thoroughly for weeks and weeks... I have a dev box I can test my installation setup on with dev releases of PHP ... where do I sign up? (If needed) -- Dan Hardiker [[EMAIL PROTECTED]] ADAM Software Systems Engineer First Creative Ltd -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] 4.2.3
As long as there is momentum on the development process and on the QA process when needed, I don't think release momentum matters that much. Right. Since the first part of the sentence does not stand in reality, the direct result is that momentum matters, a lot :) Lack of momentum is the main reason PHP releases are taking several weeks now. It's not as if people are testing it thoroughly for weeks and weeks... Exactly right. During the last release cycle, Derick made elaborate test cases, etc. but the result was not very promising. Very few people actually took part in the QA process and as a result 4.2.0 was released with some serious bugs in it. I believe that 4.2.3 should be released, and that it should be very fast. If Derick has no time for the release, and Zeev volunteers to do it, I really see no point in delaying it further. Especially since 4.3.0 release doesn't seem to be very near. Edin -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] 4.2.3
Okay then... let's start up the QA process whenever you guys are ready and I'll test as much as I can on 2 of our developement machines, one on linux the other one on SPARC 64. I'll start as soon as the process is ignited. Let's get to work and give it some momentum ;) -Original Message- From: Edin Kadribasic [mailto:[EMAIL PROTECTED]] Sent: Sun 18/08/2002 4:21 PM To: Xavier Spriet; Zeev Suraski Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [PHP-QA] Re: [PHP-DEV] 4.2.3 As long as there is momentum on the development process and on the QA process when needed, I don't think release momentum matters that much. Right. Since the first part of the sentence does not stand in reality, the direct result is that momentum matters, a lot :) Lack of momentum is the main reason PHP releases are taking several weeks now. It's not as if people are testing it thoroughly for weeks and weeks... Exactly right. During the last release cycle, Derick made elaborate test cases, etc. but the result was not very promising. Very few people actually took part in the QA process and as a result 4.2.0 was released with some serious bugs in it. I believe that 4.2.3 should be released, and that it should be very fast. If Derick has no time for the release, and Zeev volunteers to do it, I really see no point in delaying it further. Especially since 4.3.0 release doesn't seem to be very near. Edin
[PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] 4.2.3
As soon as Dan K signals that the patch-backporting phase is over (should happen by tomorrow or the next day; he's coordinating with other backporters), we'll get started. Zeev At 23:30 18/08/2002, Xavier Spriet wrote: Okay then... let's start up the QA process whenever you guys are ready and I'll test as much as I can on 2 of our developement machines, one on linux the other one on SPARC 64. I'll start as soon as the process is ignited. Let's get to work and give it some momentum ;) -Original Message- From: Edin Kadribasic [mailto:[EMAIL PROTECTED]] Sent: Sun 18/08/2002 4:21 PM To: Xavier Spriet; Zeev Suraski Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [PHP-QA] Re: [PHP-DEV] 4.2.3 As long as there is momentum on the development process and on the QA process when needed, I don't think release momentum matters that much. Right. Since the first part of the sentence does not stand in reality, the direct result is that momentum matters, a lot :) Lack of momentum is the main reason PHP releases are taking several weeks now. It's not as if people are testing it thoroughly for weeks and weeks... Exactly right. During the last release cycle, Derick made elaborate test cases, etc. but the result was not very promising. Very few people actually took part in the QA process and as a result 4.2.0 was released with some serious bugs in it. I believe that 4.2.3 should be released, and that it should be very fast. If Derick has no time for the release, and Zeev volunteers to do it, I really see no point in delaying it further. Especially since 4.3.0 release doesn't seem to be very near. Edin -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] 4.2.3
At 22:21 18-8-2002, Edin Kadribasic wrote: As long as there is momentum on the development process and on the QA process when needed, I don't think release momentum matters that much. Right. Since the first part of the sentence does not stand in reality, the direct result is that momentum matters, a lot :) Lack of momentum is the main reason PHP releases are taking several weeks now. It's not as if people are testing it thoroughly for weeks and weeks... Exactly right. During the last release cycle, Derick made elaborate test cases, etc. but the result was not very promising. Very few people actually took part in the QA process and as a result 4.2.0 was released with some serious bugs in it. And those who did take part were confronted with Oh yeah, that test is not good (I don't mean the special cases that Derick compiled, as they are more aimed at compilation). So again: Is the testkit QA-proof? Are the tests that fail, failing due to a bug or a buggy test script? See below for php-STABLE, on AIX. Especially the array stuff, where many fixes have gone and the first three fail and everything relating to aggregation fails. Since we know the OO bug test is bogus, can we remove that? Further more - how about adopting the regression tests that Sebastion Nohn has compiled? And since we're providing bcmath as a module, I'm surprised there are no tests for that. I believe that 4.2.3 should be released, and that it should be very fast. If Derick has no time for the release, and Zeev volunteers to do it, I really see no point in delaying it further. Especially since 4.3.0 release doesn't seem to be very near. +1 Another argument for it: Having a stable 4.2 release invites people to play with the new features in 4.3. $ grep failed ./test.out Session Object Serialization (001.phpt) ... failed Session Object Deserialization (003.phpt)... failed session_set_save_handler test (004.phpt) ... failed Custom save handler, multiple session_start()s, complex data structu ... failed References between variables in sessions (006.phpt) ... failed aggregating everything (aggregate.phpt) ... failed aggregating all methods (aggregate_methods.phpt) ... failed aggregating methods specified in the list (aggregate_methods_by_list ... failed aggregating methods matching regular expression (aggregate_methods_b ... failed aggregating all default properties (aggregate_properties.phpt) ... failed aggregating default properties specified in the list (aggregate_prop ... failed aggregating default properties matching regular expression (aggregat ... failed retrieving aggregation info (aggregation_info.phpt) ... failed deaggreating (deaggregate.phpt) ... failed Test array_merge and array_walk (001.phpt) ... failed Test arsort, asort, krsort, ksort, rsort, and sort (002.phpt)... failed Test usort, uksort and uasort (003.phpt) ... failed Tests for floor en ceil (floorceil.phpt) ... failed Various pow() tests (pow.phpt) ... failed strtotime() function (002.phpt) ... failed DB configurable error handler test (db_error2.phpt) ... failed XML Parser: parse from file (002.phpt) ... failed XML Parser: parse from file resource (003.phpt) ... failed PEAR_Config (pear_config.phpt) ... failed PEAR_Error: default error handling (pear_error3.phpt)... failed Simple POST Method test (002.phpt) ... failed GET and POST Method combined (003.phpt) ... failed Two variables in POST data (004.phpt)... failed Three variables in POST data (005.phpt) ... failed Testing $argc and $argv handling (011.phpt) ... failed Output buffering test (006.phpt) ... failed OO Bug Test (Bug #7515) (029.phpt) ... failed Tests failed: 32 ( 24%) Met vriendelijke groeten / With kind regards, Webmaster IDG.nl Melvyn Sopacua -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] 4.2.3
On Sat, 17 Aug 2002, Dan Kalowsky wrote: I disagree that it should go out as is, very strongly at that too. I agree with Dan here. - Sascha -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-QA] RE: [PHP-DEV] 4.2.3
At 17:52 17/08/2002, Sebastian Nohn wrote: No! This simply confuses users! Someone reported a bug n weeks ago, this bug has been fixed in CVS n-x weeks ago. Now there is a new release an WOW! this bug is'nt fixed! Fixed in CVS means fixed in CVS and the user expects this bug to be fixed in the next release. I believe that 'fixed in CVS' should be changed then. As the versioning scheme was changed (against my opinion), the bugs database has to be consistent with it. Instead of 'fixed in CVS', which is now meaningless, there should be 'fixed in the next bug-fix release' or 'fixed in the next semi-major release'. Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] 4.2.3
there should be 'fixed in the next bug-fix release' or 'fixed in the next semi-major release'. How about Will be fixed in version major.minor.buildrelease ?? ie tell them which version it will be fixed in, no confusion at all then -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] 4.2.3
Isnt this what a bug/change log is for... If its not in the change log it wasnt put in yet. Just add a small comment at the top. Not all changes currently in CVS may be in this release due to blah blah blah contraints On Sat, 2002-08-17 at 11:19, Liz wrote: there should be 'fixed in the next bug-fix release' or 'fixed in the next semi-major release'. How about Will be fixed in version major.minor.buildrelease ?? ie tell them which version it will be fixed in, no confusion at all then -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] 4.2.3
Because we aren't always sure what the next version will be. Witness the 4.0.6-4.0.7/4.1 release process. On Sat, 17 Aug 2002, Liz wrote: there should be 'fixed in the next bug-fix release' or 'fixed in the next semi-major release'. How about Will be fixed in version major.minor.buildrelease ?? ie tell them which version it will be fixed in, no confusion at all then --- Dan KalowskyA little less conversation, http://www.deadmime.org/~danka little more action. [EMAIL PROTECTED]- A Little Less Conversation, [EMAIL PROTECTED]Elvis Presley -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] 4.2.3
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. 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 ? Thanks. -Original Message- From: Zeev Suraski [mailto:[EMAIL PROTECTED]] Sent: Sat 17/08/2002 11:37 AM To: Rasmus Lerdorf Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [PHP-QA] Re: [PHP-DEV] 4.2.3 It's not a matter of what we call it - I thought it would make sense to release a new version based on the 4.2 branch, because 4.3 has TONS of new features and is thus very likely to introduce new inconsistencies and bugs. As people have said here several times in the last few weeks, most users will be unlikely to install 4.3.0 anyway, until they either hear it's ok, or see it mature with a few bugfix releases. Just a thought. Zeev At 18:33 17/08/2002, Rasmus Lerdorf wrote: Regardless of what we call it, we need to light a fire under people to get a new release out. The fixes are piling up in CVS. Stig, could you give us a status report? Do you still have time to push this release? -R On Sat, 17 Aug 2002, Zeev Suraski wrote: Ok then, I retract my suggestion to release 4.2.3. Zeev At 17:59 17/08/2002, Dan Kalowsky wrote: I disagree that it should go out as is, very strongly at that too. Some fixes not in the 4.2 branches: - ODBC no longer crashes on Windows upon unloading - while not fully tested, ext/java now works for 1.4 JDK's - various memory leak fixes provied by Ilia (pack being one of them) - a few misc fixes for Win32 platforms - nsapi build fix which allows it to build and reported run again (although I still think we need to decide if we can kill this support) - numerous domxml bug fixes have been added as well. - QTDOM fix to allow it to compile again and run again This is one yet to be made, but: - a potential fix to have 'make install' work on AIX machines again finally. These are just bug fixes. I don't want to see new functionality added to PHP for a potential 4.2.3, but I do want to see a LOT of these bugs squished. There is a fix, why go and release another version of PHP with known and non-fixed bugs in it? It still doesn't seem to compile and work on 64-bit arch's. But yet again, there are numerous reasons why we should move to release PHP 4.3. The biggest of which in my book is, it supports OSX! While possibly a minor issue to many of the users on this list, it's becoming a more significant issue, especially with Jaguar/10.2 being released in a few days. There have been numerous fixes to all the code bases in an effort to get support for OSX implemented into them (ext/java still being a bastard). On Sat, 17 Aug 2002, Zeev Suraski wrote: I think it makes good sense to release 4.2.3 as-is (after a short QA cycle, that will ensure we didn't introduce any new bugs). If 4.2.3 becomes a larger project, with more pre-requisites, I don't see it happening (if it will not be simple, it will simply not be).
[PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] 4.2.3
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 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] 4.2.3
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. 64-bit support has worked for years in PHP -- it is not new or a 'major thing'. Assuming these fixes just relate to some type issues, they can be savely committed to the 4.2 branch. I think 4.2.3 makes perfect sense as long as it gets started immediately, immediately being sometime within the next few days. Is there some event I'm not aware of that a few days matter to you? If not, I don't see any problem with merging all important fixes and commencing the QA process afterwards. - Sascha -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] 4.2.3
At 22:58 17/08/2002, Sascha Schumann wrote: 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. 64-bit support has worked for years in PHP This is what I thought too. I'm not sure what these fixes are, but it's quite possible that it didn't really work too well in 64-bit systems for years as you and I thought, in which case it's quite alright to wait. I'm not saying we *should* wait, I'm saying it's a possibility, depending on how far-reaching they are. Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] 4.2.3
On Sat, 17 Aug 2002, Zeev Suraski wrote: At 22:58 17/08/2002, Sascha Schumann wrote: 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. 64-bit support has worked for years in PHP This is what I thought too. I'm not sure what these fixes are, but it's quite possible that it didn't really work too well in 64-bit systems for years as you and I thought, in which case it's quite alright to wait. I'm not saying we *should* wait, I'm saying it's a possibility, depending on how far-reaching they are. Well, my primary workstation was a 64-bit Alpha system for about a year in 1999 or 2000. After fixing a few issues, PHP worked without a hitch -- while it is easy for me to imagine that new code violated some portability concerns, I don't think that PHP or the Zend engine have been actually destabilized to the effect of being unusable. :-) I've had at a look at the bug reports Sebastian Nohn pointed out. None of these are major issues. Annoying, but nothing which would qualify PHP as being buggy as hell. Still, having these fixes in 4.2.3 would be a definitive advantage. - Sascha -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] 4.2.3
I agree on every point. It's not buggy as hell but it's quite annoying and it puts the developer in a situation where many workarounds have to be made when these bugs are fixed in CVS... -Original Message- From: Sascha Schumann [mailto:[EMAIL PROTECTED]] Sent: Sat 17/08/2002 5:18 PM To: Zeev Suraski Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [PHP-QA] Re: [PHP-DEV] 4.2.3 On Sat, 17 Aug 2002, Zeev Suraski wrote: At 22:58 17/08/2002, Sascha Schumann wrote: 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. 64-bit support has worked for years in PHP This is what I thought too. I'm not sure what these fixes are, but it's quite possible that it didn't really work too well in 64-bit systems for years as you and I thought, in which case it's quite alright to wait. I'm not saying we *should* wait, I'm saying it's a possibility, depending on how far-reaching they are. Well, my primary workstation was a 64-bit Alpha system for about a year in 1999 or 2000. After fixing a few issues, PHP worked without a hitch -- while it is easy for me to imagine that new code violated some portability concerns, I don't think that PHP or the Zend engine have been actually destabilized to the effect of being unusable. :-) I've had at a look at the bug reports Sebastian Nohn pointed out. None of these are major issues. Annoying, but nothing which would qualify PHP as being buggy as hell. Still, having these fixes in 4.2.3 would be a definitive advantage. - Sascha -- PHP Quality Assurance Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] 4.2.3
At 00:18 18/08/2002, Sascha Schumann wrote: I've had at a look at the bug reports Sebastian Nohn pointed out. None of these are major issues. Annoying, but nothing which would qualify PHP as being buggy as hell. Still, having these fixes in 4.2.3 would be a definitive advantage. Ok, thanks for taking the time to look into it. Sounds like they should be MFH'd. Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] 4.2.3
-Original Message- From: Zeev Suraski [mailto:[EMAIL PROTECTED]] Sent: Saturday, August 17, 2002 10:06 PM To: Sascha Schumann Cc: Xavier Spriet; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [PHP-QA] Re: [PHP-DEV] 4.2.3 At 22:58 17/08/2002, Sascha Schumann wrote: 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. 64-bit support has worked for years in PHP This is what I thought too. I'm not sure what these fixes are, but it's quite possible that it didn't really work too well in 64-bit systems for years as you and I thought, in which case it's quite alright to wait. I'm not saying we *should* wait, I'm saying it's a possibility, depending on how far-reaching they are. http://bugs.php.net/bug.php?id=18228 did'nt work with 4.2.0. With 4.0.4pl1 everything was fine, did'nt check, when it broke, but if it's needed I can do so. http://bugs.php.net/bug.php?id=18623 did'nt work with 4.2.0. The patch is simple. http://bugs.php.net/bug.php?id=17449 did'nt work with 4.2.0, until 4.1.2, everything was fine. These are the most disturbing bugs in my eyes and for my work. Regards, Sebastian Nohn -- +49 170 471 8105 - [EMAIL PROTECTED] - http://www.nohn.net/ PGP Key Available - Did I help you? Consider a gift: http://www.amazon.de/exec/obidos/wishlist/3HYH6NR8ZI0WI/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] 4.2.3
-Original Message- From: Sascha Schumann [mailto:[EMAIL PROTECTED]] Sent: Saturday, August 17, 2002 11:19 PM To: Zeev Suraski Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] 4.2.3 Well, my primary workstation was a 64-bit Alpha system for about a year in 1999 or 2000. After fixing a few issues, PHP worked without a hitch -- while it is easy for me to imagine that new code violated some portability concerns, I don't think that PHP or the Zend engine have been actually destabilized to the effect of being unusable. :-) I've had at a look at the bug reports Sebastian Nohn pointed out. None of these are major issues. Annoying, but nothing which would qualify PHP as being buggy as hell. Still, having these fixes in 4.2.3 would be a definitive advantage. At least all functions of ext/standard should work as expected on all platforms. Regards, Sebastian Nohn -- +49 170 471 8105 - [EMAIL PROTECTED] - http://www.nohn.net/ PGP Key Available - Did I help you? Consider a gift: http://www.amazon.de/exec/obidos/wishlist/3HYH6NR8ZI0WI/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] 4.2.3
On Sat, 17 Aug 2002, Sascha Schumann wrote: I think 4.2.3 makes perfect sense as long as it gets started immediately, immediately being sometime within the next few days. Is there some event I'm not aware of that a few days matter to you? If not, I don't see any problem with merging all important fixes and commencing the QA process afterwards. I agree with that. Derick --- Did I help you? http://www.derickrethans.nl/link.php?url=giftlist Frequent ranting: http://www.derickrethans.nl/ --- PHP: Scripting the Web - [EMAIL PROTECTED] All your branches are belong to me! SRM: Script Running Machine - www.vl-srm.net --- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] 4.2.3
At 18:19 17-8-2002, Liz wrote: there should be 'fixed in the next bug-fix release' or 'fixed in the next semi-major release'. How about Will be fixed in version major.minor.buildrelease ?? ie tell them which version it will be fixed in, no confusion at all then Actually - It's wiser to explain: Fixed in HEAD - This bug has been fixed in CVS. Unfortunately, it cannot be committed to the STABLE branch, because of too many incompatibilities, which would potentially introduce new bugs. Fixed in HEAD/STABLE - This bug has been fixed in CVS, for both the CURRENT and STABLE branch. Fixed in STABLE - This bug has been fixed in CVS, for the STABLE branch. The problem does not apply to HEAD, as the implementation has changed or was already fixed. Met vriendelijke groeten / With kind regards, Webmaster IDG.nl Melvyn Sopacua -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
