#35980: Make Django release artifacts PEP 625 compliant
-------------------------------------+-------------------------------------
Reporter: Sarah Boyce | Owner: Natalia
Type: | Bidart
Cleanup/optimization | Status: assigned
Component: Packaging | Version: 5.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Natalia <124304+nessita@…>):
In [changeset:"234478764c5d85fb2e1934082af91a60fa83476d" 2344787]:
{{{#!CommitTicketReference repository=""
revision="234478764c5d85fb2e1934082af91a60fa83476d"
[5.2.x] Refs #35980 -- Updated internal docs for artifact upload and
release via admin site.
Recent updates to djangoproject.com extended the `Release` model to
support uploading and storing artifacts and checksum files. This branch
updates the "How to release Django" docs to match the new release flow.
Backport of 08dae5bd46a02a2e2798028c83d97b1894beffb8 from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35980#comment:17>
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/01070195abf93cc2-8b5bd1ac-02c2-4164-a1f9-af2d1b74e7e5-000000%40eu-central-1.amazonses.com.
