versjonsstamme

Versjonsstamme is a term used in software development to describe the main lineage of a project’s versions within a version control system. It represents the central backbone from which features, fixes, and releases diverge and later converge. In some systems the versjonsstamme is called trunk (as in Subversion), while in distributed systems like Git the closest analogue is the main or master branch, often renamed to main.

In practice, developers create branches off the versjonsstamme to implement new functionality or address issues. When work is complete and validated, changes are merged back into the versjonsstamme. Releases are typically produced by tagging a specific state of the versjonsstamme or by creating a release branch derived from it. The versjonsstamme thus serves as the reference point for ongoing development and for formal version numbers.

Stability and workflow considerations are common around the versjonsstamme. Teams often enforce practices such as code review, automated testing, and continuous integration before merging into the versjonsstamme to maintain a reliable integration line. Some workflows also maintain long-running release branches that snapshot the versjonsstamme for a particular release train, while hotfix branches may revert to the versjonsstamme for patches.

Terminology can vary by organization and version control system. While versjonsstamme communicates the idea of a main development line, others may prefer terms like hovedgren, hovedlinje, trunk, or main. The concept remains the same: a central, evolving lineage that anchors the project’s version history.