aboutsummaryrefslogtreecommitdiffstats
path: root/docs/development/design/versioning.rst
diff options
context:
space:
mode:
authorahothan <ahothan@cisco.com>2017-10-18 10:43:09 -0700
committerahothan <ahothan@cisco.com>2017-10-18 10:53:54 -0700
commit9b4428f37e07e400e978a5e1681d0391cf7512ec (patch)
tree0a09bb4d6cd77a6c88edc4dc71f3f33541fdbab3 /docs/development/design/versioning.rst
parent8fca5f93109dfb317b14e6ed41298497504bce39 (diff)
Add dev section to doc1.1.0
Change-Id: I1e8d4a3fa6be7305c89fbc28b31377ec0f9d51a2 Signed-off-by: ahothan <ahothan@cisco.com>
Diffstat (limited to 'docs/development/design/versioning.rst')
-rw-r--r--docs/development/design/versioning.rst22
1 files changed, 22 insertions, 0 deletions
diff --git a/docs/development/design/versioning.rst b/docs/development/design/versioning.rst
new file mode 100644
index 0000000..870ed86
--- /dev/null
+++ b/docs/development/design/versioning.rst
@@ -0,0 +1,22 @@
+
+.. This work is licensed under a Creative Commons Attribution 4.0 International
+.. License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) Cisco Systems, Inc
+
+Versioning
+==========
+
+NFVbench uses semver compatible git tags such as "1.0.0". These tags are also called project tags and applied at important commits on the master branch exclusively.
+Rules for the version numbers follow the semver 2.0 specification (http://semver.org).
+These git tags are applied indepently of the OPNFV release tags which are applied only on the stable release branches (e.g. "opnfv-5.0.0").
+
+In general it is recommeneded to always have a project git version tag associated to any OPNFV release tag content obtained from a sync from master.
+
+NFVbench Docker containers will be versioned based on the OPNF release tags or based on NFVbench project tags.
+
+
+
+
+
+