Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Announce Python / PostgreSQL deprecation policies #9085

Merged
merged 3 commits into from
Jan 12, 2021

Conversation

callahad
Copy link
Contributor

Fixes #8782

[skip ci]

Comment on lines +4 to +5
Ending Support for Python 3.5 and Postgres 9.5
----------------------------------------------
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be above the rc1 release notes and get put into the 1.25.0 release notes?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

...yep. Fixed.

CHANGES.md Outdated Show resolved Hide resolved
CHANGES.md Outdated
* We will end support for PostgreSQL 9.5 early next month.
* We will end support for Python 3.6 and PostgreSQL 9.6 near the end of the year.

The https://endoflife.date/ website has convenient summaries of the support schedules for projects like [Python](https://endoflife.date/python) and [PostgreSQL](https://endoflife.date/postgresql).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Neat website. 👍

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I blame @ShadowJonathan 🙂 It is really well presented.

CHANGES.md Outdated Show resolved Hide resolved
Copy link
Member

@clokep clokep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems fine overall.

Signed-off-by: Dan Callahan <[email protected]>
CHANGES.md Outdated

Which means:

* This is the last release which supports Python 3.5.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is correct, I think we need to call out the fact that it means we will no longer provide debs for stretch and xenial more explicitly.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's also not really what was said on #8782.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤠

Is 74a3959 better?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does extend the transition period a bit from what #8782 proposed, but has less nuance to its messaging.

I'm trying to strike a balance between "oh hey they're serious" and "we've still got time."

I think that's important because, if we're honest with ourselves, we're in that world right now. Python 3.5 is unsupported, and we don't have the spare capacity to backport fixes as our dependencies drop support.

This has happened at least a few times in the past two months (PySAML, PyJWT). And now that they've broken compatibility, if their next update resolves a serious vulnerability, we're in for a lot of completely preventable pain.

Copy link
Member

@richvdh richvdh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@callahad callahad merged commit 6d91e6c into matrix-org:release-v1.25.0 Jan 12, 2021
@callahad callahad deleted the deprecation branch January 12, 2021 20:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants