[xmlsec] versioning and library naming policies

[Doug Royer]

Rich Salz wrote:
>>Are you really prepared to increment N every time a function signature is
>>changed, a public structure is changed, or the semantics of the API
>>is changed?
> 
> 
> Makes sense to me.

I agree. It is a common convention.

>>  This rule must be applied to every release you make, development, stable, or
>>otherwise.
>>
>
> Disagree.  You can change N when you start an incompatible branch, not
> during development.

And as the library is out for a longer amount of time the number
of incompatible changes tend to go down.


-- 

  Doug Royer                     |   http://INET-Consulting.com
  -------------------------------|-----------------------------
  Doug at Royer.com                 | Office: (208)612-INET
  http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                 |   Cell: (208)520-4044

                 We Do Standards - You Need Standards
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4411 bytes
Desc: S/MIME Cryptographic Signature
Url : http://www.aleksey.com/pipermail/xmlsec/attachments/20030402/76bfe2ff/smime.bin