public inbox for [email protected]
help / color / mirror / Atom feedFrom: Pravesh Sharma <[email protected]>
To: pgadmin-hackers <[email protected]>
Cc: Dave Page <[email protected]>
Subject: Re: Next Library/Package update
Date: Tue, 5 Nov 2024 12:52:57 +0530
Message-ID: <CA+36bxFDm=tdov8wrjAD+028VbWWaJm6GCmM9oCnSnJoAeRWng@mail.gmail.com> (raw)
In-Reply-To: <CANxoLDcy60WFp0hXmhw6zCKqfAhu2SheH0BgQ5SegHs26jJ_5w@mail.gmail.com>
References: <CANxoLDfbtxPtFgnuXrcfvrMdt9z+Q91=j+FbZTriRaxFN7J8FA@mail.gmail.com>
<CA+36bxHQ27W_Bm_V_i8GPewEFNu2fA8BD+Aa8Prm0viUJUCFfg@mail.gmail.com>
<CA+36bxH9yg1wvcPZQFxgx4DDGjfJPMvrKJu3NXp7+B-EVrYjOg@mail.gmail.com>
<CANxoLDcy60WFp0hXmhw6zCKqfAhu2SheH0BgQ5SegHs26jJ_5w@mail.gmail.com>
Hi Dave/Team,
The next pgAdmin 4 release, version 8.13, is scheduled for November 14,
2024. I have reviewed the upcoming OS releases and their EOL dates, and
here are the details:
- Fedora 41 has already been released, and we need to add support for it.
- Fedora 39 will reach EOL on November 12, 2024, so we can drop support
for it.
- We need to test pgAdmin 4 on macOS Sequoia due to a reported issue,
but we do not have a machine available for testing.
Please share your thoughts or suggestions.
Thanks,
Pravesh
On Thu, Jun 27, 2024 at 5:57 PM Akshay Joshi <[email protected]>
wrote:
> Hi All,
>
> The next pgAdmin 4 release, v8.10, is scheduled for July 25, 2024. Based
> on the EOL dates of the operating system in the previous email, we will
> discontinue support for *Debian 10* and *Ubuntu 23.10* (with an updated
> EOL of July 11) starting with this release. If anyone has any
> objections/suggestions, please let us know.
>
> On Tue, May 14, 2024 at 10:53 AM Pravesh Sharma <
> [email protected]> wrote:
>
>> Hi Team,
>>
>> I have reviewed the list of upcoming OS releases and EOL dates. Below are
>> the details:
>>
>> Upcoming OS versions:
>> 1. Fedora 40 - released on 23 Apr 2024
>> 2. Ubuntu 24.04 - released on 25 Apr 2024
>>
>> OS nearing EOL:
>> 1. Fedora 38 - 14 May 2024
>> 2. Debian 10 - 30 Jun 2024
>> 3. Ubuntu 23.10 - 01 Jul 2024
>>
>> Please note that Python 3.8 security support will end on 31 Oct 2024.
>> I have referenced the details from here <https://endoflife.date/;.
>>
>> Regards,
>> Pravesh Sharma
>>
>>
>> On Thu, Apr 11, 2024 at 5:04 PM Pravesh Sharma <
>> [email protected]> wrote:
>>
>>> Hi Dave/ Team,
>>>
>>> While updating to the latest Flask version, I found that support for
>>> Python 3.7 has been dropped on most of the packages. Debian 10, which
>>> defaults to Python 3.7, will reach its End of Life on 30th June 2024.
>>> Should we drop support for Python 3.7 in the upcoming May release with the
>>> package update, or should we wait?
>>>
>>>
>>> @team Please share your suggestions.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Pravesh
>>>
>>> On Wed, Jun 21, 2023 at 12:55 PM Akshay Joshi <
>>> [email protected]> wrote:
>>>
>>>> Hi Dave/Team
>>>>
>>>> Following things that we should update as the next big change:
>>>>
>>>> 1. Flask and other dependent packages( Can't pick until we drop
>>>> support for Python 3.7)
>>>> 2. WCDocker
>>>> 3. Mui 5
>>>> 4. Code Mirror 6
>>>> 5. React Aspen tree with React Arborist (
>>>> https://www.npmjs.com/package/react-arborist)
>>>>
>>>>
>>>> --
>>>> Akshay Joshi
>>>> Principal Software Architect
>>>> www.enterprisedb.com
>>>>
>>>> *Blog*: https://www.enterprisedb.com/akshay-joshi
>>>> *GitHub*: https://github.com/akshay-joshi
>>>> *LinkedIn*: https://www.linkedin.com/in/akshay-joshi-086497216
>>>>
>>>
>>>
>>> --
>>>
>>> <http://www.enterprisedb.com;
>>>
>>> Pravesh Sharma
>>>
>>> Software Engineer
>>>
>>> +91 9406461406
>>>
>>> www.enterprisedb.com
>>>
>>> Power to Postgres
>>>
>>> <https://www.linkedin.com/company/edbpostgres;
>>> <https://twitter.com/edbpostgres?lang=en;
>>> <https://www.facebook.com/EDBpostgres;
>>> <https://www.instagram.com/EDBpostgres/;
>>>
>>
--
Pravesh Sharma
Senior SDE
+91 9406461406
enterprisedb.com
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Next Library/Package update
In-Reply-To: <CA+36bxFDm=tdov8wrjAD+028VbWWaJm6GCmM9oCnSnJoAeRWng@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox