I don't know if belongs in this thread. But what happened to point releases ?
Kernel X point release Y was a good idea. How is it replaced ?
Kernel X point release Y was a good idea. How is it replaced ?
No. Maybe it's a "Linux expatriate syndrome" or something jumping on -STABLE and totally misunderstanding it, but if you don't know what a RELEASE is, you have problems not solvable on FreeBSD's side. SirDice's theory makes a lot more sense here…
Where exactly? What's unclear about the download options offered at FreeBSD's website? Stuff like "distrowatch" is out of FreeBSD's control.
They still exist, 12.2 is a point release, 11.4 is a point release. But you're probably referring to the old support scheme where odd minor versions had two year support and even minor version one year. That went out the window from 11.0 onward. The problem was that it had a relatively short support period (2 years max) and too many different versions had to be supported at once. Now every major version is supported for at least 5 years and only the latest minor version of a major version is supported.
Well, I jumped on 13 as soon as it reached the "release candidates" phase, so I might be "infected" as well
If you want to use a complex tool, such as an operating system, you need to stop being an outsider. You need to actually read the instructions. *BSD is very different from Linux, except superficially. The way you use it (from a GUI and at user level) might be pretty similar; the way you administer it is somewhat different (for example /usr/local versus /usr for packages), but more importantly, the underlying philosophy (for example of base versus packages, or how to document things, or decomposition into separate subsystems) is VERY different. If you don't understand these differences, you will not be a happy user.
Maybe those who didn't bother to read up about the stuff they grabbed, but is that really of any concern? Those would be the same people - in my opinion obviously - who'd also happily download malware for Windows only to end up blaming Microsoft because their Windows environment runs so slowly. Surely it can't be because of them.
Patches for that release.
Is it correct to say that errata patches fix serious bugs that are not security vulnerabilities?Yep, they're security and/or errata patches for that release.
FreeBSD Security Advisories
FreeBSD is an operating system used to power modern servers, desktops, and embedded platforms.www.freebsd.org
FreeBSD Errata Notices
FreeBSD is an operating system used to power modern servers, desktops, and embedded platforms.
Yes, that's a good distinction.
-STABLE is the next minor release. As there's no 13.1-RELEASE on the horizon yet, so you would basically be 'downgrading' back to 13.0-RELEASE. If/when you want to switch from -STABLE to a -RELEASE the best moment is to wait just before the imminent release of that next minor version. Until then you should just keep up to date with -STABLE. And yes, you can switch from 13-STABLE to a -RELEASE without having to reinstall from scratch. You just need to checkout the correct release branch (when it's available), then build and install it. One of my systems I upgraded from a 12-STABLE to 13.0-RELEASE. And I've done similar conversions in the past.
stable/12 are naturally less frequent than merges to stable/13RELEASE and STABLE are supported – <link removed> (2013) point 2 helps to put this in contextYou can sit around the fire and marvel at how dumb everyone is all night, but the fact of the matter is: FreeBSD has a versioning scheme that's confusing for outsiders, it does a bad job at communicating the actual meaning, and nobody cares enough about users constantly installing the wrong version to make any changes.
And therefore, threads like this will keep popping up until the End of Time
. ' .
. . : . .
'. ______ .'
' _.-"` `"-._ '
.' '.
`'--. / \ .--'`
/ \
; ;
- -- | | -- -
| _. |
; /__`A ,_ ;
.-' \ |= |;._.}{__ / '-.
_.-""-|.' # '. ` `.-"{}<._
/ 1938 \ \ x `" _________
----/ \_.-'|--X---- < RELEASE >
-=_ | | |- X. =_ ---------
- __ |_________|_.-'|_X-X## \ ^__^
jgs `'-._|_|;:;_.-'` '::. `"- \ (oo)\_______
.:;. .:. ::. '::. (__)\ )\/\
||----w |
|| ||
/|___
///| ))
/////| )))
///////| )))
/////////| )))
///////////| ))))
/////////////| )))
//////////////| )))
////////////////|___)))
______________|________
\ STABLE /
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >
≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅ C T ≅≅≅≅ >
U N
R R Estable/13 to main (to 14.0-CURRENT): that's extraordinary, because I accidentally did so – with ease – twenty-two days ago:
main into stable/13stable/13 are periodically release engineered into releng/13.0.
Yes, it was. I bet I will get it right next time. I was actually doing an upgrade to 14.0-current over a custom kernel.
This is what I meant with the use of 13.0-CURRENT being 13.0-STABLE, which will "come to be" 13.1-RELEASE.
Based on what I know. Guys if I made a mistake, please correct.
