[xmlsec] versioning and library naming policies

Rich Salz rsalz at datapower.com
Wed Apr 2 08:22:20 PST 2003

> 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.

>   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.

More information about the xmlsec mailing list