Hi,
So, speaking for myself here and not representing the Twisted community or anyone else.
I think that the consensus inside the Twisted contributors is that we should have a new release ASAP.
The current release is blocked by the following issues:
* A release process protocol / procedure / communication
-------
For the blocker bug, there were 2 PR there were closed
We can wait one more week to see if this issue can be fixed and unblock the release in this way.
Otherwise, we can revert the change that introduced the regression and have the release unblocked.
Note that reverting a merge that introduced a regression as soon as the regression is detected, is the current best practice.
The revert was not done as there was hope that this can be fixed.
With the release unblock Craig or I or someone else can create the release branch and push the release candidate to PYPI.
-------
For the release procedure / communication
The release documentation and the process to publish the wheels to PyPI was updated with the goal of making it easier for the current release
to happen.
You just create a tag and you have the documentation and PyPI wheels already published.
You can still manually create the wheels and publish them with twine
If anyone thinks that the current changes that were made for automatic Docs (narrative and API) and wheel publishing are a regression,
they can be reverted at any time, and we can merge them after the release.
The ad-hoc / informal Twisted dev communication happens over IRC Freenode #twisted-dev
It would be nice if we can have all active developers there for quick feedback and brainstorming.
------------
Have I forgotten anything?
I hope that in 2 weeks we can have a release candidate and by the end of February a final release.
Cheers