freebsd-skq/RELNOTES

Release notes for FreeBSD 14.0.

This file describes new user-visible features, changes and updates relevant to
users of binary FreeBSD releases.  Each entry should describe the change in no
more than several sentences and should reference manual pages where an
interested user can find more information.  Entries should wrap after 80
columns.  Each entry should begin with one or more commit IDs on one line,
specified as a comma separated list and/or range, followed by a colon and a
newline.  Entries should be separated by a newline.

Changes to this file should not be MFCed.

76681661be28
	Remove support for asymmetric cryptographic operations from
	the kernel open cryptographic framework (OCF).
Bump CURRENT to 14.0 This one goes to 14. Approved by: re (implicit) Sponsored by: Rubicon Communications, LLC ("Netgate") 2021-01-22 00:10:07 +00:00			`Release notes for FreeBSD 14.0.`
Add an initial RELNOTES file. The intent is to provide a convenient location to document changes that are relevant to users of binary FreeBSD distributions, in contrast with UPDATING, which exists to document caveats for users who build FreeBSD from source. This complements the "Relnotes:" tag in commit messages by providing a place to document the change in more detail, or in case a "Relnotes:" tag was accidentally omitted. In particular, "Relnotes:" should be used if you do not intend to document the change in RELNOTES for some reason. Changes to the file should not be MFCed. For now the file will exist only in head, but may be updated via direct commits to stable branches depending on how things go. I took the liberty of pre-populating the file with some recent release notes-worthy changes. Reviewed by: ian (earlier version) Discussed with: cy, gjb, imp, rgrimes Differential Revision: https://reviews.freebsd.org/D20762 2019-07-17 19:09:05 +00:00
			`This file describes new user-visible features, changes and updates relevant to`
			`users of binary FreeBSD releases. Each entry should describe the change in no`
			`more than several sentences and should reference manual pages where an`
			`interested user can find more information. Entries should wrap after 80`
			`columns. Each entry should begin with one or more commit IDs on one line,`
			`specified as a comma separated list and/or range, followed by a colon and a`
			`newline. Entries should be separated by a newline.`

			`Changes to this file should not be MFCed.`

RELNOTES: Document removal of asym crypto from OCF. Sponsored by: Chelsio Communications 2021-04-12 21:34:23 +00:00			`76681661be28`
Spellcheck. Reported by: 0mp 2021-04-12 22:12:19 +00:00			`Remove support for asymmetric cryptographic operations from`
RELNOTES: Document removal of asym crypto from OCF. Sponsored by: Chelsio Communications 2021-04-12 21:34:23 +00:00			`the kernel open cryptographic framework (OCF).`