3 ms·
> ... which means that if 12.1-RELEASE came out at the end of 2019 and 13.0-RELEASE came out in April of 2021, you had all of 16 months to make investments in t
by lmm 5y ago
> ... which means that if 12.1-RELEASE came out at the end of 2019 and 13.0-RELEASE came out in April of 2021, you had all of 16 months to make investments in the 12 branch
A worst-case 16 months sounds like an absurdly long support window by the standards of most actively developed projects; anything but the largest and most corporate of projects is unlikely to do better than that.
And it seems contradictory to complain that stable releases aren't supported long enough but you're waiting too long for new functionality. Of course everyone wants daily releases that are supported forever, but realistically with finite development effort most projects have to settle on something equivalent to "you can run -CURRENT or you can run LTS, pick your poison".
- smaudet 5y agoAs others have pointed out LTS exists elsewhere - the truth is LTS is minimum level of support necessary for most users. Everything else is essentially bleeding edge - too much work to maintain, constantly bugged, etc. The previous model where a major change could have support last for decades, where the system was modular in that patches could apply to any major version - that was gold. Unfortunately today we have this "yesterday's tech is garbage" attitude, and honeslty it is mostly making all software garbage.
- r_hoods_ghost 5y agoThis has not been my experience over the last 20 years across multiple industries. Generally I'd expect (and have written into an SLA) a minimum of 2 years support for anything even vaguely critical. If using Open Source I'd be buying from a vendor who would guarantee that level of support. I acknowledge it's different if you're working for an early stage startup designing the next tinder for marmosets or whatever in which case you probably don't care about support windows because you're likely to crash and burn within your support window.
- lmm 5y agoI've worked across industries in everything from a 2-person startup to an F500 investment bank, and I've very rarely seen a 2 year SLA for anything. (Rolling 6 months was the standard at the investment bank). Buying all your open source frameworks is an expensive luxury (and rarely worth anything), at least if you're in a position where you actually need to deliver.
- oblio 5y agoSo you're saying that you've never worked somewhere where the base OS was an old version of Red Hat that was still supported, probably 5-7 years after release?
- lmm 5y agoNow that I think about it I have seen computer running an OS like that, but only for the machine that was running the Oracle database that let the CTO get his golf buddy a $50k/month sale, never on one that was actually being used to do something.
- oblio 5y agoThis is standard operating procedure for financial institutions in Europe, at least. And many, many other types of enterprises. For core banking and other mission critical systems. Nobody upgrades an OS for fun, especially when the checklist for doing so is longer than both my arms put together.
- lmm 5y agoNot every financial institution in Europe, I assure you. The one I worked with actually had a policy that anything that hadn't been updated in six months had to be signed off as it was considered a risk factor.
- oblio 5y agoI think we might be talking past each other and you may have missed the original point. This is not about security updates. This is about using old, but still updated LTS/enterprise versions. I don't know <<any>> enterprise mandating upgrade to the latest LTS within 6 months. Most do it 6 months before the old LTS period will expire :-))
- lmm 5y ago