-
-
Notifications
You must be signed in to change notification settings - Fork 803
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[new product] Deno #6449
base: master
Are you sure you want to change the base?
[new product] Deno #6449
Conversation
Thank you for opening this pull request 👍. If you are not familiar with the project, please check out our Contributing Guidelines and our Guiding Principles. Also take a look at our Hacking Guide if you intend to work on site internals. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few suggestions. We need a policy summary before we can merge.
Deno support policy can be found on the | ||
[Stability and releases documentation page](https://docs.deno.com/runtime/fundamentals/stability_and_releases/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There needs to be a clear summary of the upstream policy here, instead of just a link. Things to include:
- Release Cadence
- Support policy
- Stability Guarantee
- Release Channels, including the exact guarantees made by LTS releases.
- Versioning Policy(?). Does deno use semver?
- Standard Library stability.
https://endoflife.date/nodejs might be a good reference.
tags: javascript-runtime | ||
permalink: /deno | ||
versionCommand: deno --version | ||
releasePolicyLink: https://github.com/denoland/deno/releases |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
releasePolicyLink: https://github.com/denoland/deno/releases | |
releasePolicyLink: https://docs.deno.com/runtime/fundamentals/stability_and_releases/ | |
releaseImage: https://docs.deno.com/runtime/fundamentals/images/deno-lts-support.png |
- releaseCycle: "2" | ||
releaseDate: 2024-10-09 | ||
eol: false | ||
latest: "2.1.4" | ||
latestReleaseDate: 2024-12-11 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is v1 considered EOL? We should add v1 as well to the table.
Using eoas
might also be helpful to split between Deno versions receiving active development or only bugfixes.
Closes #4160
Adds Deno.
Note, I disrespected the YAML schema in
product-schema.json
, to keep it as close to the other products. The schema forces:auto
contents to be an array, and not havemethods
child key.releases[].latestReleaseDate
expects a date-time instead of a date.