---
slug: /governance
title: Governance
question: How does a change to ABI get decided, released, and supported?

---

# Governance

ABI is MIT licensed. The source and the issues live in [jupyter-naas/abi](https://github.com/jupyter-naas/abi).

## How a decision is recorded

A change to a boundary, an ownership, cross-cutting configuration, or a major trade-off gets an architecture decision record (ADR). Each ADR is a page of this site, named `YYYYMMDD_topic.md`, with Status, Date, Context, Decision, and Consequences. The ABI repository does not keep them. The list is [Decision records](/developer-guide/adr).

## How a change lands

A change follows [Contribute to ABI](/developer-guide/contributing/overview) and passes `make check` and the tests of what it touched ([Testing](/developer-guide/contributing/testing)). A change to a command, a config key, or a behaviour updates its docs page in the same PR.

## How a release is cut

The commit type sets the version: `fix:` is a patch, `feat:` is a minor, a `BREAKING CHANGE:` footer is a major. A push to `main` releases stable packages, and a push to `dev` releases prereleases. The order is on [Releasing](/developer-guide/releasing/release-process).

## What is supported

3.0 is the current line. The `v2` branch takes bug fixes and security fixes only, until 2027-01-31. See [v2 support](/user-guide/upgrade/v2-support) and [Migrate from 2.x to 3.0](/user-guide/upgrade/migrate-to-3).

## Where to report

Bugs and requests go to [GitHub issues](https://github.com/jupyter-naas/abi/issues). Security reports go to [security@naas.ai](mailto:security@naas.ai), as set out in the [Security policy](/governance/security-policy). Which terms apply to ABI and to Naas services is on [Terms and conditions](/governance/terms).