Re: [RFC] Introduce semantic versioning 2.0.0 to FreeBSD releases

Hi,

I would prefer staying with what we have ... for consistency.

All the tools/scripts/everything have already been 'taught' to interpret 14.3-RELEASE-p7 format.

Switching *now* after more then 30 years of FreeBSD releases would only cause this: https://xkcd.com/927/

No one wants that confusion.

 ... but I have better idea.

We already have these:

    % sysctl kern | grep -e kern.osrelease -e kern.version    
    kern.osrelease: 14.3-RELEASE-p7
    kern.version: FreeBSD 14.3-RELEASE-p7 GENERIC

Adding additional 'kern.dotrelease' which would be in 0.0.0 format will not hurt anyone - yet you will have your version.

    % sysctl kern | grep -e kern.osrelease -e kern.version    
    kern.osrelease: 14.3-RELEASE-p7
    kern.version: FreeBSD 14.3-RELEASE-p7 GENERIC
    kern.dotrelease: 14.3.7

... and I would also add '-d' flag for freebsd-version(*) to print FreeBSD version in '0.0.0' format.

Regards,
vermaden



Temat: Re: [RFC] Introduce semantic versioning 2.0.0 to FreeBSD releases
Data: 2026-02-25 17:42
Nadawca: "Tomek CEDRO" <[email protected]>
Adresat: "Minsoo Choo" <[email protected]>; 
DW: "freebsd-hackers" <[email protected]>; 

>> On Wed, Feb 25, 2026 at 7:17 AM Minsoo Choo wrote:
>> Currently FreeBSD uses a variant of semantic versioning for releases
(e.g. 15.0-RELEASE-p1) where backward compatibility can be broken (e.g.
deprecation of a utility) in a new major version, new features are added in
minor versions, and security fixes are introduced in a new patch version.
>> (..)
> 
> +1 for simpler numbering like standard major.minor.patch:
> 16.0-RELEASE -> 16.0.0.
> 16.0-RELEASE-p1 -> 16.0.1.
> 16.1-RELEASE -> 16.1.0.
> 16.1-RELEASE-p1 -> 16.1.1.
> 
> X.Y.Z numbering would imply release, maybe 16.0.0-RELEASE for clarity.
> 
> 15-STABLE and 17-CURRENT could be left untouched or something like
> 17.0.20260225-CURRENT to mark snapshot?
> 
> :-)
> 
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info