PRs are being closed for bogus reasons :-(

[Brooks Davis]

On Fri, Jun 01, 2018 at 11:23:48AM -0700, Conrad Meyer wrote:
> On Fri, Jun 1, 2018 at 2:09 AM, Andrey V. Elsukov <bu7cher at yandex.ru> wrote:
> > On 01.06.2018 00:02, Mark Linimon wrote:
> >> I'd like to see us do a lot better at dealing with "PRs with patches" --
> >> even more so than "can't get FreeBSD to run" -- but without some kind
> >> of set of new volunteers willing to work on only such issues, it simply
> >> isn't going to happen.
> >
> > I suggest to forcibly subscribe any committers to the freebsd-bugs@
> > mailing list in addition to *-committers at . :)
> 
> Hi Andrey,
> 
> Maybe this proposal was made in jest, but I actually like the idea.
> The dominant noise of freebsd-bugs@ comes from follow-up comments, bug
> status notifications (sometimes bulk changes made by e.g., Eitan), or
> direct email reply discussion (not really sure why bugs@ isn't just
> treated as announce-only).
> 
> It's still sort of a firehose if you *just* receive new bug reports,
> but it's much more manageable and you can click through any that look
> interesting and mark the rest read with no risk of future
> notification.

+1

I did a bit of triage while skimming the resets Eitan did and while I
didn't find much actionable I was able to close some things properly.

-- Brooks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20180601/fe556aa8/attachment.sig>