[Request - Product] AWS Lambda runtimes

[jamietanna]

Full and short name of product

AWS Lambda

Does this product have LTS versions? What are the intervals between each LTS version?

No

What is the website for the product and for its version information?

https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html

Additional context

AWS Lambda contains a number of runtimes which have different deprecation/end-of-life policies.

I've previously worked on this problem and ended up hardcoding the dates at the time of writing which has the risk of being out of date before too long, so thought of automating this process, perhaps by parsing the HTML.

[welcome]

Thank you for opening your first issue here 👍. Be sure to follow the issue template if you chose one.

[jamietanna]

I've looked at endoflife-date/release-data#127 but that may be blocked by endoflife-date/release-data#51 - instead, does it even need that, or can we just have the scripts work for the YAML in this repo?

[captn3m0]

The first step is creating a page for the product, setting up automation (for new releases) comes next, and we can look at automating EOL dates after that.

[jamietanna]

Cool, thanks! For AWS Lambda runtimes, there's not really an "update" to a runtime (at least made publicly available) but are more treated as released but never updated. Would that still make sense to exist in release-data or instead maybe just in this repo?

[marcwrobel]

This product looks difficult to document, I am wondering if we shouldn't treat each runtime independently, that would facilitate the maintenance and automation IMO.

Cool, thanks! For AWS Lambda runtimes, there's not really an "update" to a runtime (at least made publicly available) but are more treated as released but never updated. Would that still make sense to exist in release-data or instead maybe just in this repo?

Yes it makes sense. If there is a script in release-data, even if we do not display the latest versions, we will at least be alerted that new releases must be documented (would be similar to #3323 (comment) for example). The process of documenting new releases is manual (for the time being), but relatively easy.

[captn3m0]

I would prefer separate pages for now, till we can decide on a schema for distinct identifiers for various release cycles. I created a discussion for that here: #3346

[jamietanna]

Thanks folks - so I guess we'd have i.e. aws-lambda-nodejs as the product, with nodejs12.x as a cycle?