Rolling releases

A rolling release is a software development model where updates are continuously delivered rather than in large, fixed version releases or time-based releases. Instead of waiting for a new major version (e.g., version 2.0 after version 1.0), the software is continuously updated with new features, bug fixes, security patches as they become ready.

I have been using ArchLinux as my daily driver which uses this model. Recently moved the webserver also on an Archlinux OS, update the distributions once a week and optionally reboot if kernel is updated otherwise continue. My workstation has been rolling on ArchLinux since 2016 and hope that webserver continues with the streak as well.

Usually its said that rolling release is preferred by developers who want cutting-edge software and are ready for frequent upgrade/reboots, requires more active maintenance, which is true but if I calculate total time spent on maintenance on a rolling release it is far less than maintaining time-based releases lets say Ubuntu, consider time I will spend upgrading from 22.04 to 24.04, its perhaps double the amount I need to spend on Archlinux in that two year period.

Rolling releases are also informing me regularly of technical cruft I collect as a result I collect less, it keeps the system nimble.

Overall, it looks to have simplified the process.

We grow from being infant to toddler to teenager and adult in a continual manner, we do not freeze ourselves to be an 8-year-old for next 5 years and suddenly become a teenager one fine day, so life itself seems to be following a rolling release model and hence a natural process. If we can get a process which reflects nature, its already tested and tried, we only need to ensure that right kind of guardrails are in place for it to work effectively

Keep Rolling !