On Mon, Dec 28, 2020 at 6:13 AM Adi Roiban <adi@roiban.ro> wrote:
I plan to update the release documentation to make it clear that all release blocker tichet should have an owner and there are plans to fix the ticket in a maximum of 2 weeks.
Otherwise we risk to block the release forever... and if we delay forever people will start using "trunk" and if everybody is using trunk, what is the point of a release :) ?
Part of the point is that when someone runs `pip install ...` they get a *working* version of Twisted, to the best of the project's ability to provide one.
Fortunately many regressions aren't that difficult to resolve. At worst, find the merge that introduced them and revert it. This works best when regressions are found in a timely manner, of course. Of course it's also nice if the problem can be fixed without backing out whatever (presumably desirable) set of changes it came along with.
Part of the release managers job is to motivate this kind of work to happen. A standing policy to revert the cause of a regression can also serve as good motivation to get the other kind of fix in, too.
It's better if these known regressions don't linger for months, though. It looks like the Buildbot PR had a failing CI run in October. I'd suggest that not waiting until December is a good way to avoid having these kinds of situations turn into a larger problem.
Jean-Paul
Thanks Kyle and Jean-Paul for your feedback.
I guess there are no comments against removing a ticket from the release-blocking list if the ticket is not active for 1 or 2 weeks.
Commenting against this was the main reason for my earlier reply. I've left my quoted reply above. Jean-Paul