Steve Morris wrote:

> Colin Guthrie wrote:
>> Steve Morris wrote:
>>> It is just not true that a change in library major guarantees that
>>> dependent applications will no longer work
>>
>> Erm? If it will definately work, then why change the major? Just
>> change the minor and go. This is *exactly* what application majors do.
>> Sure some apps that only make use of a subset of your library's API
>> should continue to work, but the simple thing is that it's guaranteed
>> *not* to work for some people and the flipside is what's actually
>> wrong with continuing to use the library the developer specifically
>> developed, tested and used his application with? To me this is
>> fundamentally more sensible.
> It is sensible to increase the major when you are introducing new apis,
> i.e. new functionality. Doing this should not cause software that is
> using other unchanged apis within the library to fail.

Incorrect. Major is only raised when you are *removing* "apis" and
breaking something. Adding "apis" does not break anything, so there is
no sense in changing the major number. When "apis" are added, the minor
number is raised. When there is no change in api, the micro number is
raised.

--
Anssi Hannula