Date: Wed, 19 Feb 2020 19:59:40 +0100 From: Polytropon <freebsd@edvax.de> To: Ottavio Caruso <ottavio2006-usenet2012@yahoo.com> Cc: Ottavio Caruso via freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life Message-ID: <20200219195940.0e252745.freebsd@edvax.de> In-Reply-To: <CAEJNuHycWihEj0_61bW2WBBU3vWmqQHKWKd3DqCXtLAD%2BWof5A@mail.gmail.com> References: <20200217231452.717FA1E820@freefall.freebsd.org> <CAFYkXjmZi1-MB6W0HsMx9gHek7Xg5heoSKKWkNTnw74dxRTwAw@mail.gmail.com> <20200218091959.b0220ac75bcfbbced91a5708@sohara.org> <CAFYkXjmWBUDyV3XKL1qwt=g0AUgDttDfOB6euKqJMAmOs-1Prw@mail.gmail.com> <CAPyFy2D4Dyq6P6sZZ70R1cG%2BNoVcv808sbQeSWTzTrNELnH8ew@mail.gmail.com> <CAFYkXjk=rpp_8nD=xGirghCLouRAsC-N%2BJJppMKDQN0aGKnKDw@mail.gmail.com> <D2835D98-3303-4DE7-A98D-82035535E18B@yuripv.me> <CAEJNuHycWihEj0_61bW2WBBU3vWmqQHKWKd3DqCXtLAD%2BWof5A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 19 Feb 2020 08:52:33 +0000, Ottavio Caruso via freebsd-questions wrote: > On Wed, 19 Feb 2020 at 00:49, Yuri Pankov <yuripv@yuripv.me> wrote: > > > > On 18 Feb 2020, at 20:39, Tomasz CEDRO <tomek@cedro.info> wrote: > > > > > > On Tue, Feb 18, 2020 at 3:51 PM Ed Maste <emaste@freebsd.org> wrote: > > >> > > >> On Tue, 18 Feb 2020 at 05:37, Tomasz CEDRO <tomek@cedro.info> wrote: > > >>> > > >>> Maybe its a time to give OpenBSD a try.. > > >> > > >> I really don't understand this comment, either. Certainly give OpenBSD > > >> a try and if it fits your needs better that's great. > > >> > > >> As far as I'm aware OpenBSD issues a release every six months and > > >> supports the most recent two releases, so it seems odd to me to > > >> complain about FreeBSD's ~1 year minor release support lifetime and 5 > > >> year stable branch support lifetime in that context. > > > > > > Its more like "lets try if what I need works better over there". Not > > > really the release timeline. > > > > > > The release timeline problem is more related with pushing untested > > > features (and possible avalanche of solutions that introduce yet > > > another complications that we observe right now). > > > > > > "The BSD Way", for me, was always about "it works solid or its not > > > there". Like macOS / iOS. > > > > > > Unlike "The Linux Way" where things changes upside down from release > > > to release and each one of them has its own universe of variants. Like > > > Android. > > > > > > I am not sure if it is that important if there is a release in 6 month > > > or 2 years. Not a problem at all. If in two years I get a 5 new > > > features that work rock solid then it seems a better choice than > > > getting new features every six months and have more problems on a > > > production because of that. > > > > > > If I need to experiment there is a CURRENT branch. For well tested > > > features I have STABLE. For rock solid "I bet my money on that" I have > > > a RELEASE. Right? > > > > > > I did miss the 12.0 EoL kind of fix for DRM, sorry, it seems > > > reasonable. I am just worried that 12.2-RELEASE will have the same > > > problems, if not more new problems. > > > > It is something you can help with, run 12.2-STABLE on some > > spare equipment and report problems that affect *your* environment. > > To a beginner and uninitiated like me, the way FreeBSD labels > "stable", "release", "releng" and "current" is, at the very least, > confusing. That is true. If you look at the FreeBSD website, you'll quickly find documentation that explains "which is for whom". Basically, it's a kind of "refinement process" that has the following habits: HEAD / CURRENT: Active development takes place here. It's updated quite quickly, sometimes several times a day. Such a snapshot might build, but not run, but might fail to build, too. Features can be tested, can disappear, or change. STABLE: Everything that's considered to stay in FreeBSD will be kept here. It is usually tested, and such a snapshot will build and boot. Thw word "stable" refers to the ABI being stable. Both -HEAD and -STABLE can only be tracked via source control (here: svn). RELEASE: This is the snapshot that contains what is on the installation media: tested and verified. Stages up to this point can include -BETA, -ALPHA, -RC, (release candidate), -PRERELEASE or such kinds of snapshots. RELEASE-pX: WHen development moves on, security patches will be made available. They can be "added" to already installed release versions. Both -RELEASE and RELEASE-pX can be obtained in a binary way (here: freebsd-update). That is just a rough outline, but I believe it's fully clear now what the different names refer to. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200219195940.0e252745.freebsd>