#36563: Adopt PEP 740 attestations for Django release files on PyPI
-------------------------------------+-------------------------------------
Reporter: JaeHyuckSa | Owner: (none)
Type: New feature | Status: closed
Component: Packaging | Version: dev
Severity: Normal | Resolution: wontfix
Keywords: PEP740, PyPI, | Triage Stage:
provenance, attestations, | Unreviewed
release-process |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* resolution: => wontfix
* status: new => closed
Comment:
Hello JaeHyuckSa, thank you for the ticket and the forum post
conversation. As mentioned there, this is far from trivial and warrants a
much deeper conversation since, currently, releases are performed with a
fully manual procedure (see docs:
https://docs.djangoproject.com/en/dev/internals/howto-release-django/)
I'll close as `wontfix` following the documented triage procedure.
--
Ticket URL: <https://code.djangoproject.com/ticket/36563#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070198ccc5856d-5652a66e-52ee-48eb-ac63-005a84f8b5f2-000000%40eu-central-1.amazonses.com.
