I am also +1 on the technical side, but I share (and thank) Carlton’s concern about timing. Feature Freeze is Sept 17, which is already tight. To make it more challenging:
- Our top priority is Jacob starting on Aug 25
, so we will have onboarding to do which takes time. - Our second priority is a security release (to be announced next week) happening Sept 3, and we hope to pair with Jacob on that for training, so the release will be inherently more involved.
- Sarah will be semi-available the first two weeks of September due to travel.
- DjangoCon US is Sept 8-12, and I will be attending and out Sept 5-12. I believe Jacob may also be attending, which is amazing, but it means less/no review capacity.
- We already have a committed backlog of new features to shepherd, including CSP decorators, Django tasks, and, less “featury” but equally relevant, a new shiny docs extra linter.
- And then there are the requests we got months ago in the 6.0 dedicated forum post.
All of that plays against the odds of us taking this comfortably before freeze. So, if the patch is really as small and self-contained as Tim says, we can aim for it, but expectations should be realistic. Otherwise, it might be better to land early in the 6.1 cycle rather than rush it now.
As 6.0 release manager I will do my best here and keep folks posted. In the meantime, if anyone would like to help with pending 6.0 items, the tickets raised by David and Adam in the post linked above could use some reviews, and that would certainly help.
Lastly, no PR really takes just a few minutes to review. Maybe typo fixes come close, but even those can take longer once you account for docs building and manual checks. A change like this will require hours, if not days, to include proper manual testing and docs adjustments. It would be great if the time needed for review work was not minimized. I don’t feel comfortable landing changes that I haven’t perused consciously.