Statements (116)
| Predicate | Object |
|---|---|
| gptkbp:instance_of |
gptkb:archive
|
| gptkbp:bfsLayer |
3
|
| gptkbp:bfsParent |
gptkb:aircraft
gptkb:spacecraft gptkb:church gptkb:npm gptkb:API gptkb:Apache_Camel_Component gptkb:software gptkb:item gptkb:chess_match |
| gptkbp:allows |
backward compatibility
|
| gptkbp:based_on |
three-part version number
|
| gptkbp:challenges |
can lead to confusion if not followed correctly
|
| gptkbp:communication |
changes in software
|
| gptkbp:community |
has a strong community of users and contributors
|
| gptkbp:consists_of |
patch version
major version minor version |
| gptkbp:construction_material |
provides additional build information but does not affect version precedence
|
| gptkbp:controls |
release planning
|
| gptkbp:created_by |
gptkb:2013
gptkb:Tom_Preston-Werner |
| gptkbp:defines |
a versioning system for software that conveys meaning about the underlying changes with each new release
Sem Ver specification |
| gptkbp:first_released |
indicates unstable versions that may not meet the full version criteria
|
| gptkbp:goal |
to make it easier to manage dependencies
|
| gptkbp:has_documentation |
should be well-documented to avoid misunderstandings
|
| gptkbp:has_version |
aims to provide stability in software releases
|
| gptkbp:historical_documentation |
has a history of evolving practices in software versioning
|
| https://www.w3.org/2000/01/rdf-schema#label |
Semantic Versioning
|
| gptkbp:impact |
has influenced other versioning schemes
|
| gptkbp:includes |
pre-release versions
build metadata |
| gptkbp:is_a_framework_for |
gptkb:software
release cycles software development processes |
| gptkbp:is_a_tool_for |
project management
many tools and libraries support semantic versioning software project coordination |
| gptkbp:is_adopted_by |
widely adopted in the software development community
|
| gptkbp:is_compatible_with |
continuous integration
ensures that software can be updated without breaking existing functionality |
| gptkbp:is_described_as |
version numbers
software versioning |
| gptkbp:is_documented_in |
gptkb:semver.org
|
| gptkbp:is_essential_for |
dependency management
software maintenance |
| gptkbp:is_implemented_in |
package managers
|
| gptkbp:is_known_for |
Sem Ver
|
| gptkbp:is_maintained_by |
Semantic Versioning Specification
|
| gptkbp:is_often_used_in |
open source projects
|
| gptkbp:is_recognized_by |
software engineers
|
| gptkbp:is_referenced_in |
gptkb:document
software libraries software documentation standards software engineering best practices |
| gptkbp:is_related_to |
release management
|
| gptkbp:is_represented_in |
breaking changes
bug fixes new features |
| gptkbp:is_standardized_by |
software releases
software development communities software interoperability software package distribution software versioning practices |
| gptkbp:is_used_by |
gptkb:software
|
| gptkbp:is_used_for |
version tracking
software versioning policies |
| gptkbp:is_used_in |
gptkb:software_framework
|
| gptkbp:latest_version |
promotes transparency in software development
common examples include libraries, frameworks, and applications is based on principles of clarity, consistency, and communication increases when functionality is added in a backwards-compatible manner aims to provide clarity in versioning practices encourages consistency across software projects helps developers communicate changes effectively increases when incompatible API changes are made provides guidelines for versioning practices sets clear expectations for users regarding updates tools like npm and Composer utilize semantic versioning uses a set of rules to determine which version is more recent can arise if multiple projects use different versioning schemes describes the stages of a software version from development to release facilitates better communication between developers and users the current version of the specification as of 2023 |
| gptkbp:legal_issue |
gptkb:architect
software engineering software project management |
| gptkbp:marketing_strategy |
software updates
|
| gptkbp:next_edition |
1.0.0
|
| gptkbp:origin |
proposed by Tom Preston-Werner in 2011
|
| gptkbp:performed_by |
agile development
software quality assurance encourages clear communication about software changes |
| gptkbp:philosophy |
is rooted in the philosophy of making software development more predictable.
|
| gptkbp:provides |
clear versioning guidelines
rules for versioning |
| gptkbp:provides_information_on |
API versioning
software compatibility software release management software release policies |
| gptkbp:related_concept |
gptkb:software
|
| gptkbp:related_model |
software evolution
software project lifecycles |
| gptkbp:release_format |
MAJOR. MINOR. PATCH
|
| gptkbp:released |
often accompany version changes to explain the updates
increases when backwards-compatible bug fixes are introduced |
| gptkbp:requires |
version number incrementing
|
| gptkbp:technique |
version control
versioning strategies version differentiation versioning conventions |
| gptkbp:updates |
provides a clear and consistent way to manage version numbers
|
| gptkbp:uses |
MAJOR. MINOR. PATCH format
|
| gptkbp:website |
gptkb:semver.org
|