From f1d59a8130dce2ac9295bc5495e628fdb752b74d Mon Sep 17 00:00:00 2001 From: ahothan Date: Thu, 1 Nov 2018 08:17:49 -0700 Subject: NFVBENCH-105 ARP not working with NFVbench 2.0 Fix type in arp record field. Remove unneeded code. Change-Id: I7a77f66c5e1c357907f4fd113f864708a351f152 Signed-off-by: ahothan --- docs/development/design/versioning.rst | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) (limited to 'docs/development/design/versioning.rst') diff --git a/docs/development/design/versioning.rst b/docs/development/design/versioning.rst index 870ed86..8103534 100644 --- a/docs/development/design/versioning.rst +++ b/docs/development/design/versioning.rst @@ -8,15 +8,9 @@ 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). +Rules for the version numbers follow the semver 2.0 specification (https://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