| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-release(at)postgresql(dot)org, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org>, Christoph Berg <cb(at)df7cb(dot)de>, Sandeep Thakkar <sandeep(dot)thakkar(at)enterprisedb(dot)com>, Jonathan Katz <jkatz(at)postgresql(dot)org> |
| Subject: | Re: PG 15 downloads |
| Date: | 2022-10-17 08:32:30 |
| Message-ID: | 4E16E1F8-5DA6-497A-B568-834986496A20@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
> On 17 Oct 2022, at 10:29, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> A couple of possible solutions that spring to mind:
>
> 1) Jonathan (or whoever is handling the release process) could ensure those pages are updated as part of the release push, but that would require confirmation from Sandeep or someone on the EDB team that the packages have been published and everything looks good.
>
> 2) We could database-ise the data in those tables, and then Sandeep could update that through the Django admin interface at the appropriate time. He does have access to a limited part of the admin interface already.
3) EDB publish an API endpoint with the available releases that pg.org consumes
and use to create the page?
--
Daniel Gustafsson https://vmware.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2022-10-17 08:32:55 | Re: PG 15 downloads |
| Previous Message | Dave Page | 2022-10-17 08:29:44 | Re: PG 15 downloads |