5 ms·
What we need is updates that only include security patches.... FEATURE CHANGES SHOULD BE OPTIONAL. Because all software tend to decrease in quality overtime.
by ijhuygft776 3y ago
What we need is updates that only include security patches.... FEATURE CHANGES SHOULD BE OPTIONAL. Because all software tend to decrease in quality overtime.
- codepoet80 3y agoIf you're in the Microsoft world, try out the LTSC flavors (of Windows and Office). Its basically just that -- security updates and patches, no new features. Since switching, my environments have been much more stable, no Windows Updates that ruin my day -- just the stuff I need to stay secure, none of the new crap they're trying to push...
- ocdtrekkie 3y agoEven Office LTSC has to have policy changes applied to bypass some cloud functionality they stuffed in there, mind you.
- dspillett 3y agoWhile a desirable state for users, this could quickly balloon into a nest of support issues for the maintainers due to having many different versions to patch when a security issue or other significant bug becomes apparent, increasing the project's response time to anything important like that. You could try to mitigate this by maintaining only a couple of versions (perhaps preview, current, and LTS similar to Debian's sid/testing/stable) which would work for small projects, but for large ones or those that see fairly rapid development you runt he risk of stable gaining a reputation for being out of date, unless you bump it forward regularly which puts you back at square one with giving people feature updates they may not need.
- ijhuygft776 3y ago> While a desirable state for users, isn't users all that matters in the long term?
- arccy 3y agoif your development process is unsustainable, then your users get nothing in the end.
- ijhuygft776 3y agothey just need new development methods
- dspillett 3y agoIf you have an idea for a process that could deal with the potential significant extra load caused by many optional updates on the general case, feel free to share. It can work well and easily when the features are relatively distinct, but as they start to interact it can become a huge burden.
- vbezhenar 3y agoRHEL and many other companies offer that. It's called long term support, extended long term support and so on. And costs a fortune. Most people wouldn't want to buy it.
- Pxtl 3y agoThat functionally makes refactoring your codebase impossible as backporting security patches and bugfixes would be a nightmare.