Page MenuHomeFreeBSD

14.4/relnotes: Doc section is going to be updated
ClosedPublic

Authored by vladlen on Mon, Mar 2, 5:40 PM.
Tags
Referenced Files
Unknown Object (File)
Mon, Mar 23, 10:17 AM
Unknown Object (File)
Mon, Mar 23, 5:59 AM
Unknown Object (File)
Thu, Mar 19, 12:42 AM
Unknown Object (File)
Mon, Mar 16, 5:00 PM
Unknown Object (File)
Mon, Mar 16, 12:41 PM
Unknown Object (File)
Sat, Mar 7, 3:45 PM
Unknown Object (File)
Fri, Mar 6, 1:01 PM
Unknown Object (File)
Thu, Mar 5, 9:04 PM
Subscribers
None

Details

Summary

This is the last section in the Relnotes preparation process. I checked the commits with man page changes and selected (in my opinion):

changes in man pages that are important for users

documentation of previously undocumented features or commands

man pages about new hardware, if they are not already covered in other sections

Additions of all entirely new man pages are not included — otherwise it would look too much like a changelog.

I would really appreciate a review: should this information be added? The man section was the hardest part for me to decide on.

The section "Ports Collection and Package Infrastructure" is still empty. I didn’t find any commits in releng/14.4 related to user-visible changes in this area — only internal build structure changes — and there was nothing in the status reports about this topic either.

It would also be good to have some content for the section "General Notes Regarding Future FreeBSD Releases", but I don’t see any proposals so far.

The last step will be to remove empty sections ("Ports Collection and Package Infrastructure" and "General Notes Regarding Future FreeBSD Releases" for now) before the release.

Diff Detail

Repository
R9 FreeBSD doc repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

vladlen created this revision.

I like this section because I primarily work on the manpages project, so showing it has activity is very appreciated to me. I would organize them by section number, then alphabetically, but I can do that! Thank you so much for doing this!

This revision is now accepted and ready to land.Mon, Mar 2, 6:24 PM

Once you commit this I'll add some more.

This revision was automatically updated to reflect the committed changes.

Once you commit this I'll add some more.

I sorted all man records and commited.

I have doubt about man:dtrace_fbt[4]. I considered it important for users in my first round of selection, but in the final result set it looks different from other records (it could be important for developers).
dtrace also is in the next commits:
04bb91e9c5f73bf6637a5cdb0840363e926d85df The commit adds a new manual page man:dtrace_vfs[4] documenting the DTrace vfs provider.
ff6b04c37e780e070d871dff60370a0376efde4c The DTrace PID provider man page man:dtrace_pid[4] is added, documenting its usage and options.
f69bf8f994e56104fb42abdce169ed3841ac63c9 The DTrace priv provider is documented in man:dtrace_priv[4], describing static tracing for privilege checking.
7d43404485bf2e306e54bdfdb0ae937d6921df39 Adds man:dtrace_callout_execute[4] manual page documenting the DTrace callout_execute provider.

Maybe make the list of all added providers in one record?