Yes, there are blockers: I still have to merge the introduction, which references the status reports instructions that I am updating, and I need to check all reports with vale. Hopefully I should be able to do all of these within the next 24 hours.

Approved once the listed issues are fixed, thanks!

Approved once the minor issues listed are fixed, thanks!

Approved, thanks!

Approved, thanks!

A few minor changes and it is ready to merge.
Thanks for your report!

A few changes and it is ready to merge. Thanks for your report!

Approved, thanks!

A few small fixes and it is ready to merge.
Thanks!

In D53824#1242870, @salvadore wrote:

Another case in which using variables in WWW makes sense is for master/slave ports or ports that are very similar (e.g. the GCC ports, which do not follow the master/slave model at least for now, but have indeed very similar Makefiles). Assume for example software foo comes in different versions and we want to point WWW to different urls depending on those versions, we could do something like WWW= https://foo.com/${DISTVERSION}.

Since I have been put in the reviewers, let me add my two cents.

Approved, thanks!

A few small fixes and it is ready to merge.
Thanks for you report!

A few small changes and it is ready for merge. The report also needs to have one sentence per line (I can do it at merge time if you prefer).
Thanks!

A few small changes and it is ready for merge. The report also needs to have one sentence per line (I can do it at merge time if you prefer).
Thanks!

Approved, thanks!

Approved, thanks!

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.

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.

Revision's link and revision's author referenced in the mailing list: https://lists.freebsd.org/archives/dev-commits-doc-all/2025-November/004816.html

Merged with changes as https://cgit.freebsd.org/doc/commit/?id=ecd8cc0702da9d3fff4c8b18d2c9236d48cdea83 (forgot to put it in the commit message, sorry)