Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 6269 invoked from network); 22 Dec 2009 12:01:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Dec 2009 12:01:11 -0000 Received: (qmail 47721 invoked by uid 500); 22 Dec 2009 11:58:21 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 47589 invoked by uid 500); 22 Dec 2009 11:58:04 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 47332 invoked by uid 99); 22 Dec 2009 11:57:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Dec 2009 11:57:13 +0000 X-ASF-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.220.228] (HELO mail-fx0-f228.google.com) (209.85.220.228) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Dec 2009 11:57:04 +0000 Received: by fxm28 with SMTP id 28so260373fxm.26 for ; Tue, 22 Dec 2009 03:56:43 -0800 (PST) Received: by 10.223.5.18 with SMTP id 18mr11498070fat.58.1261483002924; Tue, 22 Dec 2009 03:56:42 -0800 (PST) Received: from ?172.31.13.157? (cpe-90-157-168-234.dynamic.amis.net [90.157.168.234]) by mx.google.com with ESMTPS id k29sm9831495fkk.51.2009.12.22.03.56.41 (version=SSLv3 cipher=RC4-MD5); Tue, 22 Dec 2009 03:56:41 -0800 (PST) Message-ID: <4B308CD9.3070404@apache.org> Date: Tue, 22 Dec 2009 10:09:45 +0100 From: =?UTF-8?B?QnJhbmtvIMSMaWJlag==?= User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Bojan Smojver CC: "William A. Rowe Jr." , Guenter Knauf , APR Developer List Subject: Re: [discuss] Releasing pre-release APR References: <4B2FC35A.9030101@rowe-clan.net> <4B2FCE13.7070105@apache.org> <1261430039.1981.19.camel@shrek.rexursive.com> <4B2FF1BC.7000808@rowe-clan.net> <4B2FFCC8.7030503@apache.org> <4B2FFE60.3020505@rowe-clan.net> <1261436709.1981.25.camel@shrek.rexursive.com> In-Reply-To: <1261436709.1981.25.camel@shrek.rexursive.com> X-Enigmail-Version: 0.96.0 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAAXNSR0IArs4c6QAAADBQTFRF IhsbCy0qZjoVOVRoeFxSAIKBzXQiAKaibYiewnk7nn9z0qCTgL3i87Ep6Kx/+tHBsrE+zgAAAjZJ REFUOMvF0jFoE1EYB/CzjWlqIzaTjqVIBifRRWyG0t5iUqlLyFpCeXBgKg5yq6A4degUDJjoUDpc 1Qt4Ux94B11SOLB0KGS4discpbkORTCn9/m9d3fvLhXnvuHu3f+Xx/veyyfZfLSdZHzgicSfeyw4 JISwdz8FT6M8lM8Ceg385Dlhs+cC9sQCDn0B78QCogzwN+sxfHGOIXBbRGkNAM4cZymGtgNsDPgz cByxon3EEm1TLmvAlghoHOO3CZSa+IQ/vF6JV8tgKOMow78gRgL2/+EIvATOUtB3SSdMg4GXgrbn uk0uLiGdoCHKbX4E+t1FUTqn1AtIdPJebssDQ64YANSQyyaQNyUOFs0ijMsMFnOPTahPLXKYowtY 08MfCP7vR7hRnc5zmPK7CDYYbHcbC7tHuyFA94U/1LYZaJpu/sxACHMwvwZljTLY0TbNk4x+zuEt yC3MfCM6uSIvfwur0itFL4FA2Yal8BzLfnYV4EIGwEPAk7o5zIcnvzHMEjwJrrhAKK7on6IrsfRJ 7A53BhaK+CL7fj6+q/sPeOvcDTtoZTxpUYsFeIknrOXep3p3l7Ua+8sZ5FPQKyKwWi+DfROTU7ny C1/9UhpeY7K287WJCzbsNPQm2S6Yk4PSCNhWM2r3nD0K9liYb6yPgCRJhSzPrxUK0yUBVk1VX0lj s7MzGZyp0wImMK/e8rHbz2soL+O+2r1dxfGsAmBcx0lNjS/RUhlUC7gRn1wGMdQ7Vw1/AReW/RN3 xFWdAAAAAElFTkSuQmCC Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Bojan Smojver wrote: > On Mon, 2009-12-21 at 17:01 -0600, William A. Rowe Jr. wrote: > >> I don't think Bojan actually suggests we nuke it. >> > > No, no nuking at all. Just bit of skipping. > > >> The suggestion is that all n.even releases would be ABI stable. n.odd >> releases would be purely alpha- and beta-, with clear notices to the >> user of what they are obtaining, and that updating is likely to break >> their applications which are ./configure'd --with-apr-dev or some >> similar flag. >> > > Yep, something like that. In other words, if we have say 1.8 released > and we are working towards 1.10, then anything in 1.9 is completely > API/ABI unstable and relying on it being present in 1.10 is a gamble. Of > course, the relationship between 1.8 and 1.10 would still obey the same > rules as we now have for say 1.3 to 1.4. > -1 ... I've always found that approach a bit weird. There's no functional difference between 1.(oddx).y and 1.x.y-dev. It makes marginal sense to use the odd/even approach in projects like the Linux kernel where one expects to have dozens of intermediate development "releases" that do need to be differentiated. APR is quite a bit smaller and there's less flux, so changing the versioning scheme would cause unnecessary pain to users who're already well accustomed to it. Besides, I'm aware of quite a few projects who use the same versioning scheme and refer explicitly to our versioning.html file; if we change that without making a huge announcement, we intercourse those projects too. So I agree with RĂ¼diger that we can't actually change what APR version numbers mean before 2.0. If we /do/ happen to make a 1.x.y-dev pre-release that doesn't fly and we're concerned about breaking early adopters, and want to really differentiate between different releases, we're allowed to do a 1.x.y+1-dev without a 1.x.y release in between. This is going to be rare once the -dev and non-dev libraries become mutually unlinkable, so I really wouldn't worry about burning too many version numbers. They're free, after all. -- Brane