Bug 273466

Summary:	Bug reports (public list, freebsd-bugs) does not include all public bug reports
Product:	Services	Reporter:	Graham Perrin <grahamperrin>
Component:	Mailing Lists	Assignee:	postmaster
Status:	Open ---
Severity:	Affects Some People	CC:	doc, philip
Priority:	---	Keywords:	needs-patch, needs-qa
Version:	unspecified
Hardware:	Any
OS:	Any
URL:	https://lists.freebsd.org/archives/freebsd-bugs/

Description Graham Perrin 2023-08-31 02:56:15 UTC

> Bug reports

Public reports not publicly archived at <https://lists.freebsd.org/archives/freebsd-bugs/2023-August/date.html> include: 

bug 273419 
bug 273420 
bug 273421 
bug 273422 
bug 273423 
bug 273424 

bug 273426 
bug 273427 

If not an issue with archiving, then the description of the list is incorrect (too vague).

Comment 1 Philip Paeps freebsd_committer

2023-08-31 04:27:35 UTC

bugs@ only gets the bug reports that are not assigned at creation.  It is not meant to archive every bug report.  That's what Bugzilla is for.

I agree that the mailing list description is a little vague though.

Can you suggest an improvement?

Comment 2 Graham Perrin 2023-08-31 08:27:57 UTC

(In reply to Philip Paeps from comment #1)

Ah, thanks. 

Random pick, one of the reports for which there's a thread in the archive: <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272965>. 

Is the archive strictly representative of reports where, for example, 
'freebsd-bugs (Nobody) <bugs@freebsd.org>' 
is typically the _assignee_ 
and/or less typically a _CC_ at the time of activity?

Comment 3 Philip Paeps freebsd_committer

2023-08-31 08:50:25 UTC

It is strictly an archive of email sent to bugs@FreeBSD.org. :-)

Bugzilla will send bugs there which are not assigned to anyone else when created.  Bugzilla will also send bugs there which have bugs@FreeBSD.org listed in Cc:.

Sometimes (rarely?) people have discussions on the list without involving Bugzilla at all.

(Distressingly often, spammers send spam there.)

Comment 4 Graham Perrin 2023-09-03 21:08:23 UTC

(In reply to Philip Paeps from comment #1)

> … Can you suggest an improvement?

Certainly, I do have some thoughts, I'm allowing some time for them to settle (and gathering other relevant information) before sharing a suggestion. 

Thanks

Comment 5 Graham Perrin 2023-09-03 21:17:20 UTC

(In reply to Philip Paeps from comment #3)

> … Sometimes (rarely?) people have discussions on the list 
> without involving Bugzilla at all. …

First thought: this exclusive approach should be expected, given documentation that describes the option. For example, from <https://www.freebsd.org/fr/support/bugreports/>: 

> … la commande send-pr(1) sur un système FreeBSD, ou en envoyant un 
> courrier électronique à freebsd-bugs@FreeBSD.org. Note: 
> Nous encourageons l’utilisation de send-pr …

Translated (partly by Google): 

> … the send-pr(1) command on a FreeBSD system, or by sending an email to 
> freebsd-bugs@freebsd.org. Note: We encourage the use of send-pr ... 

Archaic, but not linked from within the page: <https://man.freebsd.org/cgi/man.cgi?query=send-pr&sektion=1&manpath=FreeBSD+10.0-RELEASE>, and so on.