Return-Path: Delivered-To: apmail-perl-dev-archive@www.apache.org Received: (qmail 40105 invoked from network); 1 Dec 2004 16:58:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 1 Dec 2004 16:58:44 -0000 Received: (qmail 92198 invoked by uid 500); 1 Dec 2004 16:57:01 -0000 Delivered-To: apmail-perl-dev-archive@perl.apache.org Received: (qmail 92157 invoked by uid 500); 1 Dec 2004 16:57:01 -0000 Mailing-List: contact dev-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@perl.apache.org Received: (qmail 92111 invoked by uid 99); 1 Dec 2004 16:57:01 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of gcamd-dev@m.gmane.org designates 80.91.229.2 as permitted sender) Received: from main.gmane.org (HELO main.gmane.org) (80.91.229.2) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 01 Dec 2004 08:56:58 -0800 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CZXmh-000201-00 for ; Wed, 01 Dec 2004 17:56:55 +0100 Received: from adsl-3-9-118.mia.bellsouth.net ([65.3.9.118]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 01 Dec 2004 17:56:55 +0100 Received: from joe+gmane by adsl-3-9-118.mia.bellsouth.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 01 Dec 2004 17:56:55 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: dev@perl.apache.org To: dev@perl.apache.org From: Joe Schaefer Subject: Re: t/modules/proxy.t fails with httpd-2.1 Date: Wed, 01 Dec 2004 11:56:48 -0500 Lines: 28 Message-ID: <87brdeufcf.fsf@gemini.sunstarsys.com> References: <41A7A22D.5010607@stason.org> <20041201083849.GA27489@redhat.com> <41ADD7F6.5060709@stason.org> <20041201145711.GA30908@redhat.com> <41ADE017.1010904@stason.org> <87fz2quiqt.fsf@gemini.sunstarsys.com> <20041201163950.GA6546@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: adsl-3-9-118.mia.bellsouth.net Mail-Copies-To: never User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.3 (gnu/linux) Cancel-Lock: sha1:m9gKcCL63l0TWqsNVnECmzn+USE= Sender: news X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Joe Orton writes: > On Wed, Dec 01, 2004 at 10:43:22AM -0500, Joe Schaefer wrote: >> Stas Bekman writes: >> >> > One needs to go through a deprecation cycle before any backwards >> > compatibility in the same generation of the project can be dropped. >> >> Heh, a search for "deprecation cycle" on marc's dev@httpd archives >> comes up empty. > > I'm not sure really what you expect. That no API changes can be made > during 2.1 development unless they were predicted ahead of time by N > years and marked with a red dot? I think what Stas was expecting something similar to the perl5 versioning rules: misfeatures that occur minor version $X (X even) cannot be removed until $X+4, and must first be marked deprecated in $X+2. I'm just pointing out that dev@httpd has never discussed doing something like that, so Stas is mistaken if he's expecting dev@httpd to follow such rules. Not that I think it'd be a bad thing though, because it would provide specific guidance about when to bump the minor number. But I won't be lobbying for this on dev@httpd any time soon :-) -- Joe Schaefer --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org For additional commands, e-mail: dev-help@perl.apache.org