Unity API

Merge lp:~michihenning/unity-api/version-semantics into lp:unity-api

  1. version-semantics
  2. Merge into trunk
Proposed by Michi Henning
Status: Merged
Approved by: Michał Sawicz
Approved revision: 42
Merged at revision: 42
Proposed branch: lp:~michihenning/unity-api/version-semantics
Merge into: lp:unity-api
Diff against target: 23 lines (+4/-5)
1 file modified
include/unity/api/Version.h.in (+4/-5)
To merge this branch: bzr merge lp:~michihenning/unity-api/version-semantics
Reviewer Review Type Date Requested Status
Michał Sawicz Approve
PS Jenkins bot (community) continuous-integration Approve
Review via email: mp+164164@code.launchpad.net

Commit message

Updated version semantics to state that only major version change indicates ABI incompatibility.

Description of the change

Updated version semantics to state that only major version change indicates ABI incompatibility.

To post a comment you must log in.
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

PASSED: Continuous integration, rev:42
http://jenkins.qa.ubuntu.com/job/unity-api-ci/33/
Executed test runs:
    SUCCESS: http://jenkins.qa.ubuntu.com/job/unity-api-raring-armhf-ci/33
        deb: http://jenkins.qa.ubuntu.com/job/unity-api-raring-armhf-ci/33/artifact/work/output/*zip*/output.zip
    SUCCESS: http://jenkins.qa.ubuntu.com/job/unity-api-raring-i386-ci/33

Click here to trigger a rebuild:
http://s-jenkins:8080/job/unity-api-ci/33/rebuild

review: Approve (continuous-integration)
Revision history for this message
Michał Sawicz (saviq) :
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'include/unity/api/Version.h.in'
2--- include/unity/api/Version.h.in 2013-05-13 11:39:49 +0000
3+++ include/unity/api/Version.h.in 2013-05-16 11:53:18 +0000
4@@ -43,15 +43,14 @@
5 Version information is represented as
6 <i>&lt;<code>major</code>&gt;</i>.<i>&lt;<code>minor</code>&gt;</i>.<i>&lt;<code>micro</code>&gt;</i>.
7
8-Releases that differ in the major or minor version number are binary incompatible.
9+Releases that differ in the major version number are binary incompatible.
10
11-Releases of the library that differ only in the micro version number are binary compatible with older releases,
12+Releases that differ in the minor or micro version number are binary compatible with older releases,
13 so client code does not need to be recompiled to use the newer library version.
14
15-A different minor version is compatible at the API level, that is, it may add new APIs, but does not change existing
16-ones. API clients must be recompiled for a new minor version.
17+Changes in the micro version number indicate bug fixes.
18
19-A different major version indicates incompatible API changes.
20+Changes in the minor version indicate feature additions that are binary compatible.
21 */
22
23 // Version could be a namespace instead of a class, but that requires a lower-case name,

Subscribers

People subscribed via source and target branches

to all changes: