Merge pull request #51 from gozer/issue-40-tags

Document tagging usage, fixes #40
nubisproject · Jun 29, 2015 · 1589a9d · 1589a9d
2 parents c1a152e + 0590b29
commit 1589a9d
Showing 1 changed file with 12 additions and 0 deletions.
diff --git a/RELEASING.md b/RELEASING.md
@@ -19,3 +19,15 @@ There can also be an extra postfix to the version number, added to describe the
  ### Code names
 
  Release code-names might be exist, but will be used for purely cosmetic purposes. The *Happy Panda* release would just be a name for the v1.5.0 release.
+
+## Tags
+
+Tags will be used to track releases of the Nubis Project.
+
+All tags will be [semantic versions](http://semver.org/) in the form of vn.n.n, where v stands for 'v'ersion, as per GitHub's recommended naming practices.
+
+All tags will be [GPG Signed](https://git-scm.com/book/tr/v2/Git-Tools-Signing-Your-Work) by the Release Manager, allowing anybody to verify their integrity.
+
+Each Nubis repository is allowed to follow it's own minor release tagging schedule.
+
+Major release bumps (i.e, from v0.9.2 to v1.0.0) will be coordinated across all repositories, to provide a consistent versionning scheme for each major Nubis Project release.