@@ -99,18 +99,19 @@ previously taken to shield users from such a change, for example by
9999such structures only ever being allocated/instantiated by a library
100100function which would give the new field a suitable default value.
101101
102- Adding a new function would NOT force an increase in the major version
103- number. When the major version is increased all applications which
104- link to the library MUST be recompiled - this is not desirable. When
102+ Adding a new function should NOT force an increase in the major version
103+ number. (Packagers will see the standard minor number update and install
104+ the new library.) When the major version is increased all applications
105+ which link to the library MUST be recompiled - this is not desirable. When
105106the major version is updated the minor version gets reset.
106107
107108Minor Version
108109=============
109110
110- The minor version number should be updated whenever the functionality
111- of the library has changed, typicallyand change in source code
112- between releases would mean an increase in the minor version number so
113- long as it does not require a major version increase.
111+ The minor version number should be updated whenever the functionality of
112+ the library has changed, typicallya change in source code between releases
113+ would mean an increase in the minor version number so long as it does not
114+ require a major version increase.
114115
115116Minimizing Changes
116117==================