Conversation
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
Conflicts have been resolved. A maintainer will review the pull request shortly. |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
Conflicts have been resolved. A maintainer will review the pull request shortly. |
kiblik
force-pushed
the
django_6.0
branch
2 times, most recently
from
20382cc to
138543a
Compare
github-actions
bot
added
the
settings_changes
|
Waiting for django-commons/django-prometheus#489 |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
Signed-off-by: kiblik <5609770+kiblik@users.noreply.github.com>
|
Conflicts have been resolved. A maintainer will review the pull request shortly. |
|
Although it's interesting to prepare for Django 6.0 compatibility, I think we should sit on this for a bit. Django 5.2 is an LTS release with a long support horizon, longer than 6.0. If we make it work for 6.0 but it breaks in 6.1 and we have to wait for some library to fix it we may get in trouble. TL;DR; Let's re-assess after the summer when 6.1 is available. |
2 participants
TBD