Re: programmatic way to fetch latest release for a given major.minor version
От | Magnus Hagander |
---|---|
Тема | Re: programmatic way to fetch latest release for a given major.minor version |
Дата | |
Msg-id | 20070410101852.GC24976@svr2.hagander.net обсуждение исходный текст |
Ответ на | Re: programmatic way to fetch latest release for a given major.minor version (Dave Page <dpage@postgresql.org>) |
Ответы |
Re: programmatic way to fetch latest release for a given
major.minor version
Re: programmatic way to fetch latest release for a given major.minor version Re: [pgsql-www] programmatic way to fetch latest release for a given major.minor version |
Список | pgsql-general |
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. > But I can't help thinking that we should have some additional values for > release notes, download sub-URLs (to be appended to the mirror roots) etc. Yeah, thus the X in XML :-) But given that we might want to add things like this, having our own custom XML format certainly makes a bit more sense, it might be harder to try to trick it into RSS. //Magnus
В списке pgsql-general по дате отправления: