According to your schedule there seems to be no way of avoiding upgrading every 6 months in order to remain in support. Example;
Currently, everyone using Drupal would be on v11.3 or lower.
June to December: upgrade to v11.4 between June and December.
December to June next year: if support for v11.4 ends December (currently no advised date), then you have the options of upgrading to either v11.5 or v12.
When you are responsible for multiple Drupal sites, this continual need to upgrade every 6 months to remain in support is problematic.
The upgrade path needs to provide more lead time, or more time in support for each upgrade.
At the moment trying to plan the next year of work is not possible based on the information available (or rather, lack of information).
By janehad on
Comments
Drupal Release Calendar in Mermaid
There is the Release process overview > Sample release schedule diagram, and a lot of work went into #3399348: Commit a mermaid version of the core release cycle diagram to core to make Drupal Release Calendar in Mermaid two years ago, but sadly the issue stalled.