In reply to Cavalary.

"LTS" (Long Term Service) distros became popular in Linux. They were intended at first for (sniff) business-users, and other special-cases. Regular people of course caught on, and started flocking to LTS releases. The idea & practice is spreading far & wide.

Highly competitive sectors need to innovate and react rapidly. In part, they use a fast/frequent release schedule to do this. It lets them evolve & adapt. At this point, WordPress needs to give the appearance of competing with Drupal, which helps them feel like they are indeed competing/competitive. With the kind of dominance WP now has, any 'competitor' still alive has value, as insulation against monopoly-charges.

But WP does have real & good goals they want to achieve, and they may be fully-loaded, just trying to maintain momentum. Adding the burden to maintain (multiple) LTS, or modifying the current product so it makes an LTS version practical, could be more than WP can swing.
===

Note carefully that dependency-resolution (using PHP Composer, in this case) - a main topic here - strongly promotes release-stability and a more-conservative software paradigm, overall. It also isolates the system from its components, which helps with the kinds of things you want.

So going with the Composer-dependency innovation would tend to favor the prospects for an LTS WordPress. It sounds like an enormous step, though.