Overlapping LTS releases

[tjconcept]

I'm not sure if this is the right place, but couldn't find anywhere else.

I just read the Deno 2.0 blog post, showing the upcoming release schedule, and was surprised to see LTS versions not having any overlap.

Basically, what I'm aiming for is; always running the most stable (often means "oldest") version still receiving security patches. I currently practice this in Node.js by jumping from LTS to LTS. As an example, I would not want to run into nodejs/node#54543 in production.
Node.js LTS overlaps provide plenty of migration time.

If overlapping LTS versions is not the strategy for Deno, what's the recommendation?

[junderw]

Currently NodeJS LTS releases

• Spend about 1 year as the current version getting active development.
• Then 1 year as active LTS with backporting of most major non-breaking features.
• Then 1.5 years as maintenance LTS only receiving security fix backports.

The total lifetime of an LTS release is about 3.5 years. The first 2 years of which overlap with the previous LTS's active and maintenance phases. And in fact a 1 year overlap with 2 LTS versions prior.

Current deno overlap as per the blog:

• 1 month active development
• 5 month security fix backports
• If you want new features, wait until the next LTS or use one of the 1 month long minor releases.
• 1 month overlap between the active month and the last month of the previous LTS security fix backport period.

---

Please let me know if my summary is inaccurate.

I think that having a larger overlap and more time to migrate between LTS, and having a longer LTS lifetime overall would be the goal eventually, but for now what they've announced is infinitely better than no LTS at all.

Great job on the releases to the deno team, btw.

[bartlomieju]

@junderw this summarizes what we plan well - so in other words, the current plan is to have one month overlap between LTS releases.

@tjconcept I understand your concerns and the schedule might be adjusted in the future, for now we're focused on acting on the feedback from Deno 2.0 release and working towards the 2.1 release which will be the first LTS release.