Edinburgh->Fuji updates

[mhall119]

Locations in the current docs that reference either "Edinburgh" or "1.0" that may need to be updated to reflect the Fuji release:

• ./application/Ch-ApplicationServices.rst:7:The intention of Application Services are to address scalability concerns of the existing EdgeX Export Client and Distribution Services (Export Services) as well as provide a flexible solution for exporting data outside of EdgeX without encumbering the EdgeX development community itself with trying to support all major cloud providers and export solutions. For the Edinburgh release cycle, the existing Client and Export Service remain supported and are still considered the primary way to export data out of EdgeX. However, it is encouraged for new development efforts adopting EdgeX that the App Functions SDK and resulting Application Services be leveraged moving forward with the intention that by the Fuji release, the SDK will be moved into release status and become the primary method of exporting data from EdgeX.
• ./configuration/Ch-Configuration.rst:68: - 1.0
• ./configuration/Ch-Configuration.rst:74: - 1.0
• ./configuration/Ch-Configuration.rst:80:The versions shown correspond to major versions of the given services. These are not necessarily equated with long term support (LTS) releases. For all minor/patch versions associated with a major version, the respective service keys live under the major version in configuration (such as 1.0). Changes to the configuration structure that may be required during the associated minor version development cycles can only be additive. That is, key names will not be removed or changed once set in a major version, nor will sections of the configuration tree be moved from one place to another. In this way backward compatibility for the lifetime of the major version is maintained.
• ./configuration/Ch-Configuration.rst:89:- /edgex/core/1.0/edgex-core-data/Clients
• ./configuration/Ch-Configuration.rst:90:- /edgex/core/1.0/edgex-core-data/Databases
• ./configuration/Ch-Configuration.rst:91:- /edgex/core /1.0/edgex-core-data/Logging
• ./configuration/Ch-Configuration.rst:92:- /edgex/core/1.0/edgex-core-data/MessageQueue
• ./configuration/Ch-Configuration.rst:93:- /edgex/core/1.0/edgex-core-data/Registry
• ./configuration/Ch-Configuration.rst:94:- /edgex/core/1.0/edgex-core-data/Service
• ./configuration/Ch-Configuration.rst:95:- /edgex/core/1.0/edgex-core-data/Writable
• ./examples/Ch-ExamplesAddingMQTTDevice.rst:325:Download the docker-compose file from https://github.com/edgexfoundry/developer-scripts/blob/master/releases/**edinburgh**/compose-files/docker-compose-edinburgh-1.0.0.yml.
• ./examples/Ch-ExamplesAddingMQTTDevice.rst:332: image: edgexfoundry/docker-device-mqtt-go:1.0.0
• ./examples/Ch-ExamplesAddingMQTTDevice.rst:5:EdgeX - Edinburgh Release
• ./examples/Ch-ExamplesVirtualDeviceService.rst:105: image: edgexfoundry/docker-device-virtual-go:1.0.0
• ./general/conf.py:62:#version = u'1.0'
• ./general/conf.py:64:#release = u'1.0'
• ./getting-started/Ch-GettingStartedSDK-C.rst:25:The next step is to download and build the EdgeX Device SDK for C. You always want to use the release of the SDK that matches the release of EdgeX you are targeting. As of this writing the edinburgh release is the current stable release of EdgeX, so we will be using the edinburgh branch of the C SDK.
• ./getting-started/Ch-GettingStartedSDK-C.rst:27:#. First, clone the edinburgh branch of device-sdk-c from Github::
• ./getting-started/Ch-GettingStartedSDK-C.rst:29: git clone -b edinburgh https://github.com/edgexfoundry/device-sdk-c.git
• ./getting-started/Ch-GettingStartedSDK-C.rst:59: export CSDK_DIR=../device-sdk-c/build/release/_CPack_Packages/Linux/TGZ/csdk-1.0.0
• ./security/Ch-SecretStore.rst:156: edgex-core-consul | Version: 'v1.1.0'
• ./security/Ch-SecretStore.rst:552: edgex-core-consul 127.0.0.1:8301 alive server 1.1.0 2 dc1

[bnevis-i]

• ./security/Ch-SecretStore.rst:156: edgex-core-consul | Version: 'v1.1.0'
• ./security/Ch-SecretStore.rst:552: edgex-core-consul 127.0.0.1:8301 alive server 1.1.0 2 dc1

This is the correct version for Fuji; no action needed.

[jpwhitemn]

Configuration that references 1.0 config is still correct for Fuji (verified against what is in consul).

[jpwhitemn]

have verified all of these items have been changed on the Fuji branch. All have been changed on master branch except those in Ch-GettingStartedSDK-C.rst and Ch-ExamplesAddingMQTTDevice.rst . Closing this issue and creating two new issues for these doc updates for Geneva