| From: | Dave Page <dpage(at)postgresql(dot)org> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Andrew Hammond <andrew(dot)george(dot)hammond(at)gmail(dot)com>, CAJ CAJ <pguser(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, pgsql-www <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version |
| Date: | 2007-04-10 08:52:52 |
| Message-ID: | 461B5064.8010004@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-www |
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 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.
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Listmail | 2007-04-10 08:57:43 | Bad plan using join on VALUES |
| Previous Message | Magnus Hagander | 2007-04-10 08:15:58 | Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Listmail | 2007-04-10 09:09:50 | Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version |
| Previous Message | Magnus Hagander | 2007-04-10 08:15:58 | Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version |