Thank you all. I am mostly concerned about a possible widespread security
issue. Hopefully, this is only paranoia on my part. While I'll look out for
Adam's "maybe" ;) in such an event, I'll also look into the links Adam
shared in case we need to backport any fixes ourselves.
I appreciate the r
Personally, I'm counting the days and I'm against extending support of
Django 1.11, just 1 day remaining.
Best,
Mariusz
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and s
I agree with James, the cutoff date has been more than reasonable.
Also, if there aren't any show-stopping bugs you know about, asking for the
extension of the EOL "by a few weeks" doesn't really mean much. If we were
past the cutoff date, and a high impact, wide reaching bug was found - yes,
mayb
The end of support simply means there will be no further releases, and
any showstopping bugs reported will not be fixed. It doesn't mean
Django itself will stop working. Also, the decision is in the hands of
the Technical Board, not the Django Fellows, so the correct process
would be to request tha
Mariusz,
Thank you for your response.
Would it be possible for the Django Fellows to vote to extend Django 1.11's
EOL by a few weeks? For those of us with a large Django codebase, we were
bitten by the onerous Python 2->3 upgrade and so the start of our Django
upgrade was delayed by several wee
No, support of Django 1.11 ends on 1st April.
Best,
Mariusz
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-develo
