id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
37159	Implement reproducible artifact builds	Jacob Walls	Jacob Walls	"When building Django artifacts, if the build is [https://reproducible-builds.org/ reproducible], then consumers can verify that an artifact was built from the revision it claims to be built from, and releasers can also confirm with each other (or with CI) before publishing.

Florian [https://forum.djangoproject.com/t/adopt-pep-740-digital-attestations-for-django-releases/42460/18 mentioned] on the forum we are likely to want this:

> Independent of whether any attestation might be a good idea or not, the first steps imo are reproducible builds. We might even have them without knowing it (or via slight adjustments only) since all in all we are just packing up some files from a known revision in a tar/zip and we mostly just need to fix timestamps (we don’t have to worry about compiled code etc). This way it is possible to verify the built release by multiple people before publishing. This makes a compromise of an individual machine even less likely/useful. The next step would be to build the release in CI as well providing another verifier for the reproducible build."	Cleanup/optimization	assigned	Packaging	dev	Normal			Charles Roelli	Accepted	0	0	0	0	0	0