Skip to content

Latest commit

 

History

History
58 lines (40 loc) · 2.4 KB

versioning.md

File metadata and controls

58 lines (40 loc) · 2.4 KB
Raw

Versioning

tezos-packaging follows all Octez releases, both stable and candidates.

Packages from our releases provide additional functionality (e.g. systemd services in Ubuntu and Fedora package or brew formulae with launchd services). This additional functionality may change within the same upstream version.

In order to track this, our GitHub releases and packages use the following RPM-like versioning scheme: <name>-<version>-<release>:

  • <name> is used to mention which Octez binary is packaged.
  • <version> is used to reference the packaged upstream version.
  • <release> is used to reflect changes in additional packages functionality.

Note that each <release> will be consistent across distribution methods ( corresponding to the same git commit), but may be partial in scope, affecting only some binaries in some distribution.

GitHub releases

Depending on the upstream <version>, on GitHub we provide:

  • releases for stable Octez releases
  • pre-releases for Octez release candidates

In our GitHub repository we use tags in which the <name>- part is omitted.

E.g. v11.0-1 is the first tezos-packaging release within the v11.0 upstream stable release, or v11.0-rc2-2 for the second tezos-packaging release within the v11.0-rc2 upstream release candidate.

GitHub {pre-}releases contain static binaries compiled from the given upstream source <version>. If any are applicable, they also contain brew bottles for macOS (see below).

Ubuntu packages

Ubuntu packages use a slightly different versioning scheme, which follows the Debian versioning policy: <name>-<version>-0ubuntu<release>~<ubuntu-version>.

E.g. tezos-client-11.0+no-adx-0ubuntu1~focal, where focal is 20.04 LTS.

We use different PPA repositories for stable and release candidate Ubuntu packages. You can read more about this in the doc about Ubuntu packages.

Fedora packages

We use different Copr projects for stable and release candidate Fedora packages. You can read more about this in the doc about Fedora packages.

Brew formulae

We use two distinct repository mirrors to provide stable and release candidate brew formulae. You can read more about this in the doc about macOS packaging.