PostgreSQL 16.0.0 Released!

[<fabian.gruen@xxxxxxxxxxxxxxxxx>]

Title: Action Required: PostgreSQL New Release (v16.0.0) and Update Process

Hi Tomek,

 

great work so far. 😊

 

Also like the idea to integrate all community members to interact and discuss.

 

Some guesses for improving the current mail, would be from myside.

 

• Adding mailto:tractusx-dev@xxxxxxxxxxx links when writing about Mailing List
• Adding a link to our TRG´s  to find the current aligned version
• Maybe also link to  https://semver.org/ to reduce the explanation for MAJOR.MINOR.PATCH
• Removing version numbers when explaining what to do for specific major minor patch version
• Examples like Major: 15.x.x -> 16.x.x / Minor:  x.1.x -> x.2.x   / Patch: x.x.1 -> x.x.2
• Referencing to our contribution Guides on ETX web page

 

BR

Fabian

 

Von: Tomasz.Barwicki@xxxxxxxxxxxxx <Tomasz.Barwicki@xxxxxxxxxxxxx>
Gesendet: Mittwoch, 18. Oktober 2023 11:00
An: Gruen, Fabian (415) <fabian.gruen@xxxxxxxxxxxxxxxxx>; Zierer, Harald (415) <harald.zierer@xxxxxxxxxxxxxxxxx>; Bezold, Sebastian (415) <sebastian.bezold@xxxxxxxxxxxxxxxxx>; Lenz, Carsten (415) <carsten.lenz@xxxxxxxxxxxxxxxxx>
Cc: siegfried.kiermayer@xxxxxxx
Betreff: FW: Action Required: PostgreSQL New Release (16.0.0) and Update Process

 

[**EXTERNAL E-MAIL**]

Hey team,

 

As mentioned in the daily call, kindly requesting you to review PostgreSQL new release notification mail content.

Many thanks in advance for your feedback!

 

BR
TB

 

From: Almádi, Gábor <Gabor.Almadi@xxxxxxxxxxxxx>
Date: Tuesday, 17 October 2023 at 14:13
To: Barwicki, Tomasz (ext) <Tomasz.Barwicki@xxxxxxxxxxxxx>
Subject: Re: Action Required: PostgreSQL New Release (16.0.0) and Update Process

Hey Tomasz,

 

I like the format and the content, it’s very informative. I think for a talk initiation it’s enought and as stated in the context, the discussion can continue in a thread/discussion on GitHub/mail.

 

Just keep in mind that if I’m not mistaken, even though pg16 is out we still mark v15 as the mandatory. Sigi suggested last week to me that we won’t enforce the upgrade to new major version when it’s released.

 

Have a nice day!

 

Gábor Almádi

DevOps Engineer

Deutsche Telekom Systems Solutions

Deutsche Telekom IT Solutions

Growth Portfolio/ IoT & M2M SCC / IoT Digital

 

Tóth Kálmán utca, 2/b,  1097 Budapest, Hungary 

+36 30 566 98 34 (Mobile)

E-mail: gabor.almadi@xxxxxxxxxxxxx

www.deutschetelekomitsolutions.hu

--

 

From: Barwicki, Tomasz (ext) <Tomasz.Barwicki@xxxxxxxxxxxxx>
Date: Tuesday, 17 October 2023 at 11:26
To: Almádi, Gábor <Gabor.Almadi@xxxxxxxxxxxxx>
Subject: FW: Action Required: PostgreSQL New Release (16.0.0) and Update Process

Hey Gabor, please let me know your feedback on the below notification content for PostgreSQL release.

The key thing is to help me understand if it’s clear enough what needs to happen after receiving this email.

 

From: eclipse.tractusx@xxxxxxxxx <eclipse.tractusx@xxxxxxxxx>
Date: Monday, 16 October 2023 at 15:37
To:
Subject: Action Required: PostgreSQL New Release (16.0.0) and Update Process

PostgreSQL 16.0.0 Released!

Dear Tractus-X Community,

We're excited to inform you that PostgreSQL has released a new version, 16.0.0, and we need your attention to ensure our projects remain up-to-date and secure. Please follow the instructions below based on the type of release.

Current Aligned Version:

Our projects are currently aligned with PostgreSQL version 15.0.0.

Major Release (e.g., v15.0.0):

If a major release has occurred, we kindly request that you initiate a discussion on our Tractus-X mailing list to address the implications and eventually agree on the upgrade plan. Major releases may involve significant changes, and we want to ensure a smooth transition. Here are the key steps to follow:

1. Create a mailing list discussion thread with a clear title indicating the major PostgreSQL release upgrade.
2. Summarize the major changes in PostgreSQL v16.0.0 and discuss any potential impacts on our projects.
3. Collaborate with the community to outline a consensus on the upgrade.
4. Follow the agreed-upon process for implementing the major release upgrade.

Minor Release (e.g., v15.x.x):

For minor releases, we only need to update our Helm charts and their dependencies. Specifically, please update the Helm chart that includes PostgreSQL to ensure we are using the latest version, which, as of now, is PostgreSQL v16.0.0. To do this:

1. Review Your Helm Charts: Examine your Helm charts and identify any dependencies on PostgreSQL.
2. Update Helm Dependencies: Update the PostgreSQL Helm chart dependencies in your projects to the latest version compatible with PostgreSQL 16.0.0.
3. Test Thoroughly: After updating the dependencies, thoroughly test your applications to ensure they function correctly with the new PostgreSQL version.

Resources

You can find the latest PostgreSQL Helm charts on bitnami official Helm chart repository: Bitnami Helm Chart Repository.

Detailed documentation on how to update Helm chart dependencies can be found here: Documentation Link.

Contribution

We would like to invite you to contribute to this project and provide your valuable insights. Your feedback and suggestions will be greatly appreciated as we continue to refine and expand the functionality of our release notification tool.

To access the repository for this project and explore the code, please visit the following link: [GitHub].

---

We greatly appreciate your commitment to keeping our open source projects up-to-date and secure. Your collaboration is vital to the success of our community.

If you encounter any issues or have questions during the upgrade process, please don't hesitate to reach out to DevSecOps team.

Best regards,

DevSecOps Team

 

If you are not the addressee, please inform us immediately that you have received this e-mail by mistake, and delete it. We thank you for your support.