You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 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.
The text was updated successfully, but these errors were encountered:
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:
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 likev0.11.1
. There are several benefits to this: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.
The text was updated successfully, but these errors were encountered: