Version Control

Git is a distributed version control system that allows developers to track and manage changes to their codebase. It enables collaboration and provides a structured workflow for developer team.

Goal of Versioning

The primary goal is to provide a clear and permanent reference to specific points in your codebase's history. It helps track and identify important versions, releases, or milestones, making it easier to manage and access specific snapshots of your project.

Semantic Versioning

Adopting a versioning scheme, such as Semantic Versioning (SemVer), helps communicate the nature of changes in a standardized way. SemVer consists of three components: MAJOR.MINOR.PATCH.

• MAJOR version indicates incompatible changes that may require updates to existing code.

• MINOR version signifies the addition of new features without breaking existing functionality.

• PATCH version denotes bug fixes and other backward-compatible changes.

Tagging Rules

Establish rules and conventions for tagging to ensure consistency and clarity. Some common rules include:

• Use descriptive and meaningful tag names, such as v1.0.0 for the initial release or v2.1.3 for a specific version.

• Follow a consistent versioning scheme (e.g., SemVer) to indicate the nature of changes associated with each tag.

• Consider adding release notes or a changelog file to document the changes included in each tagged version.

How to update tag version

Step 1: Pull the latest tags

git pull --tags

Step 2: Update the version

git tag v1.x.x // please see tagging rules

Step 3: Push the new tags

git push --tags