Making Calvera release

note

This document is about creating a new release, if you just want to make some hot-fixes, add/update a tool on Calvera, please refer to another document

Versioning

We use the calendar version scheme for platform release: yy.mm.version. Version starts with 0 and increases when we do minor updates/fixes. We publish major releases about every three months.

Release process

Development repos

We have the following development repos:

• Galaxy
• Pulsar
• Remote Data Brokers
• Ingress Proxy
• Rucio protocols
• OIDC Utils

The process is:

1. Make sure that current version numbers are up-to-date
2. Make sure deployment repos are using these current versions (e.g. Calvera uses current version of Galaxy, Pulsar, ...)
3. Make sure main branch are up-to-date (merge with dev if needed) for
   • Galaxy
   • Pulsar
   • Remote Data Brokers
   • Ingress Proxy
   • Rucio protocols
   • OIDC Utils
4. Create git tags using current version number, e.g.

git tag 
git push origin --tags

Deployment repo

We now have a single repository for NDIP Platform deployment.

1. Make sure config version file for production and dev have correct versions.

2. Make sure main branch are up-to-date (merge with dev if needed), create tag

git tag 
git push origin --tags

Tools

Same procedure - merge main with dev, create tag.

Release notes

Create to pages for release notes - user facing (see example and developer notes (see example)). Use Make changelogs script to create list of MRs.