Qt-Version-Compatibility: Difference between revisions
AutoSpider (talk | contribs) (Remove non-functioning "toc" command) |
(Clean up) |
||
| Line 1: | Line 1: | ||
[[Category:Developing_Qt::Guidelines]] | [[Category:Developing_Qt::Guidelines]] | ||
Qt uses a major.minor.patch numbering scheme for Qt releases. For example, Qt 5.0.1 represents the 1st patch release of Qt 5.0. Each release has restrictions on what kind of changes are acceptable, in order to provide a predictable and stable API. This enables users who are only interested in certain types of improvements to be sure that they won't be adversely affected by upgrading to a newer version. | Qt uses a major.minor.patch numbering scheme for Qt releases. For example, Qt 5.0.1 represents the 1st patch release of Qt 5.0. Each release has restrictions on what kind of changes are acceptable, in order to provide a predictable and stable API. This enables users who are only interested in certain types of improvements to be sure that they won't be adversely affected by upgrading to a newer version. | ||
| Line 21: | Line 14: | ||
<blockquote>A library is '''binary compatible''', if a program linked dynamically to a former version of the library continues running with newer versions of the library without the need to recompile. | <blockquote>A library is '''binary compatible''', if a program linked dynamically to a former version of the library continues running with newer versions of the library without the need to recompile. | ||
- [https://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C techbase.kde.org] | - [https://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C++ techbase.kde.org] | ||
</blockquote> | </blockquote> | ||
== Source Compatibility Guidelines == | == Source Compatibility Guidelines == | ||
<blockquote>If a program needs to be recompiled to run with a new version of library but doesn't require any further modifications, the library is '''source compatible'''. | <blockquote>If a program needs to be recompiled to run with a new version of library but doesn't require any further modifications, the library is '''source compatible'''. | ||
- [https://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C techbase.kde.org] | - [https://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C++ techbase.kde.org] | ||
</blockquote> | </blockquote> | ||
== Compatibility in Modules == | == Compatibility in Modules == | ||
Revision as of 15:25, 4 May 2015
Qt uses a major.minor.patch numbering scheme for Qt releases. For example, Qt 5.0.1 represents the 1st patch release of Qt 5.0. Each release has restrictions on what kind of changes are acceptable, in order to provide a predictable and stable API. This enables users who are only interested in certain types of improvements to be sure that they won't be adversely affected by upgrading to a newer version.
We do our best to maintain compatibility between versions. However, in order to improve Qt it is sometimes necessary to break compatibility.
Major releases may break backwards binary and source compatibility, although source compatibility may be maintained.
Minor releases are backwards binary and source compatible.
Patch releases are both backwards and forwards binary and source compatible.
Binary Compatibility Guidelines
A library is binary compatible, if a program linked dynamically to a former version of the library continues running with newer versions of the library without the need to recompile.
Source Compatibility Guidelines
If a program needs to be recompiled to run with a new version of library but doesn't require any further modifications, the library is source compatible.
Compatibility in Modules
The modules in Qt Essentials have the same forward and backward compatibility promises as Qt 4: new Qt 5 minor releases will not break binary compatibility, and patch level releases are forward and backward compatible. Qt Add-On modules specify their compatibility promise separately.
Additional Information
For more information on which branch you should submit a change to depending on its compatibility, see the branch guidelines.