Hi, The release notes of Django 5.0 state: "Third-party library support for older version of Django¶
Following the release of Django 5.0, we suggest that third-party app authors drop support for all versions of Django prior to 4.2. At that time, you should be able to run your package’s tests using python -Wd so that deprecation warnings appear. After making the deprecation warning fixes, your app should be compatible with Django 5.0." However, Django 3.2 is supported until April 2024. Would it not be recommendable for third-party packages to support Django 3.2 as well? My proprosal is to remove the above warning entirely from the release notes, or to change the first line to "From April 2024 on, we suggest that ..." Secondly, it would help me if end dates of both mainstream and extended support were set to specific dates. This hold true for all end dates in the release schedule on https://www.djangoproject.com/download/ . For example, the end date of extended for Django 5.1 ends either in December 2025 or per 1st of January 2026, which is not clear to me. I believe this difference to be relevant for organizations scheduling updates. Thanks for considering this, and for the awesome work on making Django better and better! Warm regards, Wim -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/38ace698-489b-4a66-86d6-bb755e932008n%40googlegroups.com.
