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
43
Version information is represented as
43
Version information is represented as
6
44
<i>&lt;<code>major</code>&gt;</i>.<i>&lt;<code>minor</code>&gt;</i>.<i>&lt;<code>micro</code>&gt;</i>.
44
<i>&lt;<code>major</code>&gt;</i>.<i>&lt;<code>minor</code>&gt;</i>.<i>&lt;<code>micro</code>&gt;</i>.
7
45
45
9
46
Releases that differ in the major or minor version number are binary incompatible.
46
Releases that differ in the major version number are binary incompatible.
10
47
47
12
48
Releases of the library that differ only in the micro version number are binary compatible with older releases,
48
Releases that differ in the minor or micro version number are binary compatible with older releases,
13
49
so client code does not need to be recompiled to use the newer library version.
49
so client code does not need to be recompiled to use the newer library version.
14
50
50
17
51
A different minor version is compatible at the API level, that is, it may add new APIs, but does not change existing
51
Changes in the micro version number indicate bug fixes.
16
52
ones. API clients must be recompiled for a new minor version.
18
53
52
20
54
A different major version indicates incompatible API changes.
53
Changes in the minor version indicate feature additions that are binary compatible.
21
55
*/
54
*/
22
56
55
23
57
// Version could be a namespace instead of a class, but that requires a lower-case name,
56
// Version could be a namespace instead of a class, but that requires a lower-case name,
Status:	Merged
Approved by:	Michał Sawicz on 2013-05-16
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
Related bugs:	Link a bug report
Reviewer	Review Type	Date Requested	Status
Michał Sawicz		2013-05-16	Approve on 2013-05-16
PS Jenkins bot (community)	continuous-integration		Approve on 2013-05-16
Review via email: mp+164164@code.launchpad.net
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	43	Version information is represented as	43	Version information is represented as
6	44	<i><<code>major</code>></i>.<i><<code>minor</code>></i>.<i><<code>micro</code>></i>.	44	<i><<code>major</code>></i>.<i><<code>minor</code>></i>.<i><<code>micro</code>></i>.
7	45		45
9	46	Releases that differ in the major or minor version number are binary incompatible.	46	Releases that differ in the major version number are binary incompatible.
10	47		47
12	48	Releases of the library that differ only in the micro version number are binary compatible with older releases,	48	Releases that differ in the minor or micro version number are binary compatible with older releases,
13	49	so client code does not need to be recompiled to use the newer library version.	49	so client code does not need to be recompiled to use the newer library version.
14	50		50
17	51	A different minor version is compatible at the API level, that is, it may add new APIs, but does not change existing	51	Changes in the micro version number indicate bug fixes.
16	52	ones. API clients must be recompiled for a new minor version.
18	53		52
20	54	A different major version indicates incompatible API changes.	53	Changes in the minor version indicate feature additions that are binary compatible.
21	55	*/	54	*/
22	56		55
23	57	// Version could be a namespace instead of a class, but that requires a lower-case name,	56	// Version could be a namespace instead of a class, but that requires a lower-case name,