Week ending 2025-10-19 (Week 42)
A week with a good mix of triage, reviews, and some doc updates 
. Continued progress on the 
CNA setup, still in the prep stage and moving forward at a careful pace. Also wrapped up the docs update for automatic roadmap generation 
, which should make future releases a bit smoother. Plenty of meetings in between, keeping things coordinated and on track 
.
Triaged
- https://code.djangoproject.com/ticket/23517 - Collect static files in parallel (re-triaged to wontfix)
- https://code.djangoproject.com/ticket/36658 - Invalid numeric literal in an {% if %} tag is treated as a variable (wontfix)
- https://code.djangoproject.com/ticket/36665 - Rewrite reference to model manager usage to avoid saying “tricky” (accepted)
- https://code.djangoproject.com/ticket/36622 - FileField.init is triggering storage LazyObject resolution at boot time (accepted)
- https://code.djangoproject.com/ticket/36666 - Drop support for MySQL 8.0 (duplicate)
- https://code.djangoproject.com/ticket/36671 - Drop support for SQLite < 3.37.0. (accepted)
- https://code.djangoproject.com/ticket/36670 - Admin filter_vertical widget selector chooser has incorrect background color (accepted)
Reviewed
- https://github.com/django/deps/pull/100 - Add django command
- https://github.com/django/django/pull/19945 - Fixed #36660 – Fixed a regression in descending Index local field checks.
- https://github.com/django/django/pull/19884 - Fixed #36611, Refs #36580 – Added system check for multicolumn ForeignObjects in Meta.indexes/constraints/unique_together.
- https://github.com/django/django/pull/19950 - Pinned “New contributor” GitHub action to v1.
- https://github.com/django/django/pull/19951 - Fixed #36660 – Regression in descending Index local field checks; ad…
- https://github.com/django/django/pull/19915 - Removed advice to only upload wheels for pre-releases.
- https://github.com/django/django/pull/19953 - Removed setuptools from contributor docs and GitHub actions.
- https://github.com/django/django/pull/19955 - Fixed #36648, Refs #33772 – Accounted for specifying pk fields individually in first()/last() when aggregating.
- https://github.com/django/django/pull/19944 - Fixed #36658 – Raised TemplateSyntaxError for invalid numeric litera…
- https://github.com/django/django/pull/19938 - Fixed #36622 – Prevented LazyObject FileField storages from evaluating at boot time.
- https://github.com/django/django/pull/19968 - Bumped isort to 7.0.0.
Authored
- https://github.com/django/django/pull/19952 - Added notes about automatic roadmap generation for next version in docs/internals/howto-release-django.txt.
- https://github.com/nessita/checklist-generator/pull/21 - Update security checklist to use CNA capabilities.
- https://github.com/nessita/checklist-generator/pull/22 - Provide release checklist links in the admin and on the main site.
Other/Misc
- Monthly Ops call.
- Code of Conduct check-in.
- Fellows weekly sync.
- Attended DSF Office Hours.
- Discourse setup creating the new Packages categories and setting up moderators for it.
, an important step toward the final 6.0 milestone.
. Then, the usual: plenty of coordination, a few rabbit holes, but good progress overall 
). A nice milestone on the side: the DSF was confirmed as an official PyPI organization, which makes Django’s package ownership story cleaner and more robust, and less tied to individual accounts 
. The rest was the usual mix of triage, reviews, and a bit of debugging, but the week was definitely security-heavy overall 
.
. The flow of incoming security reports keeps growing 
, and even when many are medium to low impact, keeping up is starting to get tough: most of my time went into security report triage, patch review, and planning so we can (try to) stay on top of things. I also pushed forward the Django 6.0 RC1 release and wrapped up a few small docs and tooling updates 
.
draft. Busy enough, even if it does not look dramatic 
on paper 
.
This week was also heavy on meetings and coordinations. 
was unblocking a few regressions and handling a grab bag of reviews and security follow-ups. Also, a nice change of pace occurred with some community-facing work around the Django 6.0 release. Looking ahead, I will be less available during the second half of December 
, though I will still be around keeping an eye on the essentials 
.
I had limited availability thanks to a trip to a very beach-y location, with plenty of sun, heat, and outdoor time. 
.
I focused on clearing release blockers and final prep for the Jan 6 release. Also I prioritized unblocking urgent items and closing loose ends 
so things are in good shape heading into a short holiday break.