In reply to Terence.

Terrence, there is a real need for WordPress LTS, which will be exposed as a major weakness with WordPress 5. I'd say that Gutenblock is too sarcastic to attract serious support. I thought about launching BorgPress as a joke site, but that'd be very mean-spirited.

The Classic Editor plugin by @azaozz is provided as a delay solution, and there are posts on disabling major upgrades and Gutenberg itself. When WP5 hits there will be a surge in recommendations to delay and disable Gutenberg, and some WP agency CTOs have already dug in their heels to stay on 4.9.x for a year to see how things land.

Here's the real problem: all those darn plugins! Developer shops will be forced to decide if they can support one path or the other or both...UGH. Jeff's pain on this post will not be an easy fix...

That scenario was the final nail in the Joomla coffin, when they forced a roadmap strategy of quarterly fast-paced minor upgrades with limited support and an annual major upgrade with breakage and LTS. Joomla Extension developers wouldn't have it; they said we'll just wait to see what pans out in the major upgrade and then decide what to do at a later stage. The result is that users were left floundering in the wake of mismatched versions with confusing support. There was a similar backlash with Drupal 6, where some shops sat on version 5 LTS and delayed until 7 was viable.

WordPress.org does issue patch upgrades for previous versions, and the intention is to continue that practice, BUT since WordPress has no official LTS or sunset schedules, it'll be a crap shoot.

Bottom line? Big companies can extract upgrade costs, while the rest of us ride out the turbulent waves of "Innovation." Choice? BorgPress or LTSpress.