Hello, On 05/24/2017 02:06 PM, Thorsten Glaser wrote: > On Wed, 24 May 2017, Alexander Wirt wrote: > >> The policy is pretty clear. Backporting 1.10 and backport the other packages >> too. >> >> It is maybe a problem and maybe we should get the policy changed - I >> personally don't think too. I don't wan't software that isn't in testing in >> backports - but doing it behinds our back is not an option. > > This really sounds like we want to have two separate repositories.
An alternative idea would be to have two separate (source) packages in sid: django and django-lts. Then django-lts could be put into backports and so maintained according to the backport policy. Maybe it should be named django-lts1.8 just in case a new upstream LTS should be packaged but the former should stay in testing and backports. Best regards Uwe
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Python-modules-team mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
