Package: python-django Version: 1.7.11-1+deb8u2 Severity: normal Tags: patch
As has been discussed extensively, update of python-django to a new major/ minor version can have substantial impacts on other packages and system upgradability. It would be helpful to have the policy for updates documented so that maintainers of Django related packages know what to expect. Please see the attached patch for a suggested first draft. Scott K
diff -Nru python-django-1.11.1/debian/changelog python-django-1.11.1/debian/changelog --- python-django-1.11.1/debian/changelog 2017-05-06 14:32:33.000000000 -0400 +++ python-django-1.11.1/debian/changelog 2017-05-27 17:01:23.000000000 -0400 @@ -1,3 +1,9 @@ +python-django (1:1.11.1-4) UNRELEASED; urgency=medium + + * Add considerations for version upgrades to README.Source + + -- Scott Kitterman <sc...@kitterman.com> Sat, 27 May 2017 17:00:44 -0400 + python-django (1:1.11.1-3) experimental; urgency=medium * Really add Build-Depends on libgdal-dev. diff -Nru python-django-1.11.1/debian/README.source python-django-1.11.1/debian/README.source --- python-django-1.11.1/debian/README.source 2017-05-06 14:32:33.000000000 -0400 +++ python-django-1.11.1/debian/README.source 2017-05-27 17:00:31.000000000 -0400 @@ -1,3 +1,26 @@ +Introduction of new Django versions to Unstable +----------------------------------------------- + +The upstream Django project only supports API compatibility between its Long +Term Support (LTS) releases. In order to support user upgrades in Debian, the +python-django package in Unstable/Testing must not skip an LTS release from +the current Debian Stable version. + +As a result, only LTS releases should be uploaded to Unstable/Testing. +Non-LTS releases should be uploaded to Experimental to allow maintainers of +reverse-depends to test and update their packages with the newer releases to +ease preparation for transition to the next LTS release. + +Update of python-django in Unstable to a new major/minor version should be +coordinated with maintainers of reverse-depends, much like a library +transition is handled. Micro version updates do not require coordination. + +If there is a newer LTS release available in Testing, it will often be +backported to the current stable release. Keeping the upgrade path clean for +an LTS to LTS upgrade when then next Debian release occurs will also make +updates to the stable backport possible without needing explicit additional +coordination with the Backports team. + Git packaging rules for python-django -------------------------------------
