On 10/18/22 07:43, Dave Page wrote:
>
>
> On Tue, 18 Oct 2022 at 15:15, Adrian Klaver <adrian.klaver@aklaver.com
> <mailto:adrian.klaver@aklaver.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.
Except I have not interest in doing anything with pgAdmin, whereas the
EDB installer maintainers do need to know what is going on with a site
they are linked to. By your own admission you are not really involved
with anymore, so it would seem having at least one of the folks that is
involved monitoring the list would be a good idea.
> There was no "getting around to prioritizing supporting Postgres". The
I went back and reread the thread and realized I was mistaken, the
installers where there. The Postgres site had not been updated. For that
I apologize.
> 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 <https://pgsnake.blogspot.com>
> Twitter: @pgsnake
>
> EDB: https://www.enterprisedb.com <https://www.enterprisedb.com>
>
--
Adrian Klaver
adrian.klaver@aklaver.com