Page MenuHomeFreeBSD

Articles/Status: Stop sending reports to developers@ mailing list
AbandonedPublic

Authored by salvadore on Nov 30 2025, 2:22 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Jan 15, 10:05 PM
Unknown Object (File)
Thu, Jan 8, 2:10 PM
Unknown Object (File)
Tue, Jan 6, 6:29 AM
Unknown Object (File)
Thu, Jan 1, 7:05 AM
Unknown Object (File)
Dec 27 2025, 10:04 PM
Unknown Object (File)
Dec 19 2025, 4:16 AM
Unknown Object (File)
Dec 18 2025, 3:08 AM
Unknown Object (File)
Dec 15 2025, 7:09 AM
Subscribers
None

Details

Reviewers
bapt
pi
Group Reviewers
status
Summary

Sending status reports to developers@ in BCC is not possible anymore.
Configuration now requires developers@ to be included in To: or CC:
headers.

The reports are still sent to freebsd-announce@, freebsd-hackers@,
freebsd-stable@, freebsd-current@, and are also available on the FreeBSD
website. Thus, all developers can very easily access status reports even
if no e-mail is sent to developers@.

Then, stop sending reports to developers@ mailing list.

Diff Detail

Repository
R9 FreeBSD doc repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 68940
Build 65823: arc lint + arc unit

Event Timeline

salvadore created this revision.

I have added bapt and pi to the reviewers as postmaster members because the issue probably started with some recent change in developers mailing list configuration. Now they are aware and can have a word about it if they want. But I do not think that the configuration should be changed: I believe stop sending status reports to developers@ is the right solution.

I disagree and fixed the stup of developers@ so now it accepts mails in BCC? if not, please ping me.

bapt requested changes to this revision.Dec 4 2025, 9:02 AM
This revision now requires changes to proceed.Dec 4 2025, 9:02 AM

Calls for status reports sent to developers@ in BCC on the 15th of December have arrived successfully.
So this change is not necessary anymore and I abandon the revision.

Thanks @bapt !