Comment 2 year LTS support is not realistic for govt (Score 1) 106
Why not just have TWO long term support versions plus the current version. One for every 3 years. So, currently have a 2020 LTS version and a 2017 LTS version and by then end of this year, decide on the new LTS 2023 version. When the 2023 version gets set, support the 2017 version only until they post the next Kernel build either at the end of 2023 or the first build in 2024. At that point, 2017 is dropped. And just move forward with two 3 year LTS versions going forward in a similar manner.
Places like the federal government as well as many businesses like to have longer LTS support. 6 years makes sense to keep. Otherwise, think of the DOZENS of major software systems that would have to be tested repeatedly with a narrow timeframe.
Big organizations have multi year timelines for testing just one or two major software systems (I'm thinking of one system at the moment with over 10 million lines of code in an archaic language, MUMPS), imagine testing even dozens of smaller but complex systems and add to that human churn as people come and go and you lose your knowledge base. Add to that, in government you have the major leadership and even sub-agency level churn factor every 4 years as top dogs get replaced, and then they appoint new folks under them who often appoint new folks under them who ALL have new agenda's and priorities but need to close out the previous administrations projects, which takes a year or more on one hand, but at the same time, government doesn't want to spend money to hire extra folks just to be always testing kernels vs their apps all the time.