Merge pull request #164 from tgonzalezorlandoarm/tg/parsec-v1.3.0

Change parsec version to 1.3.0

src/getting_started/installation_options.md

@@ -124,16 +124,16 @@ ldd --version
 
 ### Download the Latest Quick-Start Release Bundle
 
-Run the following command to download and unpack the `quickstart-1.2.0-linux_x86_64` folder.
+Run the following command to download and unpack the `quickstart-1.3.0-linux-x86_64` folder.
 
 ```
-curl -s -N -L https://github.com/parallaxsecond/parsec/releases/download/1.2.0/quickstart-1.2.0-linux_x86_64.tar.gz | tar xz
+curl -s -N -L https://github.com/parallaxsecond/parsec/releases/download/1.3.0/quickstart-1.3.0-linux-x86_64.tar.gz | tar xz
 ```
 
 The resulting directory contains the following structure
 
 ```
-quickstart-1.2.0-linux_x86_64
+quickstart-1.3.0-linux-x86_64
 ├── bin
 │   ├── parsec                 # The parsec binary
 │   └── parsec-tool            # The parsec client tool
@@ -144,11 +144,11 @@ quickstart-1.2.0-linux_x86_64
     └── parsec-cli-tests.sh    # Standard parsec-tool tests
 ```
 
-The following examples assume you've navigated to the `quickstart-1.2.0-linux_x86_64/quickstart`
+The following examples assume you've navigated to the `quickstart-1.3.0-linux-x86_64/quickstart`
 directory, so let's do that now.
 
 ```
-cd quickstart-1.2.0-linux_x86_64/quickstart
+cd quickstart-1.3.0-linux-x86_64/quickstart
 ```
 
 ### Configure Your Environment
@@ -241,13 +241,14 @@ export PARSEC_SERVICE_ENDPOINT="unix:$(pwd)/parsec.sock"
 ```
 
 If parsec-tool is not installed into a directory included in `PATH`, then you also need to define
-`PARSEC_TOOL` environment variable with a full path to it:
+the `PARSEC_TOOL` environment variable with a full path to it. Assuming the current working
+directory is `quickstart-1.3.0-linux-x86_64/quickstart`:
 
 ```
-export PARSEC_TOOL="$(pwd)/parsec-tool"
+export PARSEC_TOOL="$(pwd)/../bin/parsec-tool"
 ```
 
-To run the script, simply execute it without any arguments as follows:
+To run the script from the same directory, simply execute it without any arguments as follows:
 
 ```
 ./parsec-cli-tests.sh

src/parsec_service/build_run.md

@@ -36,7 +36,7 @@ at `/tmp/parsec.sock`. The test configuration will make those choices.
 Clone the Parsec service repo,
 
 ```
-git clone --branch 1.2.0 https://github.com/parallaxsecond/parsec.git
+git clone --branch 1.3.0 https://github.com/parallaxsecond/parsec.git
 ```
 
 Having cloned the Parsec repository, to build and run from source using the Mbed Crypto provider and

src/parsec_service/stability.md

@@ -23,7 +23,7 @@ without breaking anything. The only exception is for the communication channel w
 any version of the client library can successfully communicate with any version of the service.
 
 The principle of [semantic versioning](https://semver.org/) is used to describe the stability of
-Parsec versions and when breaking changes are done. If `parsec` version is at `1.2.0` then all
+Parsec versions and when breaking changes are done. If `parsec` version is at `1.3.0` then all
 future stable version to that will be `1.x.y`. Note that, although semver is used to describe Parsec
 stability, it is a strong goal for Parsec to remain stable at a `1.x.y` version. This document
 introduces the efforts that are made so that a `MAJOR` version bump should hopefully never happen.