- 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 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
Reviewed Releases
What is a release?
A release represents a specific version of a model. Multiple releases can exist for the same model, allowing changes without affecting earlier versions.
How are releases reviewed?
Release reviewers are assigned by the model owner, typically including:
- Model Technical Reviewer
- Model Senior Responsible Officer
See Completing The Model for details.
Who can create a release?
Only the owner of the model can create releases.
Approval process
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.
An example Python workflow is available here.
Copyright © Crown Copyright 2026.