Skip to content

Commit 9e66c00

Browse files
committed
github added git tagging page.
1 parent 42e3425 commit 9e66c00

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

docs/git/tagging.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,3 +3,21 @@ id: tagging
33
title: Tagging
44
sidebar_label: Tagging
55
---
6+
7+
Semantic Versioning is all about releases, not builds. This means that the version only increases after you release.
8+
9+
Following are the standards that should be followed while tagging releases:
10+
11+
* Every release should have a tag.
12+
13+
* You can tag from any long running branch ( dev, qa, staging, master). However, we strictly follow tagging from master branch.
14+
15+
* Tag name should follow the *major.minor.patch_* naming conventions as suggested by <a href="https://semver.org/" target="_blank">Semantic Versioning</a>
16+
17+
* The tag for a version is in "X.Y.Z" format where,
18+
19+
* Z is hot-fixes and patch release. If the release includes hot-fixes and patches, we increment this value by 1. Example : "2.7.1", "2.7.2"
20+
21+
* Y includes major feature releases. If the release includes a major feature which is going to production for the first time we increase this value by 1. Example: "2.8.0", "2.9.0"
22+
23+
* X is increased when there is a major change in the system which affects the entire application flow or UI/UX(flow) of a system. Example: "3.0.0", "4.0.0" .

0 commit comments

Comments
 (0)