Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 12005 invoked from network); 8 May 2006 11:37:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 May 2006 11:37:02 -0000 Received: (qmail 4817 invoked by uid 500); 8 May 2006 11:36:53 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 4768 invoked by uid 500); 8 May 2006 11:36:53 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 4756 invoked by uid 99); 8 May 2006 11:36:52 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 May 2006 04:36:52 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [80.229.52.226] (HELO asgard.webthing.com) (80.229.52.226) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 May 2006 04:36:52 -0700 Received: from asgard (asgard [192.168.10.2]) by asgard.webthing.com (Postfix) with ESMTP id B964F64556 for ; Mon, 8 May 2006 12:36:29 +0100 (BST) From: Nick Kew Organization: WebThing Ltd To: dev@httpd.apache.org Subject: Dealing with Regressions Date: Mon, 8 May 2006 12:36:26 +0100 User-Agent: KMail/1.8.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605081236.28737.nick@webthing.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N OK, we all know we get some embarrassing regressions in our new releases. PR#39490 in 1.3.35. Or 2.0.55 being effectively unusable in a proxy due to PR#37145. Look at the number of duplicates of 37145 - that's a lot of people with the confidence to report it, and who didn't find it 'cos it's marked as fixed (despite no fixed version being released until last week). We should do better than leaving the users to rediscover and deal with regressions themselves, once we know there's a problem. Can I suggest an Errata page, to list *all* known regressions in current/recent versions, linked from the main page alongside "Download/New Features/Changelog"? -- Nick Kew