Releases
This page describes how we version our releases.
libvpx
Version Numbering
The codec library is numbered using a standard three digit major, minor, patch scheme.
-
The major digit will be updated whenever a change is made that breaks the ABI. That is, whenever it would require recompiling your application to use the new version of the library. We understand the impact of these changes, and in general will make them only to add functionality that could not be provided by the existing API.
-
The minor digit will be updated whenever a new feature is added or a substantial improvement is made to the software.
-
The patch digit may be updated when there has been no substantial change in the software, but we need to issue a new release, for example to fix a bug.
Moving Forward
In general, we do not plan to backport changes other than security critical ones to older releases, but patches that do so are welcome.
Release Contents
libvpx releases correspond to Git version tags set in the repository, of the general form v#.#.#, where #.#.# is the version number.
Published tags/releases can be listed in your local repo clone with git tag -l, or in the repo web interface at https://chromium.googlesource.com/webm/libvpx.
The web interface also offers auto-generated tarballs of each release, at URLs of the pattern https://chromium.googlesource.com/webm/libvpx/+archive/ + v#.#.#.tar.gz
Example:
https://chromium.googlesource.com/webm/libvpx/+archive/v1.7.0.tar.gz