Skip to content

Conversation

hugovk
Copy link
Member

@hugovk hugovk commented Sep 18, 2025

We've been retiring mailing lists in favour of Discourse (python-dev, python-committers, typing-sig, python-ideas, translations).

Let's stop sending the release announcements to the mailing lists.

I spoke with @Yhg1s at the sprint, and decided we'll mention this plan in the 3.14.0rc3 email, then do a final one with 3.14.0 final, and then we can stop sending them out entirely.

Release announcements can still be found on Discourse and the blog.

cc @savannahostrowski


📚 Documentation preview 📚: https://pep-previews--4596.org.readthedocs.build/

@ned-deily
Copy link
Member

I understand that MLs are old-skool technology and their use has greatly declined so, even though the overhead of posting release announcments to the MLs is very small, ... progress. We should keep in mind, though, that these MLs are documented at various spots in our documentation and our website, so those refs should be updated, and the mailing lists are cross-posted to other media, like gmane.* and Usenet groups, so the size of the readership for the MLs is difficult to estimate and it may make sense to provide a longer transition period.

Copy link
Member

@AA-Turner AA-Turner left a comment

Choose a reason for hiding this comment

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

Are the notes re python-cabal still relevant? Also the note on acquiring an email address (following para) might need to be updated to account for Sigstore.

A

@willingc
Copy link
Contributor

@ned-deily Would it be ok to only post to the Announcements mailing list?

@ned-deily
Copy link
Member

Would it be ok to only post to the Announcements mailing list?

@willingc, sure. As long as other Python-related projects are still posting to the Announcements mailing list, we probably should continue to.

@Yhg1s
Copy link
Member

Yhg1s commented Sep 18, 2025

Posting to python-announce@ is the thing we're talking about stopping. Part of the reason is the hassle of crafting the message, because the markup is different from discourse/the blog. The blog is awkward for its own reasons, but at least it's editable. Email is not.

@ned-deily
Copy link
Member

The release script could just generate a templated plain text email that essentially just contains a link to the nicely-formatted Discourse and/or blog post. But it wouldn't be the end of the world if it didn't.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants