search

tomatenquark / code

The code that powers Tomatenquark
https://tomatenquark.github.io/
Other
34 stars 5 forks source link

Mark continuously deployed releases as stable releases #55

Closed Calinou closed 4 years ago

Calinou commented 4 years ago

Marking them as pre-releases prevents them from appearing in the "latest Release" view on the GitHub repository. Moreover, it made the /latest URL point to an old version (0.1.9).

In the future, we should also edit previous releases so they're marked as stable.

Fohlen commented 4 years ago

@Calinou this is actually by intention. Sometimes we do releases that are intended for testing purposes only and not for public use yet.

Calinou commented 4 years ago

@Fohlen I see; I thought these were actually intended to be stable releases. In this case, it might be better to distinguish them by adding a beta1 suffix to their tag or something like that.

We can't do that retroactively, so we'd only do it for future tags.

Fohlen commented 4 years ago

Seems appropriate. How about 0.2.0-alpha. We can even use the CI/CD pipeline to mark releases as ready depending on if they have a suffix!

Calinou commented 4 years ago

@Fohlen Sounds good to me :slightly_smiling_face: