[Opendnssec-develop] RE: Versioning and version support
Sara Dickinson
sara at sinodun.com
Mon Dec 3 11:36:21 UTC 2012
On 26 Nov 2012, at 13:35, Siôn Lloyd wrote:
> I think that this would be good, note however the text for major version
> number says "Major version X (X.y.z | X > 0) MUST be incremented if any
> backwards incompatible changes are introduced to the public API."
>
> So that doesn't preclude enforcer-ng being 2.0 even if the API didn't
> change at all if I read it correctly?
Well, it depends if you consider the database schema part of the API I suppose......
But I think your point is that we would still be free to bump versions numbers based on the magnitude of functional changes. And I think the answer is yes, but (IMHO) it could be very confusing for users if we mix and match.... I think this versioning scheme makes a lot of sense for a library because it is aimed at managing dependancies, but for a complex application it does have some drawbacks....
> It also means new functionality
> doesn't have to bump the major version.
Indeed - if you just add new stuff it is just a minor version. So this really is quite a change from how we do things now.
Sara.
>
> Sion
>
More information about the Opendnssec-develop
mailing list