WPE WebKit follows a 6-month development cycle:
WPE WebKit and WebKitGTK share a fair amount of code. Therefore, both projects produce their feature releases simultaneously, and share the same release branches. For bug fix releases, the release teams for both projects try to sync their version numbers as well as they can.
Version numbers follow the
major.minor.patch numbering scheme. Changes to
major version signify considerable architectural or API changes; the
minor version number changes throughout the development cycle. Even numbers
indicate stable releases and odd ones development releases. Lastly, the
patch number is incremented for each release, and for stable release
candidates it is bumped to
|Release Candidate||odd||≥ 90|
For stable releases the following is always true, as long as the
version number stays the same:
patchreleases are guaranteed to be backward-compatible both at the API and ABI level.
minorreleases may contain new features and backward-compatible changes in the public API. In general the ABI will remain compatible as well, because we actively avoid breaking it unless strictly needed.
The following table summarizes which stable releases of libwpe, WPE WebKit, and WPEBackend-fdo are compatible and tested with each other.
|2.20.x||< 1.0.0||< 1.0.0|
Distributors and packagers are strongly advised to use the versions above. Note that libwpe used to be called wpebackend before version 1.0.x — it was renamed to avoid confusion.