Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u5Hvf-00FLS6-T9 for pgadmin-hackers@arkaria.postgresql.org; Thu, 17 Apr 2025 05:36:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1u5Hvc-00FPvE-BF for pgadmin-hackers@arkaria.postgresql.org; Thu, 17 Apr 2025 05:36:49 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u5Hvb-00FPv5-R0 for pgadmin-hackers@lists.postgresql.org; Thu, 17 Apr 2025 05:36:48 +0000 Received: from mail-oi1-x22c.google.com ([2607:f8b0:4864:20::22c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1u5HvX-000UUv-1r for pgadmin-hackers@postgresql.org; Thu, 17 Apr 2025 05:36:46 +0000 Received: by mail-oi1-x22c.google.com with SMTP id 5614622812f47-3fa6c54cdb2so289299b6e.3 for ; Wed, 16 Apr 2025 22:36:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1744868203; x=1745473003; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=J/eoIsFX5E/WDy3wTyxmclCAXq0g3bv3WWb6UB9U6xs=; b=VGqFDrgcZQjSRVdM53B86vi1PTlaSitUwpjae8/1SPQQUMc/XCboEtpQ+aJtPG8kif WuPr4A8lFvEZHyJsiNpwaOVJQOCTDnSkhJlDD9JHQ6YcxGhQfeA2FprOCpSX+oOvwoRr jCnYOBDt6t2Kg8DW5FJkcQO/PUQ3MDYnuDUatY9RndvWLE+bMBmF2jEN4sTNJEGB9bPp BIo6JZYcWdErryI5f1raf6Uv0zj2FTHqXpqjYBET9L9OkgcXcFdUSE3tgfJ/thPYMfao d9KNsThQpr0ueuHPLi9sqZp2AURj07LtiMF9Havgy9VTHycpPb1CZrJWCfeZQXoJjxy7 FasQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744868203; x=1745473003; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=J/eoIsFX5E/WDy3wTyxmclCAXq0g3bv3WWb6UB9U6xs=; b=siwilmXOk35bfkYPsoJYL1yFCj1dtFUG5DfKKVTWcKvl5CJsH9rOx19cMbXzGZ6/R4 u+7w6n/AYQokdnxAsneUHWiJtC/GrRSs8PETmqI2h1AwI1L8nZpO//qqQubP/tsnYYpI 2beXUcv1vtUU5qJ1L+fg6TrJYnWOoVCWvIr7TwRuin2HWAEAzl++Awan2KJLPz5BmVDU 6yOdQ5qZ7y/rLWPlLi9VHM1QKzm2EydEgBHp/q5FSzro3wCXQ33q6KvwGmWC4SYRYDcA MZU2i+h7L0DZfRBZvZ5SO1IPjMDXZzMiZ/QF8qbUeC+ayrcz9XHHtPI3albDlKqqEP4F WpGQ== X-Gm-Message-State: AOJu0Yx2wvu1/VRMk/85FjNYn7flIt7YDFVX2/lSqV/8rerzbH1Hyhe9 2PjlxRH/baKBndjjjiLr4oBZ33cyaw6tBkNzlidI8aQWEiOJnQxQJ9redHk7d9vmGxaMpeYd0MD j7u2F1ZyEFZeWTb4N9jb5/z4ONiyTt0x4sR5y/HeT19bX/ZKpXwwuVw8= X-Gm-Gg: ASbGncu9xZvjdwfct3XlhbZFBj2eHRCNnl5zrVkSeUchpv1rfrBbXID+vJjCL2TSwnm VhNEcVt5EivCh7Lt4j4nYuOBzbq7twriq8ysNiYtDK4ybjbEyS5HcOpbVI/uf8tIaqqyxv+4ZHA pltxlCgIPrUHh5WJumXDB1/A5cxtsPf5IbERoTRdq//d4ua/D0bVvji2c= X-Google-Smtp-Source: AGHT+IHdaslCpXZNwmz4U/o0VAcgjGa68dVi5vkHcIg2xFhqPlBHppoKCkUk6u7/qCIn/rnPmdxEYBLGB6S7E0CmKBo= X-Received: by 2002:a05:6808:4446:b0:3fe:f41d:463a with SMTP id 5614622812f47-400b01cf338mr3285573b6e.10.1744868202591; Wed, 16 Apr 2025 22:36:42 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Anil Sahoo Date: Thu, 17 Apr 2025 11:06:05 +0530 X-Gm-Features: ATxdqUHgvsmcc9OmWuJMW-rwEBatzMqo6lc31mAFqZbIoHTebNJgP6ssxqFzYjU Message-ID: Subject: Re: Require suggestions on feature #5766 To: Dave Page Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="0000000000006555bb0632f2c992" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006555bb0632f2c992 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Dave, Yes zip files will have the version number, here is an example: pgadmin4-9.2-arm64.zip. Yes, version number will be included in the earlier mentioned URL. Also I will keep the field names in lower case. Thanks On Wed, Apr 16, 2025 at 7:15=E2=80=AFPM Dave Page wrote= : > Hi > > On Wed, 16 Apr 2025 at 11:38, Anil Sahoo > wrote: > >> Hi Dave, >> >> As we discussed in the last meeting, along with your suggestion to add a >> key in pgaweb's versions.json indicating the source URL for downloading >> updates for the auto-update feature, I propose the following approach. W= e >> will need to make corresponding changes in the pgaweb repository to >> support this. >> >> *Example versions.json format:* >> >> { >> >> =E2=80=9Cedb-pgadmin4=E2=80=9D: { >> =E2=80=9Cversion=E2=80=9D: =E2=80=9C9.0=E2=80=9D, >> =E2=80=9Cversion_int=E2=80=9D: 90000, >> =E2=80=9Cdownload_url=E2=80=9D: =E2=80=9C >> https://www.enterprisedb.com/downloads/postgres-postgresql-downloads=E2= =80=9D, >> =E2=80=9Cauto_update_url=E2=80=9D: { >> =E2=80=9CmacOS=E2=80=9D: =E2=80=9C=E2=80=9C, >> =E2=80=9Cwindows=E2=80=9D: =E2=80=9C=E2=80=9D >> } >> }, >> =E2=80=9Cpgadmin4=E2=80=9D: { >> =E2=80=9Cversion=E2=80=9D: =E2=80=9C9.2=E2=80=9D, >> =E2=80=9Cversion_int=E2=80=9D: 90200, >> =E2=80=9Cdownload_url=E2=80=9D: =E2=80=9Chttps://www.pgadmin.org/dow= nload/=E2=80=9D, >> =E2=80=9Cauto_update_url=E2=80=9D: { >> =E2=80=9CmacOS=E2=80=9D: =E2=80=9C >> https://ftp.postgresql.org/pub/pgadmin/pgadmin4/v9.2/macos/=E2=80=9D, >> =E2=80=9Cwindows=E2=80=9D: =E2=80=9C >> https://ftp.postgresql.org/pub/pgadmin/pgadmin4/v9.2/windows/=E2=80=9D >> } >> } >> } >> > Yes, that seems reasonable - except I'd keep the field names all in lower > case. > > >> Additionally, as I mentioned earlier, for Electron=E2=80=99s auto-update= to >> function on macOS, we need to provide a zip installer that contains the = pgAdmin >> 4.app. >> >> If we maintain zip installers for both arm64 and x86_64 macOS >> architectures, and potentially extend auto-update support to Windows in = the >> future, we estimate requiring up to 1.5 GB of additional storage on the = FTP >> server beyond the current allocation. Please note that we only need to >> store the zip files for the latest version, as older versions will be >> updated directly to the newest release. >> >> Please share your suggestions on this. >> > Do the zip files include the version number (and is that also included in > the URLs above)? > > >> Thanks, >> Anil >> >> On Wed, Mar 19, 2025 at 6:53=E2=80=AFPM Anil Sahoo >> wrote: >> >>> Okay, I will implement it as per the suggestions. >>> >>> Thanks >>> >>> On Wed, Mar 19, 2025 at 5:14=E2=80=AFPM Dave Page w= rote: >>> >>>> >>>> >>>> On Wed, 19 Mar 2025 at 10:58, Anil Sahoo >>>> wrote: >>>> >>>>> Hi Dave, >>>>> >>>>> As discussed I moved with auto-update of pgAdmin 4 application in >>>>> macOs system locally. It is successful. >>>>> So now I have to do some additional user experience improvements. >>>>> >>>>> Listing down some ways we can show the user that a new version is >>>>> available and he can download and install it. >>>>> >>>>> *Option 1:* >>>>> >>>>> Show a dialog with the released features and fixes(mentioned in the >>>>> release note) with *"Download & Restart"* and *"Cancel"* buttons. >>>>> This dialog will be shown only when the application starts for the fi= rst >>>>> time of the day. >>>>> >>>>> Benefits of showing this dialog will help users to know about the new >>>>> features and bugs fixed available in the latest version. >>>>> >>>>> "Download & Restart" button will download the latest version and quit >>>>> the app and install and open the latest app. "Cancel" will cancel the >>>>> notification. >>>>> >>>>> *Option 2:* >>>>> >>>>> We are currently showing a warning notification of the latest version >>>>> available, if the older version is being used by the user, we can add= *"Download >>>>> & Restart"* and *"Cancel" * buttons. And those buttons will work the >>>>> way they are working in Option 1. >>>>> >>>>> Additionally we will add *"Check for updates"* option in pgAdmin 4 >>>>> native menu, if any time a user wants to check for updates manually t= hen >>>>> can prefer this and if update is available then the *"Restart to >>>>> update"* option will show and if clicked will quit the app and >>>>> install the latest version. >>>>> >>>>> Let me know in which way we can proceed. >>>>> >>>> >>>> Option 1 seems good to me; though the current notifier should continue >>>> to work as it does now if a particular distribution channel doesn't su= pport >>>> auto-updates (for example, the EDB PostgreSQL Installer). >>>> >>>> -- >>>> Dave Page >>>> pgAdmin: https://www.pgadmin.org >>>> PostgreSQL: https://www.postgresql.org >>>> pgEdge: https://www.pgedge.com >>>> >>>> >>> >>> -- >>> >>> >>> *Anil Sahoo* >>> >>> Software Development Engineer II >>> >>> LinkedIn || Blog >>> || *GitHub >>> * >>> >>> enterprisedb.com >>> >> >> >> -- >> >> >> *Anil Sahoo* >> >> Software Development Engineer II >> >> LinkedIn || Blog >> || *GitHub >> * >> >> enterprisedb.com >> > > > -- > Dave Page > pgAdmin: https://www.pgadmin.org > PostgreSQL: https://www.postgresql.org > pgEdge: https://www.pgedge.com > > --=20 *Anil Sahoo* Software Development Engineer II LinkedIn || Blog || *GitHub * enterprisedb.com --0000000000006555bb0632f2c992 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Dave,

Yes zip files will have the ve= rsion number, here is an example:=C2=A0pgadmin4-9.2-arm64.zip.=C2=A0
<= div>
Yes, version number will be included in the earlier ment= ioned URL.

Also I will keep the field names in= lower case.

Thanks

On = Wed, Apr 16, 2025 at 7:15=E2=80=AFPM Dave Page <dpage@pgadmin.org> wrote:
Hi

On Wed, 16 Apr 2025 = at 11:38, Anil Sahoo <anil.sahoo@enterprisedb.com> wrote:

Hi Dave,

As we discusse= d in the last meeting, along with your suggestion to add a key in pgaweb= 9;s=C2=A0versions.json indicating the source URL for downloadi= ng updates for the auto-update feature, I propose the following approach. W= e will need to make corresponding changes in the pgaweb reposi= tory to support this.

Exampl= e versions.json format:

{

=C2=A0=C2=A0=E2=80=9Cedb-= pgadmin4=E2=80=9D: {
=C2=A0=C2=A0=C2=A0=C2=A0=E2=80=9Cversion=E2=80=9D: =E2=80=9C9.0=E2=80= =9D,
=C2=A0=C2= =A0=C2=A0=C2=A0=E2=80=9Cversion_int=E2=80=9D: 90000,
=C2=A0=C2=A0=C2=A0=C2=A0=E2=80=9Cdown= load_url=E2=80=9D: =E2=80=9Chttps://www.enterprisedb.com/downloads/postgres-postgresql-downloads= =E2=80=9D,
= =C2=A0=C2=A0=C2=A0= =C2=A0=E2=80=9Cauto_update_url=E2=80=9D: {
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=E2=80=9CmacOS=E2=80=9D: =E2=80=9C<edb_installer_url>=E2=80=9C,
=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=E2=80=9Cwindows=E2=80=9D: =E2=80=9C<ed= b_installer_url>=E2=80=9D
=C2=A0=C2=A0=C2=A0}
=C2=A0=C2=A0},
=C2=A0=C2=A0=E2=80=9Cpgadmin4=E2=80=9D: {
=C2=A0=C2=A0=C2=A0=C2=A0=E2= =80=9Cversion=E2=80=9D: =E2=80=9C9.2=E2=80=9D,
=C2=A0=C2=A0=C2=A0=C2=A0=E2=80=9Cversion_in= t=E2=80=9D: 90200,
=C2=A0=C2=A0=C2=A0=C2=A0=E2=80=9Cdownload_url=E2=80=9D: =E2=80=9Chttps://www.pgadmin.org/download/=E2=80=9D,
=C2=A0=C2=A0=C2=A0=C2=A0=E2=80=9Cauto_update_url= =E2=80=9D: {
= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=E2=80=9CmacOS=E2=80=9D: = =E2=80=9Chttps://ftp.postgresql= .org/pub/pgadmin/pgadmin4/v9.2/macos/=E2=80=9D,
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=E2=80=9C= windows=E2=80=9D: =E2=80=9Chttps://ft= p.postgresql.org/pub/pgadmin/pgadmin4/v9.2/windows/=E2=80=9D
=C2=A0=C2=A0=C2=A0}
=C2=A0=C2=A0}
}

Yes, that seems reasonable - except I'd keep the field = names all in lower case.
=C2=A0

= Additionally, as I mentioned earlier, for = Electron=E2=80=99s auto-update to function on macOS, we need to provide a z= ip installer that contains the pgAd= min 4.app.

If we maintain= zip installers for both arm64 and x86_64 macOS a= rchitectures, and potentially extend auto-update support to Windows in the = future, we estimate requiring up to 1.5 GB of additional storage on the FTP= server beyond the current allocation. Please note that we only need to sto= re the zip files for the latest version, as older versions will be updated = directly to the newest release.

Please share your suggestions on this.

Do the zip files include the version number (and is that also included in = the URLs above)?
=C2=A0
Thanks,=
Anil

On Wed, Mar 19, 2025 at 6:53=E2=80=AFPM Anil Sahoo <<= a href=3D"mailto:anil.sahoo@enterprisedb.com" target=3D"_blank">anil.sahoo@= enterprisedb.com> wrote:
Okay, I will implement it as per the sugge= stions.

Thanks

On Wed, Mar 19, 2025 at 5:14=E2=80= =AFPM Dave Page <= dpage@pgadmin.org> wrote:


On Wed, 19 Mar 2025 = at 10:58, Anil Sahoo <anil.sahoo@enterprisedb.com> wrote:
Hi Dave,
As discussed I moved with auto-update of pgAdmin 4 application = in macOs system locally. It is successful.=C2=A0
So now I have to= do some additional user experience improvements.

= Listing down some ways we can show the user that a new version is available= and he can download and install it.

Option 1:<= /b>=C2=A0
Show a dialog with the released features and fixes(mentioned in= the release note) with "Download & Restart" and &q= uot;Cancel"=C2=A0 buttons. This dialog will be shown only when the= application starts for the first time of the day.

<= /div>
Benefits of showing this dialog will help users to know abou= t the new features and bugs fixed available in the latest version.=C2=A0

"Download & Restart" button will d= ownload the latest version and quit the app and install and open the latest= app.=C2=A0"Cancel" will cancel the notification.
<= /blockquote>Option 2:
We are currently showing a warning notification of th= e latest version available, if the older version is being used by the user,= we can add=C2=A0"Download & Restart" and "C= ancel"=C2=A0 buttons. And those buttons will work the way they are= working in Option 1.

Additi= onally we will add "Check for updates" option in pgAdmin 4 nati= ve menu, if any time a user wants to check for updates manually then can pr= efer this and if update is available then the=C2=A0"Restart to up= date" option will show and if clicked will quit the app and instal= l the latest version.

=
Let me know in which way we= can proceed.

Option 1 s= eems good to me; though the current notifier should continue to work as it = does now if a particular distribution channel doesn't support auto-upda= tes (for example, the EDB PostgreSQL Installer).
=C2=A0
--


--


Anil Sahoo=

Software Develop= ment Engineer II

LinkedIn=C2=A0|| Blog= =C2=A0|| GitHub


enterprisedb.com

<= /span>


--


Anil Sahoo=

Software Develop= ment Engineer II

LinkedIn=C2=A0|| Blog= =C2=A0|| GitHub


enterprisedb.com

<= /span>


--


--


=

Anil Sahoo

= Software Developmen= t Engineer II

LinkedIn=C2=A0|| Blog=C2= =A0|| GitHub


enterprisedb.com

--0000000000006555bb0632f2c992--