Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:56257 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 77966 invoked from network); 10 Nov 2011 22:01:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Nov 2011 22:01:28 -0000 Authentication-Results: pb1.pair.com smtp.mail=dirk@haun-online.de; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=dirk@haun-online.de; sender-id=pass Received-SPF: pass (pb1.pair.com: domain haun-online.de designates 80.67.31.39 as permitted sender) X-PHP-List-Original-Sender: dirk@haun-online.de X-Host-Fingerprint: 80.67.31.39 smtprelay01.ispgateway.de Linux 2.6 Received: from [80.67.31.39] ([80.67.31.39:51240] helo=smtprelay01.ispgateway.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 85/B1-00436-6B94CBE4 for ; Thu, 10 Nov 2011 17:01:27 -0500 Received: from [79.222.19.2] (helo=[192.168.2.100]) by smtprelay01.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1ROcgV-0000ep-7g for internals@lists.php.net; Thu, 10 Nov 2011 23:01:23 +0100 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Thu, 10 Nov 2011 23:01:21 +0100 Message-ID: To: PHP Internals Mime-Version: 1.0 (Apple Message framework v1251.1) X-Mailer: Apple Mail (2.1251.1) X-Df-Sender: d2VibWFzdGVyQGhhdW4tb25saW5lLmRl Subject: What's the correct way to report a regression? From: dirk@haun-online.de (Dirk Haun) I've notice, back in PHP 5.4.0 beta 2, that this test was failing: Bug #48555 (ImageFTBBox() differs from previous versions for texts with = new lines) [ext/gd/tests/bug48555.phpt] So I went to https://bugs.php.net/bug.php?id=3D48555 and left a comment. The same test still fails in 5.4.0RC1 and also for 5.3.9RC1. Now, I have no idea if this is really a critical or important issue, but = apparently a test exists for it and it fails now. So how should I go = about reporting it so that somebody looks into it and decides if it's = worth fixing? Since I'm not the original reporter of bug #48555, I can't edit it to = update the affected PHP version. Should I have opened a new bug report = instead? Would that have gotten someone's attention? bye, Dirk