version updates for libraries

[Stefan (metze) Metzmacher]

Hi Tridge, hi Rusty,

>>> but no need for a new Y version, 1.0.4 is enough as a new
>>> function doesn't cause any incompatibility with previous library
>>> versions.
>>
>> I think we should make it clear if we add new features and apply this rule
>> for X.Y.Z versions:
>>
>> if X == 0:
>>     /* X == 0, means there's no stable API/ABI yet */
>>     - bug fixes and new features should trigger an update of Z.
>>     - incompatible changes should trigger an update of Y.
>> else
>>     - important bug fixes should trigger an update of Z.
>>     - new features should trigger an update of Y
>>     - incompatible changes should trigger an update of X.
>>
>> It would be nice if we could add checks for this into the ABI checking code.
> 
> Ok, I can agree with this logic, having at least guideines splleed
> clearly in a README is probably a nice first step.

Are you also fine with such a logic for talloc, tdb, tevent and ldb?

metze

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20110411/48faa66c/attachment.pgp>