Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l2cKB-0000jf-Q6 for pgadmin-support@arkaria.postgresql.org; Thu, 21 Jan 2021 15:56:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l2cKA-0002m9-Kc for pgadmin-support@arkaria.postgresql.org; Thu, 21 Jan 2021 15:56:42 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l2cJQ-0002Sr-8r for pgadmin-support@lists.postgresql.org; Thu, 21 Jan 2021 15:55:56 +0000 Received: from mail-ej1-x634.google.com ([2a00:1450:4864:20::634]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1l2cJN-0001BD-NR for pgadmin-support@postgresql.org; Thu, 21 Jan 2021 15:55:55 +0000 Received: by mail-ej1-x634.google.com with SMTP id r12so3273090ejb.9 for ; Thu, 21 Jan 2021 07:55:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; h=mime-version:from:date:message-id:subject:to; bh=4slmmkJfWAXyEviD4SvqPsP7lrcO3O/+P+HZp+Ax1fI=; b=kA9rzObv8UYZhmWhy5aTWwliE7EdpaobTNGQUbTLtEkB4vgw++LYTdI5RhZ0GKsQ+1 wdWtQvZsOdTUyaEPvoXVQNQ/ZeuKUa2a1Aw7h+D9ePWXcpGyCy8pt1uk/ILgtCik0MfV yvyot9Z3rzjbJ6Tt7pw/td1Od4ayKhu9AbNQJD4eSBl2YKPZM6+fqIBXi/2F8Ocu15rR fOxy6fpsN7pVkscHtTY/G+iXc/BuBShJdAhK712hUFr+d36lbTg8XH/nIJ6ZYXhfiCwh 9KS6Rh9JUUo1smgG4j/9H+9aGL3tyAuubb4HH6WVK2ymIdbVZ1q3dcnR8IE/NIWPhVXf r1RQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=4slmmkJfWAXyEviD4SvqPsP7lrcO3O/+P+HZp+Ax1fI=; b=XUM4o2k1mrKiO2josAiT+LqiTb7I2fLZwbZA71qHhAxz1s4G3jMlQeNTJ/a6AnGwgS HX9wFBO2NHSdZn7ORbPFdTY6kmYaZfB13YUcMxiImzPuz12EEmiqWfPV9q3PaX9q+hGg OPVlgbFXnRUoiFmRcdbARW80PsE1WEeCwjTgCePzrNS241NOJH5n/3bvYv1f6y93WdqY WyL2vTVWV324y2YXANeQU6yriFxwle61jjSNVUfY1tgX0SxyeRZIblOlV2HdTg1vgg5r S+4CdouUcOJIpvKHZswMu86vb1WYaT7irS9a+TYV/zd4yEASKrC4QdJaE+SpS9LDPLXU G7/w== X-Gm-Message-State: AOAM533iKZP3iSUQk31mXvUkASygXpe4oVdLW3BBvNi7oMqGZ39Pqd6M sJPmoTff99G5y3ZxX2JFqa7Xh21fxSP82wOdblgiA/fy4l2xNw7g X-Google-Smtp-Source: ABdhPJxV70xqoYu9kLYvwYbUoZkx2PvvPgLKW/wLHXs1TiDzTMKDgKvHDN4/sOZ/aR+7S8JbU8fp8u9vCpAxoHb+zxc= X-Received: by 2002:a17:907:f81:: with SMTP id kb1mr91717ejc.412.1611244552317; Thu, 21 Jan 2021 07:55:52 -0800 (PST) MIME-Version: 1.0 From: Dave Page Date: Thu, 21 Jan 2021 15:55:41 +0000 Message-ID: Subject: Testing required: pgAdmin 4 with new desktop runtime To: pgadmin-hackers , pgAdmin Support Content-Type: multipart/alternative; boundary="00000000000030035e05b96b1b54" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --00000000000030035e05b96b1b54 Content-Type: text/plain; charset="UTF-8" All, As you know, when run in Desktop mode, pgAdmin 4 uses a server process which runs all the time and opens a browser window to display the UI. Very early versions used a Qt based runtime that integrated the browser and server which gave a much more "normal" application feel, but unfortunately we found that the Qt browser components had performance issues. We've been working on a new runtime (based on NWjs, similar to Electron) to allow us to get rid of the separate server process, and I'm please to offer builds for testing at: https://developer.pgadmin.org/builds/nwjs-2021-01-21-1/ There you'll find an installer for 64 bit Windows, a DMG for macOS, and RPM and DEB packages for Fedora 31, 32 & 33, RHEL/CentOS 7 & 8, Debian 9, 10 & 11 and Ubuntu 18.04, 20.04 and 20.10. These builds are based on development code currently in git that will be released as v4.30 next week. This includes phase 1 of our Kerberos support (for logging into pgAdmin, but *not* the database servers), and the new ERD tool. This code is still going through QA and final improvement, so please bear that in mind. We're aiming to release v5.0 of pgAdmin 4 in late February, based on the new runtime, so would appreciate as much help and feedback as we can get prior to the release. Whilst I'm writing, I'd also like to give an update on platform support changes; - As previously noted in release announcements, Windows 32 bit builds are deprecated. v4.29 will be the last 32 bit Windows build supported. - Canonical have dropped support for Ubuntu 19.10, and now removed all of the packages repositories. We have therefore had to drop support for it as well; the last supported version of pgAdmin on Ubuntu 19.10 will be v4.29. - Due to the age of the Python version it ships with, we've had to stop producing builds for Ubuntu 16.04 (some of the security related Python modules are no longer supported on older Python versions). v4.30 will be the last version supported on Ubuntu 16.04. - Builds for Ubuntu 20.10 and Debian 11 (Bullseye/testing) have been added for the v4.30 release onwards. Thank you! -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EDB: http://www.enterprisedb.com --00000000000030035e05b96b1b54 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
All,

As you know, when run in Desktop m= ode, pgAdmin 4 uses a server process which runs all the time and opens a br= owser window to display the UI. Very early versions used a Qt based runtime= that integrated the browser and server which gave a much more "normal= " application feel, but unfortunately we found that the Qt browser com= ponents had performance issues.

We've been wor= king on a new runtime (based on NWjs, similar to Electron) to allow us to g= et rid of the separate server process, and I'm please to offer builds f= or testing at:


There you'll find an install= er for 64 bit Windows, a DMG for macOS, and RPM and DEB packages for Fedora= 31, 32 & 33, RHEL/CentOS 7 & 8, Debian 9, 10 & 11 and Ubuntu 1= 8.04, 20.04 and 20.10.

These builds are based on d= evelopment code currently in git that will be released as v4.30 next week. = This includes phase 1 of our Kerberos support (for logging into pgAdmin, bu= t *not* the database servers), and the new ERD tool. This code is still goi= ng through QA and final improvement, so please bear that in mind.

We're aiming to release v5.0 of pgAdmin 4 in late Febru= ary, based on the new runtime, so would appreciate as much help and feedbac= k as we can get prior to the release.

= Whilst I'm writing, I'd also like to give an update on platform sup= port changes;

- As previously noted in release ann= ouncements, Windows 32 bit builds are deprecated. v4.29 will be the last 32= bit Windows build supported.

- Canonical have dro= pped support for Ubuntu 19.10, and now removed all of the packages reposito= ries. We have therefore had to drop support for it as well; the last suppor= ted version of pgAdmin on Ubuntu 19.10 will be v4.29.

- Due to the age of the Python version it ships with, we've had= to stop producing builds for Ubuntu 16.04 (some of the security related Py= thon modules are no longer supported on older Python versions). v4.30 will = be the last version supported on Ubuntu 16.04.

- B= uilds for Ubuntu 20.10 and Debian 11 (Bullseye/testing) have been added for= the v4.30 release onwards.

Thank you!

--
Dave Page
Blog: http://pgsnake.blogspot.comTwitter: @pgsnake

EDB: http://www.enterprisedb.com

--00000000000030035e05b96b1b54--