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.
In addition, all changes made to the code have a unique identifier of
the form <last-release>-XX-gZZZZZZZ where XX is the number of changes
since the last release, and ZZZZZZZ is a unique identifier given to
each commit by Git.
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 consist of the following components:
- On http://git.chromium.org/gitweb/?p=webm/libvpx.git
- a tag in the Git repository
- On http://code.google.com/p/webm/downloads
- a snapshot of the Git repository, taken from the tag
- a source and binary distribution for the Windows platform, for use with Visual Studio
- On http://www.webmproject.org
- documentation update, if the API has been changed
- list of changes since the last release