Understanding the Concept of Releases

We are living in an ever changing world. So does the concept of DevOps bring an always improving string of changes and updates to our applications. To cope with this, we have introduced the concept of releases.

A release lets you freeze the legal settings as well as the assembly (list of components) for a particular module. This will allow you to continue development on that module while providing a static set of it for compliance approval or external usage.

Especially when using an "Inner Source" approach, this is a suitable way to inform your organizational members and followers of the module about a new version.

How to create a release?

To create a release, select the the module you want to release. On the details card you will find a button in the action section that will create a snapshot of the scan as well as the legal settings and store them for later use. In this step you may assign a freehand version number for better identification.

PLEASE NOTE: we highly recommend to create releases only from modules that are suitable for a compliance approval Compliant means that all licenses are in OK state.

Releases may be forwarded for compliance approval. Learn more about approvals here.

A release is the prerequisite for assigning and publishing a Bill of materials key.