Talk:Package versioning policy
Jump to navigation
Jump to search
How about describing the semantics of versions in the following way?
1. If none of the module interfaces of your package have changed, the A.B.C prefix can remain the same.
2. If a user of the package only used qualified imports and/or imports a specified list of functions would imply that they could use your new package version, then the A.B prefix can remain the same.
3. Otherwise, the A.B prefix must be incremented.
Is this equivalent to the versioning policy?
--Roconnor 20:28, 29 August 2009 (UTC)
A special case that is not discussed is change of fixity. I presume fixity changes should require bumping the major version?
--Bjorn 15:01, 8 April 2011 (UTC)