From a9dca8fdc34e3b64d80d4c21bcf95fd29f720614 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Anne-Ga=C3=ABlle=20Berg=C3=A9?=
 <anne-gaelle.berge@kereval.com>
Date: Wed, 13 Mar 2019 16:24:40 +0100
Subject: [PATCH] fix README.md add release note for TM 5.9.6

---
 README.md                              | 49 +++++++-------------------
 Test-Management/release-notes/5_9_6.md | 22 ++++++++++++
 2 files changed, 34 insertions(+), 37 deletions(-)
 create mode 100644 Test-Management/release-notes/5_9_6.md

diff --git a/README.md b/README.md
index 6ed53c6..724a3b9 100644
--- a/README.md
+++ b/README.md
@@ -8,32 +8,34 @@ This project generates pdf, pdf with revision marks and a static  website (using
 
     sudo apt-get install make git git-svn texlive-xetex pandoc ruby-dev
 
-Clone using git-svn
+Clone using git
     
-    mkdir gazelle-documentation
-    cd gazelle-documentation
-    git svn clone https://scm.gforge.inria.fr/authscm/<developername>/svn/gazelle/gazelle-documentation -T trunk -b branches -t tags
+    mkdir gazelle-user-documentation
+    cd gazelle-user-documentation
+    git clone git@gitlab.inria.fr:gazelle/documentation/gazelle-user-documentation.git
+    
+You shall have previously defined your GitLab user: git config --global user.email "email@example.com"
 
-### Usage of git svn
+### Usage of git
 
 To update your local copy
 
-    git svn rebase .
+    git rebase .
 
 Once your work is ready, you can commit locally
 
     git add filenames
     git commit -m "blah blah" filenames
 
-And then push all the local commits on the forge
+And then push all the local commits on Git Lab
 
-    git svn dcommit
+    git push
 
 ## Generate documentation
 
 install required software
 
-from `gazelle-documentation` folder run:
+from `gazelle-dev-documentation` folder run:
 
     $ make setup
       # will install requirement on the computer
@@ -89,34 +91,7 @@ To get fancy final documents, you need:
 
 The YAML header is used by Jekyll and pandoc to generate menus and front pages, make sure all the metadata are present and up-to-date. The *.md files must start with the YAML header.
 
-Add the following header to your file (header of release note is generated in Jira, you only have to set the empty values):
-
-    ---
-    title:  User Manual or Installation Manual
-    subtitle: Tool name
-    author: Your name
-    function: Engineer
-    date: current date
-    toolversion: version of the tool the document applies to
-    version: version of the document
-    status: statut du document (Approved|Draft|For review)
-    reference: KER3-MAN-HEALTHLAB-(TOOL_NAME)_(USER|INSTALLATION)
-    customer: IHE-EUROPE
-    ---
-Example:
-
-    ---
-    title: User Manual
-    subtitle: Order Manager
-    author: Anne-Gaëlle BERGE
-    function: Engineer
-    date: 02/09/2016
-    toolversion: 5.x
-    version: 2.01
-    status: Draft document
-    reference: KER3-MAN-HEALTHLAB-ORDER_MANAGER_USER
-    customer: IHE-EUROPE
-    ---
+The YAML header is used by Jekyll and pandoc to generate menus and front pages, make sure all the metadata are present and up-to-date. The *.md files must start with the YAML header.
 
 
 # Links
diff --git a/Test-Management/release-notes/5_9_6.md b/Test-Management/release-notes/5_9_6.md
new file mode 100644
index 0000000..2b42a42
--- /dev/null
+++ b/Test-Management/release-notes/5_9_6.md
@@ -0,0 +1,22 @@
+---
+title: Release note
+subtitle: Gazelle Test Management - 5.9.6
+toolversion: 5.9.6
+releasedate: 2019-03-13
+author: Anne-Gaëlle Bergé
+function: Quality engineer
+customer: IHE Europe
+reference: KER1-RNO-IHE-TEST_MANAGEMENT_5_9_6
+---
+# All changes
+
+## Bug
+* \[[GZL-4804](https://gazelle.ihe.net/jira/browse/GZL-4804)\] /Test Management/System Testing/5 - System Management/As Vendor admin/TM-312:Vendor admin generates Integration Statemen
+* \[[GZL-4819](https://gazelle.ihe.net/jira/browse/GZL-4819)\] Adding a HL7 conformance profile is failing when the selected transaction is linked to a document
+
+# Dependencies
+
+Dependencies are up-to-date
+
+# Remarks
+NA
-- 
GitLab