Re: [PHP4BETA] virtual()

At 11:06 PM 7/19/99 +0000, Jim Winstead wrote:

First, a lot of the problems are in fact likely to go away or change significantly with the new tree. Then close the bugs that are fixed by the new tree. Just abandoning the old database means that stuff will get lost.

It doesn't get lost. It's just not a PHP 4.0 related bug.

Second, it's bad to start a new version with several open bug reports. I don't get this argument. It's bad to pretend that bugs that were reported don't exist any more just because a lot of code has changed. There's also a lot of code that hasn't changed.

You do get this argument, even if you say you don't. There are hundreds of bugs or so-called bugs in the bugs database that haven't, aren't and won't be inspected by anybody for many various reasons. Starting off with this heritage is bad. Saying a lot of the bugs may have been fixed or at the very least altered isn't pretence in any way. The entire language engine changed. The entire web server interface has changed. Hash tables changed. The build process changed. God knows what else changed. So far, it pretty much means that any compile/build related issue and any language related issue was at the very least altered under PHP 4.0. New bugs were probably introduced, old ones fixed.

Third, we won't be able to handle the bugs if they're in a combined database. It's just not going to work. I have modified the stuff under version4 to only display bugs reported against bugs that are reported against a PHP version that starts with a 4. (This includes the bugstats page.) I am migrating the two bugs reported against php4 already into the combined database.

Uhmm, before you do conduct such a one-sided action, please wait to see if you actually convinced the other party, which in this case, you definitely have not. Maintaining the same bugs database for PHP 4.0 and PHP 3.0, considering they're SO different from each other, makes no technical sense either. Many bugs reported with PHP 4.0 will make absolutely no sense with PHP 3.0 and vice versa. Once PHP 4.0 goes out of beta, we may argue on whether to import all the PHP 3.0 bugs (or selectively import them), but right now, there should be a clear distinction between bugs that are old PHP 3.0 bugs and ones that actually have been discovered recently, most probably due to PHP 4.0 related changes. Please undo any changes you made to merge the two databases. Zeev