From b01bb43efe2e65d89d2a0488c87126af03a606e1 Mon Sep 17 00:00:00 2001 From: ahothan Date: Wed, 18 Oct 2017 10:43:09 -0700 Subject: Add dev section to doc Change-Id: I1e8d4a3fa6be7305c89fbc28b31377ec0f9d51a2 Signed-off-by: ahothan --- docs/development/design/versioning.rst | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 docs/development/design/versioning.rst (limited to 'docs/development/design/versioning.rst') 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. + + + + + + -- cgit 1.2.3-korg