The ports bugzilla policy is that PRs are not to be submitted to "helpfully" tell maintainers and/or ports@ mailing list that new versions are available. Yet Kevin Thompson has notified me that the PR documentation says exactly the opposite, and I confirmed it:
Some cases where it may be appropriate to submit a problem report about something that is not a bug are:
* Notification of updates to externally maintained software (such as ports or software in the contrib/ directory).
Please remove this line immediately. It reflects exactly opposite of what is acceptable for a ports PR.
In addition to removal of that line, I would suggest that the third line:
If the port is maintained, PRs announcing new upstream releases are usually not very useful since they generate supplementary work for the committers, and the maintainer likely knows already there is a new version, they have probably worked with the developers on it, they are probably testing to see there is no regression, etc.
be reworded to say that portscout makes announcement of updates unnecessary, but submitting patches to update ports instead of just announcing the update is welcome.
bugzilla has been in operation for several months, yet this obsolete "When to Submit a Problem Report" documentation has not been updated since GNATS times.
It's very visible page. I would think it would be pretty high priority to update this. Is bugmeister or somebody else working on it already?
Pending review/approval: https://reviews.freebsd.org/D2092
(In reply to Allan Jude from comment #3)
(commenting here since reviews.freebsd.org is read-only to me)
It is not obvious to newcomers what "software in the contrib/ directory" is. Rather than:
<para>When submitting a PR about externally maintained software
(such as ports or software in the contrib/ directory) consider
<para>When submitting a PR about software not written by FreeBSD
contributors, consider the following:</para>
I don't think that sentence needs much more clarification than that since the section below outlines the difference between things in base that are native, things in base that are contributed, and things in ports.
The paragraph on portscout doesn't seem to flow well, and I would suggest this:
<para>If the port is maintained, PRs announcing new upstream
releases are usually not very helpful since maintainers
are automatically notified by <application>portscout</application>,
which automatically tracks new versions of applications, and so
a PR would only create supplementary work for the committers.</para>
A commit references this bug:
Date: Sun Mar 22 19:28:19 UTC 2015
New revision: 46364
Update PR article to ask people not to submit PRs about outdated ports
Differential Revision: https://reviews.freebsd.org/D2092
Submitted by: marino (original)
Reviewed by: wblock, Andrew Berg (earlier version)
Approved by: bcr (mentor)
Sponsored by: ScaleEngine Inc.