From owner-freebsd-questions@freebsd.org Wed Feb 19 18:59:52 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1C15D24225A for ; Wed, 19 Feb 2020 18:59:52 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48N6Ty5nS7z48TV for ; Wed, 19 Feb 2020 18:59:50 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([94.222.29.196]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.167]) with ESMTPA (Nemesis) id 1N79dk-1jVyeA0V24-017RfE; Wed, 19 Feb 2020 19:59:42 +0100 Date: Wed, 19 Feb 2020 19:59:40 +0100 From: Polytropon To: Ottavio Caruso Cc: Ottavio Caruso via freebsd-questions Subject: Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life Message-Id: <20200219195940.0e252745.freebsd@edvax.de> In-Reply-To: References: <20200217231452.717FA1E820@freefall.freebsd.org> <20200218091959.b0220ac75bcfbbced91a5708@sohara.org> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:MDlOGISodXE/UKU8M+OfUOMq1w4Shs4fzLAk91AyyApo6foWcam FWn+fbVpguEqhAvK3ixFIfkoVaGUBlOoN7WbsTBV/351shnKuP5DCyNCjolGePsV1ewkWVV uwd9LjXxotERMA3fpQhXRTAyj7pUMo+zH4Xbs3jgx6uUfEBT0r653A9/zMXj+OhsI/oIau9 9sTjJ8H8gPkYC/CkDQTiw== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:h+EieJ9AiV4=:FSxwsWACeBGErBgaXh0RjI jreLFzSFQTljDa562URZi9/QnO02JEjgem37cAyv43SVTH2fcsO6Y7rIArn+YsrWPnMmpXd47 5a4YRnY61SSiKGxGZEucWwHjLoleT4e8H0iHzpKy9qcDH2CoaFx9vpfZrrDsMmeyRkjOHxuE6 w96xBPkx9sACY4Dyh0yAeknt5ZnOsOvoJg4tsaBCYA/K77MuLm5VrMjbwPgA5B/jdmn1Gh4N8 l6HIZZNsnCNj/vTNwZdLZEJyDwHdO0GglrVPXBbwh7FpvpBPUt55g7SsJ/gmyNspNFeRnW+S0 ov/fN+CdLyDOvWlNpUWqXRnQuzsFbVq9ZPE+PVekkkiwG+aGpuZiV0LBkuW6KGHhemtWtKCKM c29X0ShSkaIK6OsN87klnauq3j93PrO26btkd5/hctyVYIJg04JitKbJ4Qt+5MaUlPYjonmLI C22tMQNq7HBy93nX5x9SvgGRUztV4p8a+pNfQSeVRsYcMd2lTBBtS9zDv8Vqzs24dkYYUB5UG /GoWoCqvW2Qx8u4DHGvwwvrp0bCTvil396HxtV+2QCaDkCoLcjBsb5W0/bs85xpJyJaK/Pz0D eKQtQmNvY42fD1CNMCsKyI95pGjWoVB0ldBsSWDlgEL5FBNcJv6skIludwS8kAHfGrAExVHH/ 04vRdMunuPonLIbzJVVHGR6r9yQH881JND+M3FNZVvz0kOBrqUAj4Ee/c+XJM9v8kw994cSIe PRV58Ak5h5RzpkW01Pt3Pk2WoAh0WLlJfeJ00NYPzNXSQQNPWp1sLK2nna4mHI269ZYfDn+MC TFUosZRhAAcnBlxry0UAJAOs8vNcvnZM+mdW/5iLuciCd1KSXGxyIWRuuNojQLsFHlI64wZ X-Rspamd-Queue-Id: 48N6Ty5nS7z48TV X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd@edvax.de has no SPF policy when checking 212.227.126.131) smtp.mailfrom=freebsd@edvax.de X-Spamd-Result: default: False [4.86 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[freebsd@edvax.de]; MV_CASE(0.50)[]; HAS_ORG_HEADER(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; MIME_TRACE(0.00)[0:+]; RECEIVED_SPAMHAUS_PBL(0.00)[196.29.222.94.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; ARC_NA(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[edvax.de]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.99)[0.995,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(1.00)[0.997,0]; MID_CONTAINS_FROM(1.00)[]; RCVD_IN_DNSWL_NONE(0.00)[131.126.227.212.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(0.47)[ip: (1.30), ipnet: 212.227.0.0/16(-1.12), asn: 8560(2.19), country: DE(-0.02)] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Feb 2020 18:59:52 -0000 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 wrote: > > > > On 18 Feb 2020, at 20:39, Tomasz CEDRO wrote: > > > > > > On Tue, Feb 18, 2020 at 3:51 PM Ed Maste wrote: > > >> > > >> On Tue, 18 Feb 2020 at 05:37, Tomasz CEDRO 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, ...