Patch and minor versions MUST be reset to 0 when major version is incremented. It MAY also include minor and patch level changes. Major version X (X.y.z | X > 0) MUST be incremented if any backwards incompatible changes are introduced to the public API. Patch version MUST be reset to 0 when minor version is incremented. It MAY be incremented if substantial new functionality or improvements are introduced within the private code. It MUST be incremented if any public API functionality is marked as deprecated. Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backwards compatible functionality is introduced to the public API. A bug fix is defined as an internal change that fixes incorrect behavior. Patch version Z (x.y.Z | x > 0) MUST be incremented if only backwards compatible bug fixes are introduced. The way in which the version number is incremented after this release is dependent on this public API and how it changes. The public API SHOULD NOT be considered stable. Major version zero (0.y.z) is for initial development.The following rules label these numbers as x.y.z: Let's dig into the Semantic Versioning standards. There is a special difference between 0.0.0 and 1.0.0.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |