What is the difference between RELEASE versions, STABLE versions, and CURRENT versions? I've done some reading but I'm still a bit confused. Thanks. -Matt
On Mon, Nov 28, 2005 at 10:40:55PM -0500, Matthew Tomsa wrote:> What is the difference between RELEASE versions, STABLE versions, and > CURRENT versions?Please see the following: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/introduction.html http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/version-guide/ mcl
Scott Robbins
2005-Nov-29 03:51 UTC
Difference between RELEASE, STABLE, CURRENT (was (no subject) )
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Nov 28, 2005 at 10:40:55PM -0500, Matthew Tomsa wrote:> What is the difference between RELEASE versions, STABLE versions, and > CURRENT versions? I've done some reading but I'm still a bit confused. > Thanks. >One of the best explanations that I've seen can be found on freebsdforums.org http://www.freebsdforums.org/forums/showthread.php?t=36652&highlight=RELEASE+CURRENT+STABLE (The final post, by the gentleman who uses the name phoenix) - -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Principal Snyder: There are things I will not tolerate: students loitering on campus after school, horrible murders with hearts being removed. And also smoking. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDi8/e+lTVdes0Z9YRAswFAJ9XJ9mdnIyZErCRGkQQ2PF3/qA8xwCfcw+d Peg6cAFHCPk47zkq7ar+nHQ=z6gf -----END PGP SIGNATURE-----
Matthew Tomsa wrote:> What is the difference between RELEASE versions, STABLE versions, and > CURRENT versions? I've done some reading but I'm still a bit confused. > Thanks.-CURRENT is alpha. -STABLE is supposed to be the leading edge of functionality yet be stable enough for production use; it should be treated as a late beta. In other words, test it before deploying in production, because sometimes, perhaps a day or two per month, -STABLE contains problems or breakage. Every few months, the project makes an effort to stabilize the source tree (including ports and docs), generates a release candidate or two, and then pushes out a RELEASE by tagging the -STABLE branch. A -RELEASE or security branch is intended for production use because it has undergone such testing, and is updated with security patches and critical fixes only after such changes have been tested in -CURRENT or -STABLE. If you don't know what to run, run the security branch (ie, RELENG_5_4). -- -Chuck