-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Announce Python / PostgreSQL deprecation policies #9085
Conversation
Fixes matrix-org#8782 [skip ci] Signed-off-by: Dan Callahan <[email protected]>
Ending Support for Python 3.5 and Postgres 9.5 | ||
---------------------------------------------- |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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
* 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). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Neat website. 👍
There was a problem hiding this comment.
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.
There was a problem hiding this 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. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤠
Is 74a3959 better?
There was a problem hiding this comment.
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.
Signed-off-by: Dan Callahan <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
Fixes #8782
[skip ci]