Release management & versioning - proposal

This section gives an overview of the proposed handling of API versions and their handling in the release management process.

Highlights of the proposal

• Use of CAMARA internal work-in-progress (-wip.m) and release-candidate (-rc.n) API versions (with version extensions) for release management purposes
• No use of alpha or beta extensions (internal nor external to CAMARA) as no clear definition is identified.
• Externally released APIs (public-release API versions of a meta-release) only have API version number x.y.z (semver 2.0), no version extension
• People are free to use pre-release API versions available in the CAMARA GitHub at their own risk.
• API families are not versioned, nor release-managed, only API versions are release-managed

It consolidates inputs from 

• Rafal's proposal for the CAMARA API Maturity Levels - proposal - CAMARA Project - Confluence.
• the inputs from Consolidation Issue for open points release management · Issue #9 · camaraproject/ReleaseManagement (github.com).
• Proposal to establish API Families as Working Groups across API Sub Projects · Issue #7 · camaraproject/ReleaseManagement (github.com)
• Open Issues Consolidated - CAMARA Project - Confluence

This page was briefly discussed on the RM call of 2024-03-19. Initial feedback was:

• use work in progress "-wip.n" and release candidate "-rc.n" extensions instead of alpha and beta as the latter are not easy to define. These extensions should be only used internally in CAMARA for release management, but not in externally released APIs, which should only have semver numbers.
• API implementers are free to use these pre-release versions as they see fit, but there is no guarantee from CAMARA side that they will not change. 

Table of Contents

Definitions

API version

The API version is defined in the "version" field of the OAS definition of an API. Its content must follow Semantic Versioning 2.0.0 | Semantic Versioning (semver.org).

An API version has the format:  x.y.z  where x, y and z are numbers corresponding to MAJOR, MINOR and PATCH releases.

The following bullets are extracted of the semver 2.0 specification (and links to the corresponding spec item):

• Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable. https://semver.org/#spec-item-4
• Version 1.0.0 defines the public API. The way in which the version number is incremented after this release is dependent on this public API and how it changes. https://semver.org/#spec-item-5

  • Patch version Z (x.y.Z | x > 0) MUST be incremented if only backward compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior. https://semver.org/#spec-item-6

  • Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backward compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated. It MAY be incremented if substantial new functionality or improvements are introduced within the private code. It MAY include patch level changes. Patch version MUST be reset to 0 when minor version is incremented. 

  • Major version X (X.y.z | X > 0) MUST be incremented if any backward incompatible changes are introduced to the public API. It MAY also include minor and patch level changes. Patch and minor versions MUST be reset to 0 when major version is incremented.

Precedence example:  1.0.0 < 2.0.0 < 2.1.0 < 2.1.1.

The CAMARA API guidelines describe the applicable versioning strategy. NOTE: if this proposal is accepted, some updates of the guidelines may be needed.

API version extensions 

During the API development and release preparation, "work-in-progress" (-wip) or "release-candidate" (-rc) extensions shall be used to identify intermediate pre-releases of an API.  

The notions of work-in-progress and release-candidate API versions and the related API version extensions are INTERNAL to the CAMARA project and used only for the release management process.

The API version extension is added to the "version" field of the OAS definition of an API. Its content must follow the here described syntax and semantics.

The following API version extensions shall be used in the API version:

• work-in-progress API versions: -wip.m
• release-candidate API versions: -rc.n
• no extension - this is allowed only for initial API versions 0.y.z, and only until the first work-in-progress API version 0.y.z-wip.1 has been created.

Extensions are post-fixed to the API version numbers and separated from it by a hyphen "-". m and n are numbers.

Precedence example: 1.0.0-wip.1 < 1.0.0-wip.2 < 1.1.0-wip.1 < 1.1.0-wip.2 < 1.1.0-rc.1 < 1.1.0-rc.2 < 1.2.0 (public-release)

NOTE: a public-release API version shall have no extensions, only the major.minor.patch version number as described in the previous section.

NOTE: alpha and beta extensions shall not used (as no clear criteria are identified). Only the extensions needed for release management shall be used.

API version in URL

The API guidelines contain the following approach for defining the API endpoint URL:

servers:
  - url: "{apiRoot}/qod/v2"
    variables:
      apiRoot:
        default: http://localhost:9091
        description: API root

Once a public-release API version is created and externally published as part of a meta-release, the API version in the URL of a released API shall ONLY contain the MAJOR digit of the API version, e.g. "v2" in the above example.

The apiRoot is to be adapted by the implementer of the API endpoint (the API provider).

Before API public release, the API definition and endpoint implementation may reflect the extension of the API in the URL, but without any hyphen or dots. 

Example: in the URL the version is v2wip1 for API version 2.y.z-wip.1

This simplifies testing of the API implementations during API development.

initial API version

• Initial API versions only exist for new APIs. They are API versions 0.y.z. (without extension).
• Initial API version may exist for several minor version numbers but should at some point become a first work-in-progress API version 0.y.z-wip.1
• No further initial API versions may be created once the first work-in-progress API version 0.y.z-wip.1 has been created for the API.
• Once a first public-release API version has been created, no further initial API versions are allowed.

work-in-progress (wip) API version

• A work-in-progress API version (extension -wip.m) is an intermediate, pre-release API version with changes with respect to the latest public-release API version.
• The purpose of a -wip API version is to test an evolution of the API by the developer community.
• A work-in-progress API version provides the relevant wip items of the release checklist.
• A work-in-progress API version cannot be part of a CAMARA meta-release. 
• It needs to go through the below API pre-release and release steps first.
• A work-in-progress API version can be used by testers of the API

release-candidate (rc) API version

• A release-candidate API version (extension -rc.n) is a pre-release version of an API with stabilized changes with respect to the latest public-release API version.
• The purpose of a pre-release API version is to provide a more stable version and prepare the API readiness for public-release as part of a meta-release.
• A release-candidate API version provides the relevant rc items of the release checklist.
• A release-candidate API version cannot be part of a CAMARA meta-release. 
• For a release-candidate API version to be accepted for public-release in a given meta-release, it needs to provide all the public-release items on the release checklist.
• Once the release-candidate API version is approved by the release management process for publication as part of a meta-release, the public-release API version is created.

public-release API version

• A public-release API version (x.y.z with x>0) is a major/minor/patch stable version of an API published as part of a meta-release.
• A public-release API version provides the relevant public items of the release checklist.
• A next public-release API version is introduced if there are updates to the API definition (major/minor/patch).
• The update of a public-release API version needs to be carefully announced and discussed with API consumers.
• A public-release API version is part of a CAMARA meta-release

release

An API release is either a pre-release or a public-release version of an API.

pre-release

A pre-release version of an API is any of the following API versions

• an initial API version 0.y.z
• a work-in-progress API version (x.y.z-wip.m)
• a release-candidate API version (x.y.z-rc.m).

NOTE: the term pre-release here is defined to includes more API versions than just the API versions that have a GitHub release package with a "pre-release" tag on it, which only concerns release-candidate API versions.

public-release

A public-release version of an API is an API version published externally to CAMARA as part of a meta-release.

NOTE: all CAMARA pre-release API versions are also publicly available and can be used, but changes may happen to such pre-release API versions without notice.

meta-release

A meta-release is a set of API versions made publicly available at a given point in time (September and March).

All API versions of a given meta-release shall be using the Commonalities and Identity and Consent Management releases that are part of that same meta-release.

Releasing API versions

API version throughout the release process

The following picture gives an overview of the API versions that an API can go through from inception to release.

The following section describe the details on naming, release assets, and the steps to produce a public-release API version as part of a meta release.

API release assets & naming conventions

During the development, release preparation and release of an API version, multiple intermediate pre-releases for initial, work-in-progress or release-candidate API versions may be created, and a final public-release API version is created.

A release creation results in an associated set of API release assets.

For a given API version, its release consists in creating the following set of API release assets:

• the API version in the OAS version field in the API definition file
• the API major version in the URL defined in the API definition file
• the Github branch for the API version: apiname-x.y.z, with extension as applicable
• the API version tag on that branch apiname-vx.y.z, with extension as applicable
• a GitHub release package, tagged "latest" or "pre-release", containing the API Sub-project repo for the branch

In case of multiple APIs managed in the same API Sub-project, each API shall be developed in a separate folder.

Release are handled per API, and the apiname is part of the branch and tags names to distinquih releases of APIs in the same API family.

To create an API version (pre-)release, the API (pre-)release assets need to be created with naming rules as indicated in the below table.

This is illustrated in the following figure:

The following rules shall apply: 

• With the exception of initial API versions, all pre-release API versions must have an API extension.
• An initial or work-in-progress API version may have a GitHub release package, which must have the "pre-release" tag
• A release-candidate and public-release API version must have a GitHub release package
• Only the latest release packages of an API version may have the tag "latest".

Special case: initial API versions (0.y.z)

A newly introduced API is in the main branch and has API version 0.1.0.

The API version v0.y.z handling is slightly different from API versions > 0, as one or more working branches for initial API versions may be created differing in the minor version number during initial API development in the v0 context without creating GitHub release packages for these branches.

Examples: release-0.1.0 < release-0.1.1< release-0.2.0 < release-0.2.1 < release-0.3.0, etc. without creating release packages for these branches

Once an API version 0.y.z is deemed sufficiently stable, a first release-0.y.z-wip.1 branch shall be created with the corresponding GitHub release package.

From this point onward, the below API (pre-)release steps apply.

The first public release of an API version 0.y.z results in API version 1.0.0.

Preparing an API (pre-)release

An API Sub-project can create as many initial or work-in-progress API versions as they want during API development in preparation for the release.

For API version > v0, the next API version number is defined and does NOT change during API development and release preparation. Only the API version extensions and their numbers may change. 

To prepare the release of an API version, one or more release-candidate API versions MUST be created as follows:

• At the M3 release milestone: when the API is agreed stable for release by the API Sub-project.
• At the M4 release milestone: the final release-candidate API version is delivered for meta-release approval.

Releasing an API

A public-release API version is created when the release-candidate API version is approved for a meta-release.

• At the M5 release milestone, the final API version (without any extension) is created with its release package, and included in the meta-release.

Updating an API

Updates to a public-release API version need to be carefully planned.

To manage updates of API versions, the semver 2.0 versioning applies to the API version number as follows:

• changes in the major number when creating non-backward compatible changes to the API
• changes in the minor number when creating backward compatible changes to the API
• changes in the patch number when correcting an error of the API

During the development of an API version update, all pre-release API versions need to get a version extension so its release can be managed properly.

Example for a backward-compatible update of a public-release API version 1.0.0, resulting in API version 1.1.0:

• Develop the 1.1.0 update on the main branch
• Once sufficiently stable, create a new branch release-1.1.0-wip.1. 
• Several intermediate wip branches may be created with or without release packages,
• Then one or more intermediate release-candidate API versions (rc branches + release packages) may be created (see example table below).
• The last release-candidate API version will be proposed for meta-release. 
• After meta-release approval, create the release-1.1.0 branch and release package ("latest") for the new public-release API version 1.1.0.

API family

The notion of API family will not be managed as part of release management. CAMARA releases only consider API versions.

It is recommended to adopt the proposal to make the API family a working group, and have the API sub-project focus on the development of one or more APIs.

See Herbert's proposal here: Proposal to establish API Families as Working Groups across API Sub Projects · Issue #7 · camaraproject/ReleaseManagement (github.com)

This will reduce the number of meetings and reporting load with the increasing number of APIs, and facilitate moving APIs from one family to another, or combining APIs from multiple families into into into family.

NOTE today, there is a situation where multiple API files are managed in one release package - these should ideally be moved into their own subproject (under one API working group) so that individual release packages can be created, unless there is a way to constrain a Github release package to subset of s a repository ?

API release checklist

NOTE: This proposal can be fed back into GitHub as needed.

The following table identifies the items that need to be provided for an API version for a particular release.

It is intended as a checklist for the API sub-projects to prepare an API version release.

In addition the following are the release assets that need to be provided to support the release of an API version:

Examples

The following are examples of the API release asset naming for the various API versions throughout the API version's lifecycle. 

API version 0.y.z (initial API development and first release)

API version x.y.z (x>0) (public-release API updates)

The following table illustrates the usage of versions and version extensions throughout the API lifecycle for the 3 different types of update: minor, major, patch.

Minor update of API version

Patch update of API version

Major update of API version