search

SIMPLE-AstroDB / SIMPLE-db

BSD 3-Clause "New" or "Revised" License
11 stars 22 forks source link

Release Number #263

Closed Will-Cooper closed 2 years ago

Will-Cooper commented 2 years ago

Create a release number and micro releases for each version of the database to be passed to the website (https://github.com/SIMPLE-AstroDB/SIMPLE-web/issues/98)

dr-rodriguez commented 2 years ago

The easiest way to do this is to use the github/git release/tag structure. So every major pull request (or whenever we choose) we can tag a release on github and we're good to go. An alternative is to store a release table in the database itself. That is a bit trickier to handle, particularly since it'll need frequent and potentially manual updating, so my recommendation is an explicit release via github.

If we wanted to be extra fancy we could update some of our scripts so the database copy used by the website comes from the latest tagged release.

kelle commented 2 years ago

Proposed current workflow:

Consider having SIMPLE-web only load released versions and not dev versions.

kelle commented 2 years ago

Referring to https://calver.org/, we've decided to version control YYYY.minor. E.g., the first releases in 2022 would be 2022.1, the next one would be 2022.2 and so on. We can have as many releases in a year as we want.

kelle commented 2 years ago

The un-released version is called latest and doesn't get a version number until it is released.