Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 80840 invoked from network); 22 Nov 2004 17:38:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 22 Nov 2004 17:38:19 -0000 Received: (qmail 76694 invoked by uid 500); 22 Nov 2004 17:38:04 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 76589 invoked by uid 500); 22 Nov 2004 17:38:02 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 76546 invoked by uid 99); 22 Nov 2004 17:38:02 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Errors-To: Message-Id: <6.2.0.14.2.20041122113053.11eb4fe0@pop3.rowe-clan.net> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Mon, 22 Nov 2004 11:34:35 -0600 To: Cliff Woolley From: "William A. Rowe, Jr." Subject: Re: 2.2 roadmap with respect to APR was Re: [NOTICE] CVS to SVN migration complete Cc: dev@httpd.apache.org, dev@apr.apache.org In-Reply-To: References: <1100891614.3516.111.camel@grunt.striker.nl> <20041120014943.1507f466@parker> <20BD7D09FE72AAE1D4601067@st-augustin.ics.uci.edu> <6.1.2.0.2.20041119195907.06649ec0@pop3.rowe-clan.net> <251409A8D7DA50F198EFA39D@[10.0.1.16]> <6.2.0.14.2.20041120101355.0410c4e8@pop3.rowe-clan.net> <41A20F10.6040104@wstoddard.com> <6.2.0.14.2.20041122101558.0451d7a0@pop3.rowe-clan.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N At 11:08 AM 11/22/2004, Cliff Woolley wrote: >On Mon, 22 Nov 2004, William A. Rowe, Jr. wrote: > >> Yes - I understand that this means 1.x will never be used by >> httpd. Version numbers are cheap. The APR project should >> become used to this, if they are active, and httpd moves at >> it's normal pace, it would be easy to go through APR 2.x, 3.x, >> and land somewhere in version 4.x by the time httpd 2.4 or 3.0 >> walks out the door. > >Do you understand how ridiculous that sounds? How so? Let's imagine the release -after- 2.2 takes another 12-18 months. Perhaps the event mpm gets plugged in, and it takes three months, alone, just to find all the gotchas of thread-jumping. In the meantime, apr is adopted by other projects. These coders offer up some solid functionality for their own applications, and the apr team agrees. Yes, I realize most of the time new functionality can be a minor bump of apr. Yes, I realize apr has not been all that active in the past 12 months. All I'm arguing is that apr shouldn't be addicted to some 1:1 correspondence of httpd and apr bumps. Bill