Date: Mon, 15 Jul 2024 13:24:03 +0300 From: Anton Shepelev <anton.txt@gmail.com> To: freebsd-stable@freebsd.org Subject: Re: Change to FreeBSD release scheduling etc. Message-ID: <20240715132403.997c4734a02fea34a049220a@gmail.com> References: <ZpPCADUpmCFHNa49@disp.intra.daemon.contact> <0f3ac4f8-e5ee-4ac4-a7c2-793035d9cde9@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrea Venturoli to Peter: > > In short, it takes me about 3 months to catch the > > surprizes[*] and fix (or find out how to cope with) the > > concerning issues, regressions et al. that come along > > with a new release. Up to now that would then give > > another 9 months during which the systems can be > > operated in a plan-of-record fashion, until the next > > release starts the hassle again. With the new concept > > this does seriousely change. > > [...] > > I'd be happy to hear if others have any idea or what they > plan to do. I am very new to FreeBSD, and completely inexperienced, so what I have to say below may be wrong and even silly, and I ask to let me know if it is: In my limited experice with some *nix-like OSes, they have to be updated more or less regularly lest they "sink" into an obsolete state whence it is /very/ difficult to restore them back up into updated and workable condition, what with dependency hell and deprecated repositories. Sometimes so much so, that installing a freshly downloaded distro is easier. On the other hand, upgrades do introduce regressions -- whether many or few, so as a casual user desktop user, I naturally want less hassle and longer periods of stable operation between the necessary upgrades.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240715132403.997c4734a02fea34a049220a>