# Release process and schedule (/docs/release-notes/release-process)



BullSequana AI ships on a fixed release schedule. Platform engineers can use this page to plan upgrades and maintenance windows. Decision-makers can use it to see when a release becomes available, how long it receives patch releases, and how long it is supported.

## Release cadence [#release-cadence]

| Release type | Cadence                                       | Example      |
| ------------ | --------------------------------------------- | ------------ |
| Major        | Every six months                              | 2.0.0, 3.0.0 |
| Minor        | Monthly, between major releases               | 2.1.0, 2.2.0 |
| Patch        | When a fix is needed, within 3 weeks after GA | 1.2.1        |

Version numbers follow the `MAJOR.MINOR.PATCH` format. Every major and minor release publishes [release notes](/docs/release-notes) and an [upgrade guide](/docs/deployment/playbooks/upgrade-and-release-process) from the previous release. Upgrade through each release in order; an upgrade guide covers only the step from the release directly before it.

## Support and patch releases [#support-and-patch-releases]

* **Support window:** each release is supported for 10 months after GA on its tested Kubernetes versions, with a supported upgrade path to the current release.
* **Patch releases:** fixes, including security fixes, ship in the latest release. A release receives patch releases for 3 weeks after GA. After that, fixes are not backported to it.

Upgrade monthly to stay current with fixes.

## Release milestones [#release-milestones]

Each release passes through the same milestones. All milestone dates derive from the planned general availability (GA) date.

| Milestone                         | Timing             | What happens                                                                                                                                                                                                |
| --------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Planning                          | 6 weeks before GA  | The release scope is planned.                                                                                                                                                                               |
| Scope lock                        | 5 weeks before GA  | The release scope is fixed. Later changes to scope need an explicit decision.                                                                                                                               |
| Feature freeze                    | 2 weeks before GA  | Feature work for the release is complete. Remaining work covers fixes, tests and documentation.                                                                                                             |
| Code freeze and release candidate | 1 week before GA   | Release branches are cut on all repositories and versions are bumped to the release number. The release candidate goes through full QA qualification. Only release-blocking fixes enter the release branch. |
| Go/no-go review                   | 5 days before GA   | QA results and open defects are reviewed against the release criteria.                                                                                                                                      |
| Go/no-go final                    | 1 day before GA    | The final decision to publish the release is made.                                                                                                                                                          |
| GA                                | Release day        | The release, its release notes and its upgrade guide are published.                                                                                                                                         |
| End of patch releases             | 3 weeks after GA   | The release stops receiving patch releases. Later fixes ship in a newer release.                                                                                                                            |
| End of support                    | 10 months after GA | The support window closes. Upgrade to a supported release before this date.                                                                                                                                 |

Milestones from planning to end of patch releases fall on working days. A milestone that lands on a weekend or public holiday moves to the nearest working day.

## Release evidence [#release-evidence]

Platform releases follow semantic versioning from the `VERSION` file of the platform repository. A deployment uses an immutable release tag or commit, with the matching Portal, BSQAI API, image, and chart artifacts. A release branch that still receives fixes is not equivalent.

Keep these records as evidence for each deployed release: image-scan results, integration-test results, the release notes, the immutable manifest commit, backup evidence, and the completed upgrade validation record.

## Release calendar [#release-calendar]

Dates are planned and can change. Planning and go/no-go dates follow the offsets in [Release milestones](#release-milestones). The release notes announce each release when it reaches GA.

| Release       | Scope lock | Feature freeze | Code freeze | GA         | End of patch releases | End of support |
| ------------- | ---------- | -------------- | ----------- | ---------- | --------------------- | -------------- |
| 1.4.0         | 2026-08-28 | 2026-09-18     | 2026-09-25  | 2026-10-02 | 2026-10-23            | 2027-08-02     |
| 2.0.0 (major) | 2026-09-25 | 2026-10-16     | 2026-10-23  | 2026-10-30 | 2026-11-20            | 2027-08-30     |
| 2.1.0         | 2026-10-23 | 2026-11-13     | 2026-11-20  | 2026-11-27 | 2026-12-18            | 2027-09-27     |
| 2.2.0         | 2026-12-23 | 2027-01-15     | 2027-01-22  | 2027-01-29 | 2027-02-19            | 2027-11-29     |
| 2.3.0         | 2027-01-22 | 2027-02-12     | 2027-02-19  | 2027-02-26 | 2027-03-19            | 2027-12-26     |
| 2.4.0         | 2027-02-19 | 2027-03-12     | 2027-03-19  | 2027-03-26 | 2027-04-16            | 2028-01-26     |
| 3.0.0 (major) | 2027-03-19 | 2027-04-09     | 2027-04-16  | 2027-04-23 | 2027-05-14            | 2028-02-23     |
| 3.1.0         | 2027-04-16 | 2027-05-07     | 2027-05-14  | 2027-05-21 | 2027-06-11            | 2028-03-21     |
| 3.2.0         | 2027-05-14 | 2027-06-04     | 2027-06-11  | 2027-06-18 | 2027-07-09            | 2028-04-18     |

## Related pages [#related-pages]

* [Release notes](/docs/release-notes)
* [Upgrade 1.4.0 to 2.0.0](/docs/deployment/playbooks/upgrade-and-release-process)
* [Deployment sequence](/docs/deployment/playbooks/deployment-sequence)
