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 that the Technical Board schedule additional
support/releases of Django 1.11.
That said, my personal opinion is that both the Python 2 EOL (2020-01)
and the Django 1.11 EOL (2020-04) were set years in advance;
organizations which waited until the last minute to do their upgrades
would simply wait until the last minute again if given an extension,
and be right back in the same problem. There has to be a cutoff date
at some point where we just say "sorry, but if you haven't prioritized
upgrading for years and years, we cannot tie up our open-source
project's resources because of that". And the announced cutoff, which
is in line with previous LTS releases of Django, seems as reasonable
as any other.
> --
> 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-develop...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/f5718ec3-6041-40db-93fd-b7b8b354e64a%40googlegroups.com.