Proposal - change the post-current and pre end-of-life phase name to something else #1144
Description
Is your request related to a problem? Please describe.
In the blog post Evolving the Node.js Release Schedule, the Node.js release team announced a shift from releasing two major versions annually to just one. Starting with version 26 and beyond, every release will receive Long-Term Support (LTS).
This change raises an interesting question: if all versions now receive LTS, what makes the "LTS" designation meaningful? Previously, the distinction mattered because odd-numbered versions (like 15, 17, 19) didn't receive long-term support—only even-numbered releases did. The "LTS" label specifically identified which versions would be maintained for extended periods.
Now that every version gets the same level of support, the "LTS" phase name has become somewhat redundant. It's a legacy term from the previous release model where the distinction between supported and non-supported versions was crucial for users planning their upgrade strategies.
Describe the solution you'd like
Consider renaming the post-current phase to something other than "LTS."
What about reusing terminology from the previous model, such as Active or Maintenance? Alternatively, you could introduce a new term like Standard or simply Support.
These alternatives would better reflect the phase's purpose now that all releases receive long-term support, making the "LTS" label less distinctive.
Additional context
Originally pointed out by @bengl in https://bsky.app/profile/bengl.dev/post/3mgq7kr54fc2v