- Overview
- Users
- Managing Models and Releases
- Uploading Artifacts
- Creating a Model
- Completing the Model
- Creating a Release
- Uploading Files
- Uploading Images
- Using a Model
- Requesting Access
- Personal Access Tokens
- Using a a Pushed Docker Image
- Downloading files
- Reviews
- Reviewing Releases and Access Requests
- Reviewing a Release
- Reviewing an Access Request
- Reviewed Releases and Access Requests
- Releases
- Access Requests
- Programmatically using Bailo
- Authentication
- Open API
- Webhooks
- Python Client
- Administration
- Getting Started
- App Configuration
- Microservices
- File Scanners
- Helm
- Basic Usage
- Configuration
- Isolated Environments
- Schema
- Create a Schema
- Upload a Schema
- Migrations
- Bailo v0.4
- Bailo v2.0
- DataBase Scripts
What is a Release?
A release is a different version of a model and there can be multiple released versions from the same model. Having a release gives you the opportunity to make alterations, e.g. updates, adding new features etc, without affecting or interfering with the original state of the model.
How are the Releases reviewed?
Releases are reviewed by who the owner has chosen, to be the Model Technical Reviewer and the Model Senior Responsible Officer. See Completing The Model for more details.
Who can create one?
Only the owner of the uploaded model can create a release.
Approval process and roles
When the Model Technical Reviewer and Model Senior Responsible Officer review a release, one or both will leave a request for changes and/or approve. When approved by both roles, the release will be moved to Archived.
See here on how to do this in Python.
Copyright © Crown Copyright 2025.