Release process and schedule

How often BullSequana AI releases, the milestones each release passes through, and the planned release calendar.

Agentic Friendly

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 typeCadenceExample
MajorEvery six months2.0.0, 3.0.0
MinorMonthly, between major releases2.1.0, 2.2.0
PatchWhen a fix is needed, within 3 weeks after GA1.2.1

Version numbers follow the MAJOR.MINOR.PATCH format. Every major and minor release publishes release notes and an upgrade guide 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 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

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

MilestoneTimingWhat happens
Planning6 weeks before GAThe release scope is planned.
Scope lock5 weeks before GAThe release scope is fixed. Later changes to scope need an explicit decision.
Feature freeze2 weeks before GAFeature work for the release is complete. Remaining work covers fixes, tests and documentation.
Code freeze and release candidate1 week before GARelease 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 review5 days before GAQA results and open defects are reviewed against the release criteria.
Go/no-go final1 day before GAThe final decision to publish the release is made.
GARelease dayThe release, its release notes and its upgrade guide are published.
End of patch releases3 weeks after GAThe release stops receiving patch releases. Later fixes ship in a newer release.
End of support10 months after GAThe 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

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

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

ReleaseScope lockFeature freezeCode freezeGAEnd of patch releasesEnd of support
1.4.02026-08-282026-09-182026-09-252026-10-022026-10-232027-08-02
2.0.0 (major)2026-09-252026-10-162026-10-232026-10-302026-11-202027-08-30
2.1.02026-10-232026-11-132026-11-202026-11-272026-12-182027-09-27
2.2.02026-12-232027-01-152027-01-222027-01-292027-02-192027-11-29
2.3.02027-01-222027-02-122027-02-192027-02-262027-03-192027-12-26
2.4.02027-02-192027-03-122027-03-192027-03-262027-04-162028-01-26
3.0.0 (major)2027-03-192027-04-092027-04-162027-04-232027-05-142028-02-23
3.1.02027-04-162027-05-072027-05-142027-05-212027-06-112028-03-21
3.2.02027-05-142027-06-042027-06-112027-06-182027-07-092028-04-18

On this page