docs: SLA page and unstable for prereleases #3195
Conversation
✗ The generated branch has been deleted.If the PR has been merged, you can check the generated code on the |
|
It added |
yes it's expected to highlight that the non-released versions are not supported, wdyt? |
| if (active !== null) { | ||
| if (active < queryEnd && end > queryStart) { | ||
| - output.push({ name, type: 'active', start: active, end }); | ||
| + output.push({ name, type: isPreRelease ? 'unstable' : 'active', start: active, end }); |
There was a problem hiding this comment.
is unstable a common word for releases ? I feel like DEVELOPMENT and MAINTENANCE would be more suitable
There was a problem hiding this comment.
I've used the same as for https://nodejs.org/en/about/previous-releases
maintenance in our SLA policy means that there's no features but fixes will be delivered
website/static/img/dart-sla.png
Outdated
There was a problem hiding this comment.
for dart main is stable, its the lastest
There was a problem hiding this comment.
yes but here main refers to the unreleased versions, so non stable you know the commits in between releases
🧭 What and Why
🎟 JIRA Ticket: https://algolia.atlassian.net/browse/DI-2453
Changes included:
-ggflag for the release, in order to generate the current state PNGs