Skip to content
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

host dart's 'release policy' verbiage #6470

Closed
1 task
devoncarew opened this issue Mar 3, 2025 · 3 comments · Fixed by #6471
Closed
1 task

host dart's 'release policy' verbiage #6470

devoncarew opened this issue Mar 3, 2025 · 3 comments · Fixed by #6471
Assignees
Labels
a.install Relates to installing Dart or the archive. a.rn.release-notes Relates to Dart release notes found on dart.dev co.request Community ask for documentation d.enhancement Improves docs with specific ask e0-minutes Can complete in < 60 minutes of normal, not dedicated, work from.user Issue raised by user p1-high Major but not urgent concern: Resolve in months. Update each month.

Comments

@devoncarew
Copy link
Member

devoncarew commented Mar 3, 2025

What information needs to be added?

We'd like to host Dart's release policy on dart.dev. The text should be similar to:

Each major Dart release is supported until there is a newer stable release. On average, we ship a new stable release every 3 months. We fix critical issues, including critical security problems, in supported releases as needed by issuing minor revisions (for example, Dart 3.7.1, Dart 3.7.2, and so on). Once we ship a new stable release (for example, Dart 3.8.0), we no longer patch previous stable releases.

The section header should be Release Policy or very similar, and it would be great to have an anchor so that this is directly linkable (additionally, a short go link would be great - dart.dev/go/release-policy or similar).

cc @antfitch

Where should this new content appear?

I'm not sure of the page; I believe https://dart.dev/get-dart and https://dart.dev/get-dart#release-channels have been suggested? It should be easy to find on a page, and, people looking for something like a release policy should be able to roughly guess what page it might be on.

I would like to fix this problem.

  • I will try and fix this problem on dart.dev.
@devoncarew devoncarew added co.request Community ask for documentation from.user Issue raised by user labels Mar 3, 2025
@parlough parlough added d.enhancement Improves docs with specific ask p1-high Major but not urgent concern: Resolve in months. Update each month. e0-minutes Can complete in < 60 minutes of normal, not dedicated, work a.rn.release-notes Relates to Dart release notes found on dart.dev a.install Relates to installing Dart or the archive. labels Mar 3, 2025
@parlough
Copy link
Member

parlough commented Mar 3, 2025

@antfitch would you like to add this or would you like me to?

I think a new section titled ## Release policy on the SDK overview page would make sense, with a cross-link from the intro/overview section on the Get dart page.

And as for a redirect, do use /to/release-policy rather than /go/....

Not necessary for this issue, but I think this new section could also link to the breaking changes page.

@antfitch antfitch self-assigned this Mar 3, 2025
@antfitch
Copy link

antfitch commented Mar 3, 2025

@parlough, absolutely. Send it my way when you need a review.

@antfitch antfitch assigned parlough and unassigned antfitch Mar 3, 2025
@devoncarew
Copy link
Member Author

As an update, we'd like to refer to this as our 'Support policy'; cc @mit-mit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a.install Relates to installing Dart or the archive. a.rn.release-notes Relates to Dart release notes found on dart.dev co.request Community ask for documentation d.enhancement Improves docs with specific ask e0-minutes Can complete in < 60 minutes of normal, not dedicated, work from.user Issue raised by user p1-high Major but not urgent concern: Resolve in months. Update each month.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants