#3238652-138: [policy] Decide how long major Drupal versions should be supported →
Thanks, @xjm. Core may only support two major versions. But technically someone could upgrade form 10.3 to 12, hence a contrib needing to support three branches. This has been a major pain point in major version readiness, spreading support across real-world sites that are upgrading. Shorter minor release cycles actually makes this easier, so there might be less pain.
I just wanted to raise it, just in case. Once this is official, it'd be great to have documentation on best practice for Drupal core support in contributed projects (see also @catch comment in #104.)
Active
11.0 🔥
This probably needs to be against the documentation project rather than core, but also not moving it since it makes sense to have visibility in the core queue for a bit.
If we had a functional technical working group it would be something that could be under its oversight, but we've only got the coding standards committee part of that up and running.