| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Daniel Gustafsson <daniel(at)yesql(dot)se>, 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-18 14:43:54 |
| Message-ID: | CA+OCxowm5gVsUKd6s3WnRP=TSP+35OrHaokKMyrDofrzNWVD6A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Tue, 18 Oct 2022 at 15:15, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 10/18/22 01:15, Dave Page wrote:
>
> >
> > Regardless of who is managing them, surely the person in charge of
> > it should be on this list to be able to answer questions etc.
> >
> >
> > You're suggesting the person in charge of the EDB website should be on
> > this mailing list on the off-chance we decide to have a discussion about
> > adding an API or file to the EDB site? That seems excessive, given this
> > or anything like it has happened once in 15+ years.
>
> No, so they can be part of the conversation period so we don't have to
> wait for some intra-company communication/process to take place.
>
Well on that basis, perhaps you could subscribe to the pgadmin-hackers
mailing list just in case we decide we need something from you in a few
years?
Yes, that's a facetious suggestion, but I don't think it's far from what's
being asked.
>
> >
> > And I'm sure they have the technical skills to publish a json file
> > even without your oversight :)
> >
> >
> > Of course they do. The question is one of prioritising the work, which
> > unless it's an issue with the download pages not working etc. I have
> > very little sway over.
>
> Th solution would be to move these downloads to the PGDG infrastructure
> and not have to wait on a company that makes it's money off Postgres
> getting around to prioritizing supporting Postgres.
>
There was no "getting around to prioritizing supporting Postgres". The
installers were published and available on time, and the people doing that
work updated everything they've ever been asked to. Moving downloads to
PGDG infrastructure would not have avoided the problem being discussed at
all; the pages that needed updating would still need to be updated by
someone, through some mechanism that doesn't involve having commit rights
on the website repo and doesn't currently exist.
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2022-10-18 15:17:58 | Re: PG 15 downloads |
| Previous Message | Adrian Klaver | 2022-10-18 14:15:48 | Re: PG 15 downloads |