Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 3CA249FB791; Tue, 10 Apr 2007 11:58:29 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 28798-02; Tue, 10 Apr 2007 11:58:19 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from developer.pgadmin.org (developer.pgadmin.org [63.246.23.140]) by postgresql.org (Postfix) with ESMTP id 2B3B39FB613; Tue, 10 Apr 2007 11:58:18 -0300 (ADT) Received: from [172.24.32.110] ([62.232.55.118]) (authenticated bits=0) by developer.pgadmin.org (8.13.8/8.13.8) with ESMTP id l3AEtmwv000792 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Apr 2007 14:55:49 GMT Message-ID: <461BA604.7070600@postgresql.org> Date: Tue, 10 Apr 2007 15:58:12 +0100 From: Dave Page User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) MIME-Version: 1.0 To: Dave Page , Magnus Hagander , Andrew Hammond , CAJ CAJ , pgsql-general@postgresql.org, pgsql-www Subject: Re: Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version References: <20070410081558.GB24976@svr2.hagander.net> <461B5064.8010004@postgresql.org> <20070410101852.GC24976@svr2.hagander.net> <461B6F10.3040800@postgresql.org> <20070410111509.GF24976@svr2.hagander.net> <461B768A.8070402@postgresql.org> <20070410122708.GB25739@svr2.hagander.net> <461B8D60.6080004@postgresql.org> <20070410135708.GA7786@alvh.no-ip.org> <461B9B4F.4070208@postgresql.org> <20070410142535.GB7786@alvh.no-ip.org> In-Reply-To: <20070410142535.GB7786@alvh.no-ip.org> X-Enigmail-Version: 0.94.1.2 OpenPGP: url=http://www.pgadmin.org/pgp/davepage.pgp Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/33 X-Sequence-Number: 11783 Alvaro Herrera wrote: > It makes sense to store things separately when they have a semantic > difference. What we call "major" is the first two digits and dot. We > call "minor" to the third digit, and that's all. We don't have > "revisions". This is how it has ever been and we even document it as > such. Offering the first two digits separately would be a mistake > because it causes confusion over what's significant -- the first digit > by itself is not significant. Yes, and for the most part it's true (certainly as far as the purpose of that documentation is concerned), however it all falls apart next time we have the 'are there enough new features in this release to bump the first digit' discussion which, along with the fact that we have bumped it twice now, is proof in itself that we do give it some meaning. Anyhoo, I've said my piece now - I'll await the inevitable replies telling me I'm a donut and then move on :-) Regards, Dave