No release candidates would certainly make it easier (and perhaps allow it to be completely automated.) On Wed, Mar 6, 2024, at 4:56 AM, Adi Roiban wrote:
Many thanks for the release.
Happy to see a release done by someone else.
We were doing release candidates, but I don't know if we get any feedback on that.
I am not sure if people are testing RC releases and just don't report a successful test or people are not testing it.
Instead of testing release candidates, maybe is best to encourage running test based on the code from trunk.
To simplify the release process, maybe it would help not to do the release candidates.
If any issue is found, we release a .1 bugfix version.
What do you think?
Regards
On Fri, 1 Mar 2024, 16:50 Itamar Turner-Trauring, <itamar@itamarst.org> wrote:
__ On behalf of the Twisted contributors I announce the release of Twisted 24.3.0 (the release formerly known as 24.2.0, before too much time passed.)
The notable changes are: • A variety of small bug fixes. • A performance improvement when doing many very small writes over TLS. • Fix breakage with latest PyPy release. The release changes can be seen at https://github.com/twisted/twisted/releases/tag/twisted-24.3.0
Wheels for the release are available on PyPI.
Many thanks to everyone who worked on this release!
—Itamar _______________________________________________ Twisted mailing list -- twisted@python.org To unsubscribe send an email to twisted-leave@python.org https://mail.python.org/mailman3/lists/twisted.python.org/ Message archived at https://mail.python.org/archives/list/twisted@python.org/message/TTCD2T4EF5I... Code of Conduct: https://twisted.org/conduct
Twisted mailing list -- twisted@python.org To unsubscribe send an email to twisted-leave@python.org https://mail.python.org/mailman3/lists/twisted.python.org/ Message archived at https://mail.python.org/archives/list/twisted@python.org/message/YHU7XW4NDSP... Code of Conduct: https://twisted.org/conduct
-- Itamar Turner-Trauring