| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Dave Page <dpage(at)pgadmin(dot)org>, 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> |
| Subject: | Re: PG 15 downloads |
| Date: | 2022-10-17 15:51:12 |
| Message-ID: | bdeb8a86-6caf-fe28-3836-461c10008d09@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On 10/17/22 11:48 AM, Andres Freund wrote:
> Hi,
>
> On 2022-10-17 10:32:30 +0200, Daniel Gustafsson wrote:
>>> 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?
>
> Could these tables be updated well ahead of time and PG $next just be hidden
> until the release based on the version number?
Yes, but the suggested JSON file approach accomplishes something
similar, and is a pattern we already have for some of the other package
repos.
Thanks,
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2022-10-17 15:55:33 | Re: PG 15 downloads |
| Previous Message | Andres Freund | 2022-10-17 15:48:28 | Re: PG 15 downloads |