Skip to content

docs: automate release calendar updates #13821

@stirby

Description

@stirby

Right now, we have to manually append versions to the release calendar in our docs. It's easy to forget and tedious.

We should show: security (n-2), stable (n-1), mainline (n), the next minor release (n+1) and the latest three versions that we don't support.

Release schedule (now)

Release name Release Date Status
2.8.x February 06, 2024 Not Supported
2.9.x March 07, 2024 Not Supported
2.10.x April 03, 2024 Not Supported
2.11.x May 07, 2024 Security Support
2.12.x June 04, 2024 Stable
2.13.x July 02, 2024 Mainline
2.14.x August 06, 2024 Not Released

Release schedule (next)

Release name Release Date Status
2.9.x March 07, 2024 Not Supported
2.10.x April 03, 2024 Not Supported
2.11.x May 07, 2024 Not Supported
2.12.x June 04, 2024 Security Support
2.13.x July 02, 2024 Stable
2.14.x August 06, 2024 Mainline
2.15.x September 02, 2024 Not Released

Metadata

Metadata

Assignees

Labels

docsArea: coder.com/docsdocs/engdocs auto-generated content

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions