On 1/14/21 06:17, Kyle Evans wrote: > On Thu, Sep 10, 2020 at 7:04 PM Glen Barber <g...@freebsd.org> wrote: >> >> Author: gjb >> Date: Fri Sep 11 00:04:23 2020 >> New Revision: 365619 >> URL: https://svnweb.freebsd.org/changeset/base/365619 >> >> Log: >> Rename stable/12 to -STABLE, and bump __FreeBSD_version after >> releng/12.2 had been created. >> > > I had wondered this before, and now I wonder again after a recent > pkgbase discussion about versioning schemes. Why do we rename stable > to -PRERELEASE at all? It's decidedly a (minor) downgrade to try to go > from -PRERELEASE to -RELEASE since anyone that manages to get a > -PRERELEASE build is still along -STABLE.
-PRERELEASE indicates that the stable branch is currently in code freeze in preparation of a release. The expectation here is that whatever you are seeing in the build would end up in an upcoming release (X.Y), unless they were reverted (for -STABLE, they would go to the next release, or X.Y+1, or never, if X.Y is the last release). I believe traditionally we also bump __FreeBSD_version when -STABLE become -PRERELEASE, which typically happens when we enter a code freeze, but more recent -STABLE branches seems to have moved to doing __FreeBSD_version bumps at the time of -BETA, but technically I think we do want to bump __FreeBSD_version as early as we promoted -STABLE to -PRERELEASE to match the hardcoded version number... Cheers,
OpenPGP_signature
Description: OpenPGP digital signature
