Ask HN: Why does FreeBSD do Releases the way the do?
First a general response:<p>There&#x27;s a couple ways to run FreeBSD in production. Netflix does bleeding edge, and follows CURRENT, which is good for them because they do a lot of changes in the kernel, and want to upstream their changes, so staying up to date on CURRENT makes upstreaming easier which makes their life easier.<p>The other way is to use FreeBSD as a stable base, and only upgrade when you need it. In that way, you periodically validate new releases, and install new servers on your currently validated release, and leave existing servers with the release they were installed with, and sparingly update between releases when there&#x27;s something important. Some choose to avoid .0 releases, and some choose to avoid X.Y where X % 2 == 1 (even numbered releases don&#x27;t suck); although really it was only 5 that was worth skipping. Avoiding .0 releases may be obsolete as well, I seem to recall not having major issues with 13.0, 12.0, 11.0, and 10.0, but it&#x27;s been a while. I wouldn&#x27;t rush out to get a new major release, unless there was a very important feature&#x2F;enhancement though.<p>Build your application software on a build machine that runs the oldest release that you run, be sure to install the compat_X packages so you can run older software on newer releases. If you run into bugs, expect to fix them yourself (that&#x27;s what open source software is about, right?), and report them to upstream, and that they may be fixed in future releases. You&#x27;ll need&#x2F;want to develop a workflow where you fetch the upstream source for a release, apply your patches, and build world, release validation involves checking if your patches are still needed and updating them to still apply if needed. When releases are patched (ex 13.0-RELEASE-p7), it almost never breaks anything, so I would almost always build from the latest release patch when building a new server (there may be some exceptional versions), but I would read announcements to see if the change was relevant before updating servers. Minor versions are usually not a big deal either, but major versions often need patches updated and sometimes have major behavioral differences.<p>Now to your bullet points:<p>a) This shouldn&#x27;t be confusing. Although maybe the presentation on the security page[1] is more (or less) clear. The 13.X series was released April 2021, and is expected to get security updates and critical patches until EoL, which is currently expected to be January 2026. The 12.X series was released December, 2018 and EoL is expected to be March 2022. This is a roughly 5 year commitment, rationale in the announcement [2]. Each minor release is supported through either 3 months beyond the next minor release of that major release or until the major release EoL, whichever comes first. FreeBSD plans to not have major releases more than once every two years, so there&#x27;s at most three major releases supported at any given time.<p>b) It depends on the scope of the problem; bug fixes do get released onto branches, when it&#x27;s justified. The expectation is that RELEASE branches are mature on release and won&#x27;t change much. This isn&#x27;t great if there&#x27;s a bug that&#x27;s important to you, but doesn&#x27;t justify a fix in RELEASE for upstream.<p>c) This is at odds with your point in a. The FreeBSD team can only support so many releases, so they&#x27;ve said when a minor release is superseded, you get 3 months notice. Actually, if you follow along with upcoming release announcements, you get a bit more notice: 13.1 is currently in the release process, with a target date of April 26 (and the schedule was announced February 1); so we can anticipate 13.0 will end support near the end of July.<p>Also, it&#x27;s important to note that the end of support doesn&#x27;t mean your server turns into a pumpkin; just that you no longer have security advisories that specifically discuss your installed OS. If you keep abreast of security advisories in general, you can look into things that are reported on the software in base, and the currently supported releases and decide if it likely applies to the older versions and either backport fixes&#x2F;workarounds or upgrade to a supported release.<p>If you consider your point in b, that you&#x27;re not getting all that much support on the supported releases, losing support doesn&#x27;t seem to be that big of a deal either. If you run into a bug, try it on one of your more updated servers (or update a server to try it on); if it&#x27;s fixed, great, upgrade your impacted servers; if it&#x27;s not fixed by upgrading then figure out how to fix it and if it&#x27;s easier to fix in place or upgrade and fix at the same time.<p>e) This seems to be a rehash of a, but also c. If you want releases supported beyond the next release, they need to be listed. If you want to know what&#x27;s happening with releases, the upcoming version should be listed. If you&#x27;re having trouble picking which release to use, use the first one in the supported list, that&#x27;s why it&#x27;s there.<p>[1] <a href="https:&#x2F;&#x2F;www.freebsd.org&#x2F;security&#x2F;#sup" rel="nofollow">https:&#x2F;&#x2F;www.freebsd.org&#x2F;security&#x2F;#sup</a><p>[2] <a href="https:&#x2F;&#x2F;lists.freebsd.org&#x2F;pipermail&#x2F;freebsd-announce&#x2F;2015-February&#x2F;001624.html" rel="nofollow">https:&#x2F;&#x2F;lists.freebsd.org&#x2F;pipermail&#x2F;freebsd-announce&#x2F;2015-Fe...</a>