Release management

Intended audience

This guide is intended for maintainers and developers of InvenioRDM itself.

Scope

The guide covers how to release a new version of InvenioRDM.

Overview

We follow semantic versioning. In particular:

• 0.y.z is for initial development - anything may change at any time.

InvenioRDM consists of:

• a CLI tool,
• an instance template,
• an application, and
• many modules.

Tool versioning

The Invenio-CLI tool is intended to be able to work with many different application versions, and multiple products (RDM, ILS, ...), and is therefore independently versioned.

Application versioning

The instance template (Cookiecutter-Invenio-RDM) and the application (Invenio-App-RDM) is together considered the application and therefore versioned together.

The application locks each dependent module to their major-level versions so that patches can be distributed without breaking compatibility.

Module versioning

Each module (e.g. Invenio-RDM-Records, Invenio, ...) is versioned independently. Each module MUST follow semantic versioning, so that the application can lock the module version to the major-level release.

Release checklist

Initial iteration

In the beginning of each iteration we start by releasing new development versions of the below modules in the order they specified:

• flask-resources GitHub (if needed)
• marshmallow-utils GitHub (if needed)
• invenio-records-permissions GitHub (if needed)
• invenio-records-resources GitHub
  • bump flask-resources
  • bump marshmallow-utils
  • bump invenio-records-permissions
• invenio-drafts-resources GitHub
  • bump invenio-records-resources
• invenio-vocabularies GitHub
  • bump invenio-records-resources
• invenio-requests GitHub
  • bump invenio-records-resources
• invenio-administration GitHub
  • bump invenio-records-resources
  • bump invenio-vocabularies
• invenio-communities GitHub
  • bump invenio-administration
  • bump invenio-requests
  • bump invenio-vocabularies
• invenio-rdm-records GitHub
  • bump invenio-administration
  • bump invenio-drafts-resources
  • bump invenio-vocabularies
  • bump invenio-communities
• react-invenio-forms GitHub
• react-invenio-deposit GitHub
  • bump react-invenio-forms
• invenio-app-rdm GitHub
  • bump invenio-rdm-records
  • bump react-invenio-deposit
  • bump react-invenio-forms
• cookiecutter-invenio-rdm GitHub
  • bump invenio-app-rdm

For modules in v0.X.Y, the new version is v0.(X+1).0.

For modules in vX.Y.Z, the new version is v(X+1).0.0.dev0.

Pre-release

• Ensure all dependent modules have been released.
• Release Invenio-App-RDM (removing the pre-release suffix - e.g. dev0).
• Cookiecutter-Invenio-RDM:
  • Merge everything to master.
  • Create a new version branch from master using the pattern vX.Y (e.g., if Invenio-App-RDM is v1.0.0, then the branch should be named v1.0).
• Write release notes in dev branch, check the dev site. Then merge to master@docs-invenio-rdm.

Release

The final step to release the new modules and source code is to release Invenio-CLI. Releasing Invenio-CLI, will make all new installation use the latest released packages.

• Invenio-CLI:
  • Update Cookiecutter-Invenio-RDM branch version in the source code.
  • Bump version of Invenio-CLI and release.

Post-release

• Deploy InvenioRDM to QA and PROD (demo website AND docs).
• Check if the release announcement should be updated in the homepage of this doc.
• Blog post (including adding a link under https://inveniosoftware.org/products/rdm/#status)
• Website update
  • Update public roadmap.
  • Review project information
  • Subtitle under https://inveniosoftware.org/products/rdm/ title.
• Project tracking:
  • GitHub: Update internal product roadmap
• Create maintenance branches of supported modules (LTS releases only). See branch management.

Release a Python or JavaScript package

• Ensure all changes are merged in master branch on GitHub.
• Checkout master branch and make sure it's identical to GitHub.

  git checkout master
  git reset --hard upstream/master
  

• Bump version number:
  • Python: <package>/version.py
  • JavaScript: package.json and package-lock.json.
• Commit on master:

  git add <package>/version.py
  git commit -m "release: vX.Y.Z"
  

• Tag and push (both master and tag)

  git tag vX.Y.Z
  git push upstream master vX.Y.Z
  

Maintenance releases

Maintenance releases follow the same workflow as a new version release. You only need to replace master with maint-x.y branches.

Warning

Be aware that when the independent modules are released, they will be picked up immediately by new InvenioRDM installations. This should not be an issues since the releases MUST be backward compatible.