You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sciform attempts to adhere to Semantic Versioning (semver). According to semver
Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.
Version 1.0.0 defines the public API. The way in which the version number is incremented after this release is dependent on this public API and how it changes.
Major version X (X.y.z | X > 0) MUST be incremented if any backward incompatible changes are introduced to the public API. It MAY also include minor and patch level changes. Patch and minor versions MUST be reset to 0 when major version is incremented.
So far sciform has been operating in the "initial development" 0.y.z phase and as such the public API has seen somewhat regular breaking changes. Releasing 1.0.0 will mean transitioning to a stable API, such that backward incompatible changes will require major version bumps.
At the time of writing, all known issues on the 1.0.0 milestone have been addressed. Outstanding issues are either non-breaking or far enough out they need not be implemented before version 1.0.0. The main remaining hurdle to reaching 1.0.0 is reaching a high enough level of confidence that some breaking change (e.g. changing an option name) won't crop up in the short term like has been happening regularly throughout the initial development phase.
The text was updated successfully, but these errors were encountered:
All issues have been cleared. Attempts have been made to slim down the package/API to reduce the maintenance burden. There are currently no outstanding ideas for feature changes. The package may be in a good state for a release of 1.0.0.
sciform
attempts to adhere to Semantic Versioning (semver). According to semverSo far
sciform
has been operating in the "initial development"0.y.z
phase and as such the public API has seen somewhat regular breaking changes. Releasing1.0.0
will mean transitioning to a stable API, such that backward incompatible changes will require major version bumps.At the time of writing, all known issues on the 1.0.0 milestone have been addressed. Outstanding issues are either non-breaking or far enough out they need not be implemented before version
1.0.0
. The main remaining hurdle to reaching1.0.0
is reaching a high enough level of confidence that some breaking change (e.g. changing an option name) won't crop up in the short term like has been happening regularly throughout the initial development phase.The text was updated successfully, but these errors were encountered: