Skip to content

True Semantic Versioning, API Deprecation

No due date 20% complete

Currently, all nimi-python packages release together with the same version, getting a patch version bump, regardless of the actual changes. This is not true semantic versioning. The version change does not signal to a user whether major or even breaking changes were made.

Without true semantic versioning, it's also hard to justify breaking changes to corr…

Currently, all nimi-python packages release together with the same version, getting a patch version bump, regardless of the actual changes. This is not true semantic versioning. The version change does not signal to a user whether major or even breaking changes were made.

Without true semantic versioning, it's also hard to justify breaking changes to correct mistakes we've made in the past.
In the spirit of being able to make major API changes, we also want the ability to deprecate parts of the API.

Loading