Received: from localhost (maia-3.hub.org [200.46.204.184])
	by postgresql.org (Postfix) with ESMTP id B2D309FA0B2;
	Tue, 10 Apr 2007 08:15:14 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024)
	with ESMTP id 45289-06; Tue, 10 Apr 2007 08:15:06 -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 svr2.hagander.net (svr2.hagander.net [88.198.128.226])
	by postgresql.org (Postfix) with ESMTP id CBB899F9F18;
	Tue, 10 Apr 2007 08:15:10 -0300 (ADT)
Received: by svr2.hagander.net (Postfix, from userid 1000)
	id 9E57FDCC7CC; Tue, 10 Apr 2007 13:15:09 +0200 (CEST)
Date: Tue, 10 Apr 2007 13:15:09 +0200
From: Magnus Hagander <magnus@hagander.net>
To: Dave Page <dpage@postgresql.org>
Cc: Andrew Hammond <andrew.george.hammond@gmail.com>,
	CAJ CAJ <pguser@gmail.com>, pgsql-general@postgresql.org,
	pgsql-www <pgsql-www@postgresql.org>
Subject: Re: [GENERAL] programmatic way to fetch latest release for a given
	major.minor version
Message-ID: <20070410111509.GF24976@svr2.hagander.net>
References: <1176155240.221125.319880@y80g2000hsf.googlegroups.com>
	<467669b30704091526v79ae044boe7217cc0777dce1f@mail.gmail.com>
	<5a0a9d6f0704091534i4e4af90co2dad0e9e0b60efee@mail.gmail.com>
	<461B3E6A.8080007@postgresql.org>
	<20070410081558.GB24976@svr2.hagander.net>
	<461B5064.8010004@postgresql.org>
	<20070410101852.GC24976@svr2.hagander.net>
	<461B6F10.3040800@postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <461B6F10.3040800@postgresql.org>
User-Agent: Mutt/1.5.11
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200704/22
X-Sequence-Number: 11772

On Tue, Apr 10, 2007 at 12:03:44PM +0100, Dave Page wrote:
> Magnus Hagander wrote:
> > On Tue, Apr 10, 2007 at 09:52:52AM +0100, Dave Page wrote:
> >> Magnus Hagander wrote:
> >>> 2) Create a new file with a specific schema. Something like:
> >>> <version>
> >>>  <version major="8.2" minor="8.2.3" />
> >>>  <version major="8.1" minor="8.1.8" />
> >>> </version>
> >>> This is the most lightweight solution.
> >> More like:
> >>
> >> <versions>
> >>   <version major="8" minor="2" revision="3" />
> >>   <version major="8" minor="1" revision="8" />
> >> </versions>
> > 
> > But that doesn't reflect our terminology. Per our own terminology, bioth
> > 8.1 and 8.2 are major versions. Not only is that what we've been saying for
> > years, we even documented it at
> > http://www.postgresql.org/support/versioning.
> 
> Yeah yeah, but terminology aside, having 2 or three digits in each
> attribute is just wrong!

Terminology aside, why? The unit is "8.1" not "8" and "1". It makes no
sense to say you're on version 8, in the given context, so why should the
XML data pretend there is?

//Magnus