website: Legacy Releases -> Maintenance Releases

[ziaee]

Summary

Legacy is a bad name that forces the reader to draw from context.
It makes them say "I could figure out what this means" instead of
"I understand what this means". Maintenance Releases tells the
reader what they want to know, improving the clarity of our information
ecosystem.

[ziaee]

align "where" naming convention with "release information" naming convention.

[ziaee]

release information: s/maintenance releases are for existing users/maintenance releases are for existing deployments/ because... it's the deployment that is selected for the conservative update strategy, not the user.

[vladlen]

It would be good to deal with 'legacy' word, we do not know how to translate it polite to Russian. Last version is 'old production releases', long but neutral. Word 'maintenance' sounds good, but it is also not easy to translate. Is not it common to name previous releases as 'maintenance' ? Not an objection, just for information.

[ziaee]

I still think this is a good idea, but actually general consensus is that most of my colleagues that have noticed do not agree.

[emaste]

The issue I have with "maintenance" is that then 14.x releases are production releases that get maintenance updates and 13.x releases are maintenance releases that are suitable for use in production.

Releases from both branches are still supported. 13.x is the older release series, has fewer features and perhaps more bugs (or different bugs). Semiconductor vendors use "NRND - Not Recommended for New Designs" for this kind of case -- the parts are still available, but ought not be used in new things. We can maybe say the same thing about the older release series -- not recommended for new deployments -- if you've got an existing 13.x deployment then upgrading to 13.(x+1) is a sensible path when it comes out, or adding additional 13.x machines for additional capacity. For a new deployment, use 14.x.

[ziaee]

Not Recommended for New Designs

I really like this! I think it's also aligning our language with our core market, which to me, is improving the concept of "the product reaching the correct audience".

Also, as I say often, I do not like the term legacy because I think it's kinda a catchall term, kinda imprecise.