I don't object to the final release being in April instead of January, though I'm not sure that the additional release really means we need to do that.  But FWIW I'm in favor of Option 3 / calling 19.4 the final release.  :-)

  My sense is that there was consensus on hawkowl's proposal except for, I think:

1- Should we drop the idea of a 2.7 maintenance branch?
2- It seems we need to fix the bug in twisted.names first.
3- Choosing a final 2.7 release date.

-wsv


On Dec 11, 2019, at 1:16 PM, Jean-Paul Calderone <exarkun@twistedmatrix.com> wrote:

On Wed, Dec 11, 2019 at 4:06 PM Wilfredo Sánchez Vega <wsanchez@wsanchez.net> wrote:
  With Python 2.7 support dropping in a matter of weeks, I'd like to pick up from hawkowl's thread back in March about Python 2.7 support for Twisted.

Despite the widely circulated January 1 2020 date, it seems that python-dev nevertheless plans to make a Python 2.7 release in April 2020 - https://www.python.org/dev/peps/pep-0373/

This is not to say the questions here don't need answering or that there isn't some urgency at this point, but it seems like the January 1 date is essentially an arbitrary deadline without a clear connection to the support status of CPython 2.7.

Or does anyone know a different way to reconcile these apparently conflicting dates?

Jean-Paul