| 1 |
Introduction of new Django versions to Unstable |
| 2 |
----------------------------------------------- |
| 3 |
|
| 4 |
As a large part of the Django ecosystem is developed and validated against |
| 5 |
LTS versions of Django, we have decided to keep only LTS versions of |
| 6 |
Django in Debian Unstable and Debian Testing. |
| 7 |
|
| 8 |
Non-LTS versions will be made available in Debian Experimental to make it |
| 9 |
easier for everybody to run the last stable release and possibly prepare |
| 10 |
the field for the next LTS release. |
| 11 |
|
| 12 |
Update of python-django in Unstable to a new major/minor version should be |
| 13 |
coordinated with maintainers of reverse-depends, much like a library |
| 14 |
transition is handled. Micro version updates do not require coordination. |
| 15 |
|
| 16 |
Requirements for Django reverse dependencies |
| 17 |
-------------------------------------------- |
| 18 |
|
| 19 |
To make Django transitions easier, all Django reverse dependencies should |
| 20 |
ensure that they are running with the current LTS version without |
| 21 |
generating any deprecation warning: |
| 22 |
https://docs.djangoproject.com/en/dev/internals/release-process/#internal-release-deprecation-policy |
| 23 |
https://docs.djangoproject.com/en/dev/howto/upgrade-version/#resolving-deprecation-warnings |
| 24 |
|
| 25 |
This can be ensured for example by running tests with "python3 -W error" |
| 26 |
(which will make the tests fails when such a warning is emitted) although |
| 27 |
you will most likely also need some other -W flags to ignore legitimate |
| 28 |
warnings which are unrelated to Django (ex: “-W ignore:::site:“). Another |
| 29 |
approach is to use “-W all” to print all the generated warnings without |
| 30 |
actually failing. |
| 31 |
|
| 32 |
Usage of “-W error” is forbidden in a package build, but it could be used |
| 33 |
in an autopkgtest (DEP-8) test. Even in that case, it is advised to only |
| 34 |
run tests with “-W error” when you detect that you are running against the |
| 35 |
Django LTS version that you are supporting (so that autopkgtests do not |
| 36 |
immediately fail when they are run against a newer Django version). |