Semantic Versioniong

What does the version number "1.2.3" represent in Semantic Versioning (SemVer)?

• Major version: 1, Minor version: 2, Patch version: 3

• • Major version: 3, Minor version: 2, Patch version: 1

• • Major version: 2, Minor version: 1, Patch version: 3

• Major version: 1, Minor version: 3, Patch version: 2

What type of changes would typically increment the major version number in Semantic Versioning?

• Bug fixes and security patches

• • New features that are backwards compatible

• • API changes that are not backwards compatible

• Minor enhancements and optimizations

In Semantic Versioning, when should the minor version number be incremented?

• For major overhauls and rewrites

• • For backwards-compatible feature additions

• • For bug fixes and security updates

• • For API changes that may break compatibility

What does it mean if a version number includes a prerelease identifier (e.g., "1.2.3-alpha.1") in Semantic Versioning?

• • It's a stable release suitable for production use

• • It's a version with experimental or incomplete features

• • It's a version with critical security fixes

• • It's a version with major API changes

What is the purpose of Semantic Versioning (SemVer)?

• • To ensure that software versions are always backwards-compatible

• • To provide a standardized way of versioning software releases

• • To prevent the introduction of any breaking changes in software updates

• • To guarantee that software versions are always bug-free