Bug reports which are unanswered by maintainers stay this way for a very long time. Could you add "Maintainer Timeout" flag on bugs? Ideally Bugzilla should automatically set this flag after 30 days.
Here are few examples:
Ideally, committers should work off the combined report including all port updates/new ports/maintainer timeout bugs, and they should work in chronological order.
This feature has been (and is) planned, leveraging any existing flags, as flags are exactly about request/response cycles, that all warrant 'timeout' actions being taken.
We'll continue to track this here, thank you for your report
Lower priority until we get Stage 1 (low hanging fruit) issues sorted out
Got here through randomly browsing. Wondering if this can be done now.
Created attachment 190698 [details]
This functionality can be implemented but I need more details first because I am not quite familiar with ports workflow. Also there were some changes since original request.
- Is it still required? I can see named search for Maintainer timeout port reports on main page.
- maintainer-approval "-" value means "rejected", there is no "timeout" state. Should this flag be left out of scope of this change?
- There may be several maintainer-feedback requests. Should script wait for the most recent one to lapse before setting single maintainer-feedback timeout flag or should it replace them with "timeout" flags one by one?
I attached tentative implementation of automation script just in case I drop the ball