On 19. Dec 2024, at 22:26, Daniel Engberg <daniel.engberg.li...@pyret.net> wrote:


On 2024-12-19T21:33:14.000+01:00, Michael Gmelin <gre...@freebsd.org> wrote:
On Thu, 19 Dec 2024 20:39:54 +0100
Daniel Engberg <daniel.engberg.li...@pyret.net> wrote:

Hi,

While this should be uneventful if possible please try PR 283266 and
report back if you run into any issues and of course success stories
too.


Best regards,

Daniel (diizzy@)


Prior to testing, one question: The bug indicates that the port
maintainer was not involved in these changes - is this true and has it
been resolved in the meantime?

Best
Michael

--
Michael Gmelin
Hi,

There has been no response from the maintainer regarding PRs about this port for over 2 weeks, see PR 283020

This PR was opened on 2024-11-28. You committed a patch mentioning it a week later, so it might very well look like you fixed the problem (which is what I thought at first when seeing it). Apparently that was a reference error (accidental, I assume).

and also the end at the first comment in PR 283266.

The end of the first comment in that PR reads “Cheers Max”.

PR 283266 has yet to reach maintainer timeout.

This PR is eight days old by now and it’s Christmas/Holiday season, so it certainly won’t hit maintainer timeout on Christmas Eve or the holiday week in general. I would say, acting in good faith, maintainer timeout should be delayed by at least one or two additional weeks on this one.

Lining up PRs preparing for a timeout and making a maintainer change part of that, strategically planing ahead to commit the very moment the right number of days has passed, doesn’t seem like an ingenious way of cooperating with your fellow project members to me.

Best
Michael


Reply via email to