Release Lifecycle best practises

[hex-m]

I am looking for a guidance document regarding software lifecycle management for projects. This would (probably) contain things like

• communicate clearly which versions are "supported" by your project and for how long
• make clear what "supported" means for your project (what is considered a security vulnerability; explain the threat model)

The best resource I found was this: https://endoflife.date/recommendations

I expected to find those topics in the security-policy check of the Scorecard but there is only a vague statements about "what constitutes a vulnerability".

Tags: end-of-life, eol, release schedule, maintenance, end of support