FreeBSD release engineering

grahamperrin

grahamperrin

 
The FreeBSD Project | FreeBSD Release Engineering

grahamperrin said:
13.1-RELEASE estimated some time in early 2022 at <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255979#c17>.

<https://www.freebsd.org/releases/13.1R/schedule/> for an official release schedule does not yet exist.
Click to expand...

SirDice said:
release schedule is that there's a release every 6 months. FreeBSD 12.3 is up next, that will be released some time in December. FreeBSD 13.1 will follow about 6 months after that. Then 12.4 6 months after that, etc. So you can make an educated guess that 13.1 will come some time in June/July 2022.
Click to expand...

Thanks, maybe six months is a basis for something else.

11.4 was released around two months after 13.0, and so on, and (unless I'm missing something) I see nothing relating to six months or biannual at the release engineering page above.

Release Information | The FreeBSD Project

FreeBSD Patch Level Table (parsed) at <https://bokut.in/>
 
Nick C said:
… freebsd-update … warning about 13.0-RELEASE approaching end-of-life. There is no EoL for 13.0-RELEASE yet.
Click to expand...

Thanks Nick C and drr

I guess that <https://www.freebsd.org/releases/13.1R/schedule/> and <https://cgit.freebsd.org/src/log/?h=releng/13.1> will appear before too long.

Postscripts

<https://lists.freebsd.org/archives/freebsd-questions/2022-January/000591.html>

… The freebsd-update metadata includes the EoL, so it's initially populated with the projected EoL and gets adjusted when the next release's schedule is released. I'm trying to see if we can instead initially populate it with the branch EoL and adjust it to be closer once the new schedule is released -- in theory, nobody uses this for other reasons and they just won't notice as long as we get it set right closer to EoL.

Thanks,

Kyle Evans
Click to expand...

<https://lists.freebsd.org/archives/freebsd-questions/2022-February/000594.html>

Kyle and colleagues: if not already on your radar, maybe also some adjustment for releng/12.2. …
Click to expand...
 
Last edited:
eternal_noob said:
I am sure this has been asked before but i can't find information about which features are new in 13.1 and what changes have been made.
Is there a simple overview of the changelog (yet)?
Click to expand...

Retrospective: for 13.0, release notes and other pages first appeared on the Wednesday before the Friday creation of the releng/13.0 branch:

1646030663869.png

Looking ahead: for 13.1, hardware, installation, readme and relnotes pages might appear on or around Tuesday 8th March 2022.
 
Last edited:
Last edited:
Last edited:

FreeBSD 13.1-RC1​


The update to RC1 was committed a few hours ago.

<https://cgit.freebsd.org/src/log/?h=releng/13.1>

github.com

13.1: update to RC1 · freebsd/freebsd-src@6fe2900

Approved by: re (implicit) Sponsored by: Rubicon Communications, LLC ("Netgate")
github.com github.com

gitlab.com

13.1: update to RC1 (6fe29001) · Commits · FreeBSD / FreeBSD src · GitLab

Approved by: re (implicit) Sponsored by: Rubicon Communications, LLC ("Netgate")
gitlab.com gitlab.com


Not yet in release notes (paraphrased):

UEFI boot is improved for amd64. The loader detects whether the loaded kernel can handle the in-place staging area (non-copying mode). The default is copy_staging auto. Auto-detection can be overridden, for example: with copy_staging enable, the loader will unconditionally copy the staging area to 2M, regardless of kernel capabilities. Also, the code to grow the staging area is more robust; for growth to occur, it's no longer necessary to hand-tune and recompile the loader. (Sponsored by the FreeBSD Foundation)

– oversimplified (for drive-by readers):
  • FreeBSD 13.0-RELEASE, and its installer, fails to boot various computers
  • FreeBSD 13.1-RELEASE will succeed.
 
Last edited:
Menelkir said:
AFAIK, it happens when the releng branch for the next release is created, in this case, releng/13.1.
Click to expand...
Yep. Just before a new release branch is created 13.0-STABLE changes to 13.1-PRERELEASE: https://cgit.freebsd.org/src/commit...3&id=9134a3985069e879feee8149a6da96a3ad658fa8

Then a releng/13.1 branch is created. That branch be the base of 13.1-RELEASE. In the meantime stable/13 changes back to it's 'regular' -STABLE moniker: https://cgit.freebsd.org/src/commit...3&id=08523c8c63bbcdcd3f0d36787a544817cb5b8282

As the version was changed from 13.0 to 13.1 with the prerelease name change stable/13 will now indicate 13.1-STABLE. Development will continue there towards 13.2. releng/13.1 is then put through some cleanups and the first beta releases. Followed by one or more release candidates and will eventually be fully released as 13.1-RELEASE.
 
Thanks. Odd that the release engineering article documents -PRERELEASE to -BETA1, but not -STABLE to -PRERELEASE.
 

FreeBSD 13.1-RC3​


The update to RC3 was committed a few hours ago.

<https://cgit.freebsd.org/src/log/?h=releng/13.1>

github.com

13.1: update to RC3 · freebsd/freebsd-src@ec2fbe4

Approved by: re (implicit) Sponsored by: Rubicon Communications, LLC ("Netgate")
github.com github.com

gitlab.com

13.1: update to RC3 (ec2fbe4b) · Commits · FreeBSD / FreeBSD src · GitLab

Approved by: re (implicit) Sponsored by: Rubicon Communications, LLC ("Netgate")
gitlab.com gitlab.com

Availability: expect an announcement to freebsd-stable, and at the FreeBSD home page.


Generally, looking ahead: if you have not already done so, please subscribe to freebsd-announce. Thanks.
 
eternal_noob said:
I wonder if this is the last release candidate or if we get additional ones like with 13.0 (RC4 + RC5).
Click to expand...
In the past 20-25 years I don't think I've ever seen a RC4 being needed.

www.freebsd.org

FreeBSD 13.1 Release Process

FreeBSD is an operating system used to power modern servers, desktops, and embedded platforms.
www.freebsd.org www.freebsd.org

According to the schedule, the actual release builds should start on 21 April 2022. Building all the release images takes a bit of time of course. Then it needs to be distributed to all mirrors, which will also take a bit time.
 
eternal_noob said:
13.0 even had RC5...
Click to expand...
Ah, you're right. Can't remember what the reasons where for 13.0 though. It's definitely not a general rule, I think the only rule is to have a minimum of 2 release candidates. Then review if more are needed.

www.freebsd.org

FreeBSD 9.0 Release Process

FreeBSD is an operating system used to power modern servers, desktops, and embedded platforms.
www.freebsd.org www.freebsd.org
www.freebsd.org

FreeBSD 9.1 Release Process

FreeBSD is an operating system used to power modern servers, desktops, and embedded platforms.
www.freebsd.org www.freebsd.org
www.freebsd.org

FreeBSD 9.2 Release Process

FreeBSD is an operating system used to power modern servers, desktops, and embedded platforms.
www.freebsd.org www.freebsd.org
 
You must log in or register to reply here.
Back
Top