Hi, I would like to report a possible type in /usr/src/RELNOTES, the reported version is 13.0 and I believe should read 13.2. When downloading v13.2 with git clone -b releng/13.2 --depth 1 https://git.freebsd.org/src.git /usr/src/RELNOTES reads at the top: root@mail:/usr/src # more RELNOTES Release notes for FreeBSD 13.0. This file describes new user-visible features, changes and updates relevant to ... The source code does compile and install 13.2: root@mail:~ # uname -a FreeBSD mail.bio.fsu.edu 13.2-RELEASE-p2 FreeBSD 13.2-RELEASE-p2 releng/13.2-4341433a6 MAIL amd64 Also I'd like to thank you guys for FreeBSD. I've been using it since 1996 and it currently supports over 2 petabytes of data here at FSU Biology, our mail server and web servers, and backup servers. Thanks, Alex
From initial <https://github.com/freebsd/freebsd-src/commit/8dbc2b6e026e930c119ef02f8217fad629e92f12> by markj@: > The intent is to provide a convenient location to document changes > that are relevant to users of binary FreeBSD distributions, in contrast > with UPDATING, … ---- ^Triage: * request feedback from the initial committer * see also: URL of the review for the above * URL for RELNOTES on the releng/13.2 branch, with 13.0 in line 1 * change status, product, and component * component conf, based on conf for comparable bug 274502 * remove doc@ from the CC list.
I think this is a task for re@. Every time a new minor branch is created, the version number should be bumped. I think re@ maintains a checklist for new branch creation, either it should include a note to bump the version, or we should simply remove the version number from RELNOTES. For instance, the version in main should also be updated to say "FreeBSD 15.0". Either option seems ok to me.