Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: maas-ui integration #5338

Merged
merged 1 commit into from
Mar 12, 2024
Merged

docs: maas-ui integration #5338

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,11 @@
# Release Process

## MAAS UI Integration with MAAS

- Whenever changes are pushed to `main` or `3.x` branch, a new JavaScript bundle is automatically created and pushed to the [Ubuntu assets server](https://assets.ubuntu.com/manager?tag=auto-upload&q=maas&type=tar.gz). This process is managed by the [upload.yml](https://github.com/canonical/maas-ui/blob/main/.github/workflows/upload.yml) GitHub Action.

- MAAS integrates the MAAS UI using this JavaScript bundle. For the main development branch (latest/edge), MAAS automatically pulls the latest bundle and creates a commit, triggering a new MAAS release.

## Tracking MAAS core

When MAAS core releases an initial release candidate (e.g. `2.8.0-rc1`), a corresponding branch of maas-ui named after the MAAS
Expand Down
Loading