> +1 on on that, but I do think that when a bug is set to bogus the reason > why it is bogus should always be noted.
While on that topic, I had a bug recently set to bogus because it was reported against 4.2.3 while 4.3.0 was out. More than once in the bug reporting info there is a comment something like: > Every time a new version of PHP is released, hundreds of bugs are fixed. > If you're using a version of PHP that is more than two revisions older > than the latest version, you should upgrade to the latest version to make > sure the bug you are experiencing still exists. If people are going to set to bogus reports against the previous stable release, then this should really be noted somewhere. Especially since the new version is less than a month old, and had quite a few changes in, I was slightly ruffled at the somewhat dismissive resolution. (As it happens, this particular problem is still present in 4.3.0, but it took us a while to free up a machine to build and test this on.) Don't take this the wrong way - in general I'd support rejecting bugs against older versions, but the documentation should be clear about it if that is the case, and the status change email probably shouldn't appear so terse. The somewhat lengthy form response: > Thank you for taking the time to report a problem with PHP. > Unfortunately you are not using a current version of PHP -- > the problem might already be fixed. Please download a new > PHP version from http://www.php.net/downloads.php > > If you are able to reproduce the bug with one of the latest > versions of PHP, please change the PHP version on this bug report > to the version you tested and change the status back to "Open". > Again, thank you for your continued support of PHP. was not the best mood enhancer when I came in the following morning :-) Cheers, James -- James Aylett Chief Technical Architect, Tangozebra t 020 7535 9850 f 020 7535 9900 w http://tangozebra.com/ This e-mail message, including any attachments, is intended only for the person or entity to which it is addressed, and may contain confidential information. If you are not the intended recipient, any review, retransmission, disclosure, copying, modification or other use of this e-mail message or attachments is strictly forbidden. Copyright Tangozebra 2003. All Rights Reserved. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.370 / Virus Database: 205 - Release Date: 05/06/2002 ________________________________________________________________________ This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________ -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
