Long Term Support Windows

[Eonasdan]

I would like to determine some LTS windows. Defining these will help you know how long I hope to support a version and when it's time that I can remove deprecated features or other breaking changes.

Here's a couple example LTS windows.

Angular
Node
Bootstrap

I'm leaning towards a 6-month Active status, 6 month LTS, 6 months of Maintenance, after which that version will be EOL (End of Life).

	Active	LTS	Maintenance
V6	2022-10	2023-07	2024-01

gantt
    title Tempus Dominus Release
    dateFormat  YYYY-MM
    section V6
    Active             :active, a1, 2023-1, 2023-07
    LTS                 :           lts, 2023-07,  2024-01
    Maintenance :crit, mtn, 2024-01, 2024-07
    #section V7
    #Active          :active, a2, after a1,2024-01
    #LTS     :lts2, after a2, 2024-07
    #Maintenance :crit, mtn2, after lts2, 2025-01

Loading

To quote Bootstrap's docs:

Release plan

New releases of Bootstrap are made from the main branch to the Active major version. At times to be determined by the release working group, major versions will be frozen and transitioned to Long Term Support (LTS). A long term support branch will be forked from main, making way for semver-major changes to be made on main and a new Active major version to be prepared.

A version in Long Term Support should not have new features landed without a compelling reason. It may continue to receive:

• Bug fixes
• Security updates
• Documentation updates

After a determined period of time, versions in Long Term Support will be deep-frozen and transition to Maintenance.

Versions in Maintenance should not have any changes landed, except for:

• Critical bug fixes
• Critical security updates
• Important documentation updates

Unless a change is urgent, Maintenance releases are likely to be made with minimal frequency.