Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hQUwD-0000iH-Cb for pgsql-www@arkaria.postgresql.org; Tue, 14 May 2019 10:45:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hQUwA-0006lg-VI for pgsql-www@arkaria.postgresql.org; Tue, 14 May 2019 10:45:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hQUwA-0006jJ-A3 for pgsql-www@lists.postgresql.org; Tue, 14 May 2019 10:45:34 +0000 Received: from mail-io1-xd44.google.com ([2607:f8b0:4864:20::d44]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hQUw2-0001WN-95 for pgsql-www@lists.postgresql.org; Tue, 14 May 2019 10:45:33 +0000 Received: by mail-io1-xd44.google.com with SMTP id a17so12624035iot.8 for ; Tue, 14 May 2019 03:45:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rbArV+6Er/JuMNupOOz8QGm4y6ObBLLaKWF52vMswP0=; b=eZi8Nx28zVmo/wTDMKUNOaTGtx4Btr9BhBIxgRjgSf9deIdwPYzaCtKvn0j5StKeAr +d3cpeQyRPbctlgm/EUjxrTqmaF1Owwwuw39frSr241BKzBbE6j5KWcUtycO2V9xj8Qk 2eH0UXslbE42yHr6n3n4n9XzR74XTcIoyNXUfGxDdD6Uq/3qwwPVercFDNZZVTFYaLC/ 7HGRzTLF6xMkQfMTDuMeEAG7HB3+LOdJRyrQ+T33JdnSME8N8oQkFlvel8mKqoFsX+q9 R9ezUA49uPgg1Z/rp5XZxOZk8YYPtPkvDPsMqr0/gygkuNc0kvNeDDrkHCJzn7oX98gv xtHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rbArV+6Er/JuMNupOOz8QGm4y6ObBLLaKWF52vMswP0=; b=Xei6Yw9r+zkAP882w3jhHW3ke+H+owXkJfwPcBk4UnFbUoO8LAYDvcJoCt+nShdcOA rTFDreeaY8jVAG40WAIsN6QYZfmlRsI1Nhp2qi+n7Ut4XSjljA4Ik9AnuI/DA7sHs30v 7lrofjQLIu0RnMXysSzmkR3D5h7eick8iMHAMOdoMIs5ME4J8ML1ewVG220kZ63Ax/uH 7DI1D7blzVfb5/CzMgLy+1ECkTsGlVcyY41CIaeTLyXc0+wrqg6dCPvlA0o4WBTPRjQO R6vqelA+fRVjSLj++JhFsuFx8OyeN4GcpNH2JGMSP8f/ww8NpA4SXcdNPDYTD//4pNso knUg== X-Gm-Message-State: APjAAAXIBXp6V2RofId8wgONuQDNTOmdYHQYLa/ri5fADPjJ96V6c9/+ Kui8V4On/j+gsq6g8KTnjhnlFVuYHEVOhBBqjvPvQzU4Ljc= X-Google-Smtp-Source: APXvYqy5ouLGoSjoDkC4E0WdxV36x3ct9oIqfk5/Z6hMkq7vIZttllaa3bt+Cvao30xwYOUSc/IgoVKTheg6kwyFdVo= X-Received: by 2002:a6b:511a:: with SMTP id f26mr19940339iob.56.1557830723891; Tue, 14 May 2019 03:45:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dave Page Date: Tue, 14 May 2019 11:45:12 +0100 Message-ID: Subject: Re: Cleaning up the Download options To: Oleg Bartunov Cc: PostgreSQL WWW Content-Type: multipart/alternative; boundary="000000000000eb179d0588d6ba9e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000eb179d0588d6ba9e Content-Type: text/plain; charset="UTF-8" On Sun, May 12, 2019 at 3:33 PM Oleg Bartunov wrote: > On Wed, May 8, 2019 at 6:14 PM Dave Page wrote: > > > > I've just reviewed all the download options on the website. A number are > out of date or have other issues, so I think we need to have a cleanup: > > > > Primary downloads: > > > > - postgresql.org packages are up to date. > > - EDB installers are up to date. > > - BigSQL installers are up to date. > > - postgres.app is up to date. > > - Fink is a release behind on 9.4 through 10, and doesn't carry 11 at > all as far as I can tell. > > - MacPorts is up to date. > > - The Homebrew link seems to go to a download site which after many > clicks gives me the Windows installer from EDB(!). I've fixed that now. The > packages appear to be a release behind on all supported branches. > > > > Thoughts on whether we should make any changes to the Fink and Brew > distributions? We used to require that the primary downloads be maintained > on our schedule, so by rights they should be removed. > > > > Secondary (third party) downloads: > > > > - LiveCD - this hasn't been updated since 9.6 in December 2016. It > should be removed. > > > > - 2UDA - This hasn't been updated since May 2018, and is currently > carrying 11beta1, 10.4, 9.6.9 and 9.5.13. I think this should be removed. > > > > - TurnKey - Deploying this requires signing up to their service. I > eventually tracked down the manifest file for their images and found they > ship 9.4.6. This should be removed. > > > > - BitNami images are up to date. > > > > Comments etc? I'm out from EOD until Tuesday, but will review any > comments somewhen after then, and make changes as appropriate (including > following my own suggestions if noone disagrees with them :-p ). > > We submitted download page for windows packages > https://postgrespro.com/windows Yes, but adding them is way outside the scope of what I'm proposing here. There are issues that would require discussion (on a different thread), e.g. - Your packages include patches to PostgreSQL that are not in the community repo. - Your packages include changes to LGPL licenced third party components that may put unexpected and onerous requirements on end users or users that embed in other products. - What happens if a user gets confused and tries to upgrade an existing installation from the BigSQL or EDB installers with one of yours (or the other way round)? Will it break their system? - You're packaging a version of pgAdmin that hasn't been supported in years and will likely fail in numerous ways with modern PostgreSQL versions. As the person most likely to get bug reports about that (which will be ignored), I certainly don't want us to be distributing pgAdmin 3 with modern builds of PostgreSQL. There may be more things, but those are issues I spotted in a few minutes on the Github repo, that I think would need discussion before we could consider adding more installers (and right now, I know a number of people think we should be doing the opposite, and simplifying the choices given to users). -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --000000000000eb179d0588d6ba9e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sun, May 12, 2019 at 3:33 PM Oleg = Bartunov <obartunov@postgres= pro.ru> wrote:
On Wed, May 8, 2019 at 6:14 PM Dave Page <dpage@pgadmin.org> wrote:
>
> I've just reviewed all the download options on the website. A numb= er are out of date or have other issues, so I think we need to have a clean= up:
>
> Primary downloads:
>
> - postgresql.org packages are up to date.
> - EDB installers are up to date.
> - BigSQL installers are up to date.
> - postgres.app is up to date.
> - Fink is a release behind on 9.4 through 10, and doesn't carry 11= at all as far as I can tell.
> - MacPorts is up to date.
> - The Homebrew link seems to go to a download site which after many cl= icks gives me the Windows installer from EDB(!). I've fixed that now. T= he packages appear to be a release behind on all supported branches.
>
> Thoughts on whether we should make any changes to the Fink and Brew di= stributions? We used to require that the primary downloads be maintained on= our schedule, so by rights they should be removed.
>
> Secondary (third party) downloads:
>
> - LiveCD - this hasn't been updated since 9.6 in December 2016. It= should be removed.
>
> - 2UDA - This hasn't been updated since May 2018, and is currently= carrying 11beta1, 10.4, 9.6.9 and 9.5.13. I think this should be removed.<= br> >
> - TurnKey - Deploying this requires signing up to their service. I eve= ntually tracked down the manifest file for their images and found they ship= 9.4.6. This should be removed.
>
> - BitNami images are up to date.
>
> Comments etc? I'm out from EOD until Tuesday, but will review any = comments somewhen after then, and make changes as appropriate (including fo= llowing my own suggestions if noone disagrees with them :-p ).

We submitted download page for windows packages
https://postgrespro.com/windows

Y= es, but adding them is way outside the scope of what I'm proposing here= . There are issues that would require discussion (on a different thread), e= .g.

- Your packages include patches to PostgreSQL = that are not in the community repo.
- Your packages include chang= es to LGPL licenced third party components that may put unexpected and oner= ous requirements on end users or users that embed in other products.
<= div>- What happens if a user gets confused and tries to upgrade an existing= installation from the BigSQL or EDB installers with one of yours (or the o= ther way round)? Will it break their system?
- You're packagi= ng a version of pgAdmin that hasn't been supported in years and will li= kely fail in numerous ways with modern PostgreSQL versions. As the person m= ost likely to get bug reports about that (which will be ignored), I certain= ly don't want us to be distributing pgAdmin 3 with modern builds of Pos= tgreSQL.

There may be more things, but those are i= ssues I spotted in a few minutes on the Github repo, that I think would nee= d discussion before we could consider adding more installers (and right now= , I know a number of people think we should be doing the opposite, and simp= lifying the choices given to users).
=C2=A0
--
Dave Page
Blog: http://pgsnake.blogspot.comTwitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterpris= e PostgreSQL Company
--000000000000eb179d0588d6ba9e--