On Tue, Mar 04, 2025 at 09:57:10AM +0000, Andrew M.A. Cater wrote: > On Tue, Mar 04, 2025 at 02:16:23PM +0530, Sarbjit Singh Sandhu wrote: > > Dear Debian Developers, > > > > Hi,
[...] > As it is, the creation of a major stable release takes a long time. > Once released, there's a two year cycle and an additional one year > of security support - this is typical for the last few releases. > (See, for example, https://endoflife.date/debian). > > > A yearly stable release would allow schools to benefit from the latest > > software and security updates without the long wait between releases. This > > would also make it easier for schools to plan their IT infrastructure and > > ensure that students have access to the latest tools and technologies. > > > > Security updates are supplied very regularly: the point releases also > roll them up every few months. The latest software takes time to package > - not all software changes every year, and there are > 40,000 packages. To add to all those very good points: if you need newer software (besides the security updates, which Debian is extremely good at providin in a timely fashion, BTW), there are the backports. And it's not that difficult to contribute to that. Update churn is not only a major work for the Debian developers, but also for the users. During a stable release you can be pretty sure that nothing will break -- I run my updates more or less blindly. Version upgrades are more serious -- if a basic lib ups its major version, you will get some breakage. It is good to be able to schedule those events and to test them beforehand, more so in a bigger institution. Cheers -- t
signature.asc
Description: PGP signature
