diff options
| author | Thomas Haller <thaller@redhat.com> | 2015-08-22 00:57:30 +0200 |
|---|---|---|
| committer | Thomas Haller <thaller@redhat.com> | 2015-08-25 09:04:35 +0200 |
| commit | b2a66d59c8532228906bc554ac94717b1937882d (patch) | |
| tree | f851946d8e902803b425f6e107e1fb9985a44440 /libnm/nm-device-wifi.c | |
| parent | 913f5d9898f78e6d2d457d188ef6b8e653337c4a (diff) | |
| download | NetworkManager-b2a66d59c8532228906bc554ac94717b1937882d.tar.gz | |
Revert "all: change "Since: 1.2" to "Since: 1.0.4"/"Since: 1.0.6" for backported API"
API should be added with "Since:" of the next release on the same branch.
That means, new API on 1.1 branch (development), should be "Since: 1.2"
and new API on 1.0 branch (stable) will be "Since: 1.0.x". Similarly, new
API on master is NM_AVAILABLE_IN_1_2 and will be added with the linker
version libnl_1_2 -- never the versions of minor releases.
It is also strongly advised that for the 1.0 branch, we only add API
that was previously formerly added on master. IOW, that we only do true
backports of API that already exists on master.
API that gets backported, must also be added to master via NM_BACKPORT_SYMBOL().
That gives ABI compatibility and an application that was build against 1.0.x
will work with 1.y.z version (y > 0) without need for recompiling -- provided
that 1.y.z also contains that API.
There is one important caveat: if a major branch (e.g. current master) has a
linker section of backported APIs (e.g. libnm_1_0_6), we must do the minor release
(1.0.6) before the next major release (1.2). The reason is that after the major
release, the linker section (libnm_1_0_6) must not be extended and thus
the minor release (1.0.6) must be already released at that point.
In general, users should avoid using backported API because it limits
the ability to upgrade to arbitrary later versions. But together with the
previous point (that we only backport API to minor releases), a user that
uses backported API can be sure that a 1.y.z version is ABI compatible with
1.0.x, if the 1.y.z release date was after the release date of 1.0.x.
This reverts commit 02a136682c749a0fd27853c0152d36c44635151f.
Diffstat (limited to 'libnm/nm-device-wifi.c')
| -rw-r--r-- | libnm/nm-device-wifi.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/libnm/nm-device-wifi.c b/libnm/nm-device-wifi.c index 17e2a2a2e0..9019e0384d 100644 --- a/libnm/nm-device-wifi.c +++ b/libnm/nm-device-wifi.c @@ -355,7 +355,7 @@ nm_device_wifi_request_scan (NMDeviceWifi *device, * Returns: %TRUE on success, %FALSE on error, in which case @error will be * set. * - * Since: 1.0.6 + * Since: 1.2 **/ gboolean nm_device_wifi_request_scan_options (NMDeviceWifi *device, @@ -467,7 +467,7 @@ nm_device_wifi_request_scan_async (NMDeviceWifi *device, * D-Bus call. Valid otions inside the dictionary are: * 'ssids' => array of SSIDs (saay) * - * Since: 1.0.6 + * Since: 1.2 **/ void nm_device_wifi_request_scan_options_async (NMDeviceWifi *device, |