Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 15809 invoked from network); 8 Apr 2004 17:58:41 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 8 Apr 2004 17:58:41 -0000 Received: (qmail 82281 invoked by uid 500); 8 Apr 2004 17:58:31 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 82242 invoked by uid 500); 8 Apr 2004 17:58:31 -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 82205 invoked from network); 8 Apr 2004 17:58:30 -0000 Message-ID: <1081449305.40759b592dde5@webmail.mydomain.com> Date: Thu, 8 Apr 2004 11:35:05 -0700 From: rbb@rkbloom.net To: dev@apr.apache.org MIME-Version: 1.0 User-Agent: Internet Messaging Program (IMP) 3.1 X-Originating-IP: 66.187.233.200 X-SA-Exim-Mail-From: rbb@rkbloom.net Subject: Re: Time for 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on calcium.dnsix.com X-Spam-Level: X-Spam-Status: No, hits=0.3 required=10.0 tests=NO_REAL_NAME autolearn=no version=2.63 X-Spam-Report: * 0.3 NO_REAL_NAME From: does not include a real name X-SA-Exim-Version: 3.1 (built Thu Oct 23 13:26:47 PDT 2003) X-SA-Exim-Scanned: Yes X-uvscan-result: clean (1BBdnL-0007pk-Je) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N < David meant to send this to the list, but hit the wrong button. His message is reproduced in it's entirity along with my response. > Quoting David Reid : > > The biggest problem with releasing HEAD as 1.0, is that the TIMESUP status > codes > > don't work everywhere, and locks aren't portable. Both of these changes > will > > break source compatibility and need to be fixed before 1.0. > > > OK, so let's start a list of stuff that's broken and *MUST* be fixed prior > to a 1.0. > > Also we should review STATUS. The TIMESUP stuff is relatively easy, hopefully I'll have time to do that work tonight. The locks not being portable is a big PITA to fix. I have a proposed solution that nobody has commented on yet. I am also very concerned that there are a lot more of these types of issues just waiting to bite us, because our test suite just doesn't do it's job currently. But, I am willing to release as long as everybody understands that we may be forced to explode our API to fix the problems with APIs that just don't work cross-platform. Ryan