Add policy to bump postgres minimum version #7709
Conversation
agnivade
added
1: Dev Review
|
Newest code from mattermost has been published to preview environment for Git SHA 99a4ed3 |
|
@agnivade - I've committed updates to convert the Markdown draft to ReStructuredText, wordsmithed the content for simplicity, and added links to these policy details to related pages. Please review the wordsmithing to ensure that the updated copy aligns with your intentions. |
|
Newest code from mattermost has been published to preview environment for Git SHA e10b928 |
|
|
||
| Mattermost v10.6 is not an :ref:`Extended Support Release (ESR) <about/release-policy:extended support releases>`. Going forward, this database version support policy will only apply to ESR releases. When a Postgres version reaches its end of life (EOL), Mattermost will require a newer version starting with the next scheduled ESR release. | ||
|
|
||
| Customers will have 9 months to plan, test, and upgrade their Postgres version before the new requirement takes effect. If you need more time, extended ESR support may be available on a case-by-case basis. This policy aims to provide clarity and transparency so you can align database upgrades with the Mattermost release schedule. Contact a `Mattermost Expert <https://mattermost.com/contact-sales/>`_. to discuss your options. |
There was a problem hiding this comment.
| Customers will have 9 months to plan, test, and upgrade their Postgres version before the new requirement takes effect. If you need more time, extended ESR support may be available on a case-by-case basis. This policy aims to provide clarity and transparency so you can align database upgrades with the Mattermost release schedule. Contact a `Mattermost Expert <https://mattermost.com/contact-sales/>`_. to discuss your options. | |
| Customers will have 9 months to plan, test, and upgrade their PostgreSQL version before the new requirement takes effect. If you need more time, extended ESR support may be available on a case-by-case basis. This policy aims to provide clarity and transparency so you can align database upgrades with the Mattermost release schedule. Contact a `Mattermost Expert <https://mattermost.com/contact-sales/>`_. to discuss your options. |
Co-authored-by: Amy Blais <[email protected]>
Co-authored-by: Amy Blais <[email protected]>
Co-authored-by: Amy Blais <[email protected]>
|
Newest code from mattermost has been published to preview environment for Git SHA c449e5f |
|
Newest code from mattermost has been published to preview environment for Git SHA 27232c0 |
|
Newest code from mattermost has been published to preview environment for Git SHA c8dafd5 |
|
Newest code from mattermost has been published to preview environment for Git SHA 5a36c06 |
|
Newest code from mattermost has been published to preview environment for Git SHA 70eae77 |
| .. note:: | ||
|
|
||
| - Mattermost v10.6 is not an :ref:`Extended Support Release (ESR) <about/release-policy:extended support releases>`. Going forward, this database version support policy will only apply to ESR releases. | ||
| - When a PostgreSQL version reaches its end of life (EOL), Mattermost will require a newer version starting with the next scheduled ESR release. This means the following future PostgreSQL minimum version increases as follows: |
There was a problem hiding this comment.
@streamer45 & @sadohert - Is this what you had in mind? I'm not 100% sure I have the ESR dates/versions correct, given that March 2025 will be the v10.5 ESR.
There was a problem hiding this comment.
I think this works. Combining these 2 resources:
https://www.postgresql.org/support/versioning/
https://docs.mattermost.com/about/mattermost-server-releases.html
I was imagining a table like:
| Mattermost ESR | Release Date | Minimum Postgres Version |
|---|---|---|
| 9.11 | Aug 16,2025 | 12.x |
| 10.5 | Feb 16,2025 | 13.x |
| 10.11 | Aug 16, 2025 | 13.x |
| 11.5 * | Feb 16, 2026 | 14.x |
* Forecasted version and date
There was a problem hiding this comment.
@sadohert - One concern for the table is that it can lead to further maintenance effort for the team. Because now it's one more item to keep track of and update every ESR. I was thinking that just the 2 lines would be sufficient for customers to get an idea and extrapolate. WDYT?
There was a problem hiding this comment.
I feel the maintenance effort required to update a single row in the table is justified in this case as it adds valuable clarity for customers and eliminates any potential ambiguity. We could consider incorporating this as part of a playbook's checklist for the ESR release process.
There was a problem hiding this comment.
I'm still seeing the minimum PG version for 11.5 as Postgres 14.
Postgres 13 goes EOL on Nov. 13th/2025, according to https://endoflife.date/postgresql
So this coming November PG 13 goes EOL... I thought our policy was that the next ESR will bump... and thus our minimum goes to 14?
There was a problem hiding this comment.
Oops, my brain stopped functioning there. You are right @sadohert.
There was a problem hiding this comment.
I'll add this step to the release playbook.
|
Newest code from mattermost has been published to preview environment for Git SHA 20c3ca1 |
|
Newest code from mattermost has been published to preview environment for Git SHA 1da5289 |
|
Newest code from mattermost has been published to preview environment for Git SHA 5872acf |
|
Newest code from mattermost has been published to preview environment for Git SHA 8559416 |
|
Newest code from mattermost has been published to preview environment for Git SHA 6b185a9 |
|
Newest code from mattermost has been published to preview environment for Git SHA ce70c53 |
|
Looks good to me. If we have the "Process" step documented to maintain/update this section of the docs when we publish a new ESR, I think its good to ship. @amyblais do you have that capture in a Playbook or checklist somewhere? |
| +-----------------------------------------------------------+------------------+--------------------------------+ | ||
| | v10.11 ESR | 2025-8-15 | 13.x | | ||
| +-----------------------------------------------------------+------------------+--------------------------------+ | ||
| | v11.5 ESR ``*`` | 2026-2-15 | 14.x (EOL 2025-11-13) | |
There was a problem hiding this comment.
PSQL v14 goes EOL November 12, 2026
Yes, this is captured in a release playbook. |
|
Newest code from mattermost has been published to preview environment for Git SHA 856079a |
|
Newest code from mattermost has been published to preview environment for Git SHA 26e2fa7 |
cwarnermm
added
3: Reviews Complete
|
Newest code from mattermost has been published to preview environment for Git SHA 6d40e5f |
No description provided.