[Python-modules-commits] [python-django] 02/03: Document a minimal Django packaging policy in README.Django-packaging-policy. Closes: #863514

[Raphaël Hertzog]

This is an automated email from the git hooks/post-receive script.

hertzog pushed a commit to branch debian/experimental
in repository python-django.

commit ded34befcb0ed3084fb046b0abf44f5977aba2f4
Author: Raphaël Hertzog <hertzog at debian.org>
Date:   Tue May 30 15:57:56 2017 +0200

    Document a minimal Django packaging policy in README.Django-packaging-policy. Closes: #863514
---
 debian/README.Django-packaging-policy | 36 +++++++++++++++++++++++++++++++++++
 debian/changelog                      |  2 ++
 debian/python-django.docs             |  1 +
 3 files changed, 39 insertions(+)

diff --git a/debian/README.Django-packaging-policy b/debian/README.Django-packaging-policy
new file mode 100644
index 0000000..e79a1e4
--- /dev/null
+++ b/debian/README.Django-packaging-policy
@@ -0,0 +1,36 @@
+Introduction of new Django versions to Unstable
+-----------------------------------------------
+
+As a large part of the Django ecosystem is developed and validated against
+LTS versions of Django, we have decided to keep only LTS versions of
+Django in Debian Unstable and Debian Testing.
+
+Non-LTS versions will be made available in Debian Experimental to make it
+easier for everybody to run the last stable release and possibly prepare
+the field for 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.
+
+Requirements for Django reverse dependencies
+--------------------------------------------
+
+To make Django transitions easier, all Django reverse dependencies should
+ensure that they are running with the current LTS version without
+generating any deprecation warning:
+https://docs.djangoproject.com/en/dev/internals/release-process/#internal-release-deprecation-policy
+https://docs.djangoproject.com/en/dev/howto/upgrade-version/#resolving-deprecation-warnings
+
+This can be ensured for example by running tests with "python3 -W error"
+(which will make the tests fails when such a warning is emitted) although
+you will most likely also need some other -W flags to ignore legitimate
+warnings which are unrelated to Django (ex: “-W ignore:::site:“). Another
+approach is to use “-W all” to print all the generated warnings without
+actually failing.
+
+Usage of “-W error” is forbidden in a package build, but it could be used
+in an autopkgtest (DEP-8) test. Even in that case, it is advised to only
+run tests with “-W errro” when you detect that you are running against the
+Django LTS version that you are supporting (so that autopkgtests do not
+immediately fail when they are run against a newer Django version).
diff --git a/debian/changelog b/debian/changelog
index e84b333..114e77a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,8 @@
 python-django (1:1.11.1-4) UNRELEASED; urgency=medium
 
   * Update README.source and debian/gbp.conf.
+  * Document a minimal Django packaging policy in
+    README.Django-packaging-policy. Closes: #863514
 
  -- Raphaël Hertzog <hertzog at debian.org>  Tue, 30 May 2017 14:42:53 +0200
 
diff --git a/debian/python-django.docs b/debian/python-django.docs
index 24948f1..8690f97 100644
--- a/debian/python-django.docs
+++ b/debian/python-django.docs
@@ -1,2 +1,3 @@
 AUTHORS
 README.rst
+debian/README.Django-packaging-policy

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/python-modules/packages/python-django.git