From owner-freebsd-questions@freebsd.org Thu Feb 4 11:12:11 2021 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 9EE62540138 for ; Thu, 4 Feb 2021 11:12:11 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DWbVM2CZKz3jW7 for ; Thu, 4 Feb 2021 11:12:11 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: by mailman.nyi.freebsd.org (Postfix) id 4BD6E53FE98; Thu, 4 Feb 2021 11:12:11 +0000 (UTC) Delivered-To: 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 4BA0C540137 for ; Thu, 4 Feb 2021 11:12:11 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.134]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DWbVM01y7z3jW6 for ; Thu, 4 Feb 2021 11:12:10 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([94.223.160.123]) by mrelayeu.kundenserver.de (mreue009 [212.227.15.167]) with ESMTPA (Nemesis) id 1N3sZs-1m72rL1qjo-00znGB; Thu, 04 Feb 2021 12:11:55 +0100 Date: Thu, 4 Feb 2021 12:11:53 +0100 From: Polytropon To: "@lbutlr" Cc: FreeBSD Subject: Re: Suggestion for release names? Message-Id: <20210204121153.6616001f.freebsd@edvax.de> In-Reply-To: References: 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:ODK0P0wcwQVs9QBUOAgMm91dLvR/KDDP9SK83uS2MIuGZNE+gC/ ESYEPq2OMkZcF8EMHv9EPPQYmNFSGtn8l9fh9Q88KrBr1ESpSopLke9CXF7fssGCnpM+6ob Rttuu3N3dNPJfFfPdjYITcowbIfxhWrQpCFT0n0Z+AnmQ+W0RpltPjer+hHGNHcLPxnb/4l pPMhvQV9X6PD8LVurHCoA== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:tvWvLULBgAg=:dGO482PoQuO8jER06uBOLu aiC5pnUcETemutBVErNI/UMbSSEyJxEljMyz8ov2pVbo4XuqLd4XFUmS/qYT/Xj9n2xnT8TT9 oU46Ug69hoX/Djq5DAV7seZnz3AalYWANoreLVVdKW9Z4GmaocQ3psWrT82v+tJaJdBYH94G1 Cp0YnIPAsh2sR7ZBXOQWdT0vWjxkrC6/q9Emu40xSPzbtQTo8fmkgxVEJ7DZdJ1+/ZH12BqGr ObT4IMevZO8MIC5AYDWkR/A3nddGID8/fCnEY/wRkkurWUa+wN0vW2vKbcJjl4tTgRDtLgp8p DJdbithUxDkqbdffw0mGBiI8/SjtYfg9aWwvDhgYvRszHAwtx/vOrOgIS2N1zc1f5fkqVWMdt mk48/2u+UtRpsClUZJNG6g+Pcwr6GdWoaNMF3EnNU/QwzG9jqMj72/5Mkgjnp X-Rspamd-Queue-Id: 4DWbVM01y7z3jW6 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2021 11:12:11 -0000 On Wed, 3 Feb 2021 13:34:30 -0700, @lbutlr wrote: > I know the subject of user confusion on STABLE and RELEASE has come > up in the past, but I found out that releng is also confusing as I > was recently talking to someone who only ran releng versions of > freebsd because he thought that was an English only version of > Release. RELENG means release engineering - unfortunate misunderstanding. > I know this is probably futile and there's little reason to change, > but I think all three animus could be better. The "problem" is that those termini technici all carry a well understood meaning, which now is to be considered history (i. e., "for historic reasons"). Even worse, if you try to do a mapping of RELEASE-p | RELEASE | | home user PRERELEASE | | embedded RC | is to be | desktop BETA | used for | server ALPHA | | tester STABLE | | developer CURRENT / HEAD | this will be very hard and probably won't work. ;-) Note that especially tha ALPHA, BETA, PRERELEASE and RC tags are not always used. > STABLE -> "PreRelease" or "Candidate" (although RC is already used, > so many not that) Both suggestions already have been in use: -PRERELEASE and -RC are point during development on the way to RELEASE. Also STABLE isn't really a pre-release or release candidate. It's more a "step during development" that contains stuff that will probably be in the next release, as well as being the source for special security patches that should be backported to earlier versions still under support. > RELEASE -> "" or "Production" or Tht term RELEASE indicates that this is what has been released on the installation media - today, files from the Internet, but historically RELEASE was what you got on the CD set. :-) > Releng -> Development That doesn't fully match the path of RELENG (release engineering). Like in a distillery, the development happens at the top, at HEAD or CURRENT. Those versions can add and remove (!) features, will sometimes not even build properly, and can be subject to significant changes. What has been approved, will then be in STABLE, which also means that the ABI will be stable. From that level, work will be done toward the next RELEASE, and also the patches for already existing releases are generated (RELEASE-p). > I'm not proposing the these are the names that should be picked, > but I think names could be picked that make it clearer that RELEASE > is the 'real' version for most everyone and not stable and spells > out more clearly what releng is. Maybe the following documentation parts should be more prominently presented on the home page? https://www.freebsd.org/releases/ https://www.freebsd.org/relnotes/ https://docs.freebsd.org/doc/3.5-RELEASE/usr/share/doc/handbook/current-stable.html https://docs.freebsd.org/en_US.ISO8859-1/books/handbook/current-stable.html -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...