Re: python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED
On Fri, 26 May 2017, Brian May wrote:
> Rhonda D'Vine <rhonda@deb.at> writes:
>
> > If the packagers cared about user code (and I think they should), then
> > we would have Django 1.8 in stretch?
>
> I think it is too late for that now.
Did anyone ever talk to the release team about this?
If upgrades from jessie to stretch without 1.8 delete user data,
then there *is* a chance that Django 1.10 will be removed from
stretch nevertheless.
Maybe a combined action, taking maintainers of the most high-profile
Django rdeps and Django itself, could be made to get, with release
team pre-approval and an epoch (which is, as we know, nothing to fear),
Django 1.8 into stretch (and thus restore upgradeability).
If the release team is not willing to do that (yes, we are in a
freeze, but someone, or several someones, fucked up, and this does
look like a way out, especially given that the 1.8 packages are
basically ready *and* well-tested already), the above-mentioned
removal is still hanging as a sword over Django users’ heads.
bye,
//mirabilos
--
Sometimes they [people] care too much: pretty printers [and syntax highligh-
ting, d.A.] mechanically produce pretty output that accentuates irrelevant
detail in the program, which is as sensible as putting all the prepositions
in English text in bold font. -- Rob Pike in "Notes on Programming in C"
Reply to: