#36922: Commit 787cc96e is reachable from main but not 6.0.2
-------------------------------------+-------------------------------------
Reporter: Julien Palard | Owner: (none)
Type: Bug | Status: closed
Component: Database layer | Version: 6.0
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* cc: Jacob Walls (added)
* resolution: => needsinfo
* status: new => closed
Comment:
Hello Julien, thank you for your ticket. The commit you reference was
merged into `main` after the 6.0 feature freeze (this is when the
`stable/6.0.x` branch is cut), that's why the commit is not there. Now,
whether this commit should have been backported, that's another question.
In the PR, Jacob explicitly said:
> Not certain whether to suggest a 6.0 backport. Nothing is broken per se,
it's just two examples falling outside the doc'd pattern we updated to.
Can you please provide more details about your use case and how your
project is affected? Please reopen the ticket when doing so. Thank you!
--
Ticket URL: <https://code.djangoproject.com/ticket/36922#comment:2>
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/0107019c51b29f4f-15c0e4d9-0505-4819-b19b-340a535a95b8-000000%40eu-central-1.amazonses.com.
