-
Notifications
You must be signed in to change notification settings - Fork 349
Open
Labels
DocumentationinfraIssues related to CI, Gerrit, cuelang.org, GitHub, etcIssues related to CI, Gerrit, cuelang.org, GitHub, etc
Description
For example, assuming that the latest release is currently v0.12.0 and that we already have v0.13.0-alpha.2 out for the next release cycle:
- v0.13.0-alpha.2 (pre-release) - 2025-03-25
- v0.12.0 - 2025-01-30
- v0.11.1 - 2024-12-18
- v0.11.0 - 2024-11-19
- v0.10.0 ...
This could be limited to five or so entries, but one should be able to click through to see the full history of full releases, i.e. feature releases like v0.11.0 and bugfix releases like v0.11.1. There are several benefits to this:
- It makes finding older release notes much easier. Going to https://github.com/cue-lang/cue/releases means having to go through pages and pages of releases; I can't see past v0.11.0-alpha.4.
- It makes upgrading through multiple versions of CUE, e.g. from v0.10.0 to v0.12.0, easier - as one can quickly go read the changelogs for v0.11.0 and v0.12.0 without having to skip over all the alphas and RCs in between.
- It helps remind users what the latest version of CUE is, as well as whether there is a newer alpha or RC they should try to provide feedback.
I would suggest that this go at the landing page, given how important this information is, but I don't oppose this living elsewhere if it is linked to from the main page - for example via a banner or some bit of UI near the top.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
DocumentationinfraIssues related to CI, Gerrit, cuelang.org, GitHub, etcIssues related to CI, Gerrit, cuelang.org, GitHub, etc