Merge pull request #7397 from planetf1/3.10.1

Egeria release 3.10.1

Author: planetf1

assets/img/lf-projects.svg

@@ -38,7 +38,7 @@ plugins {
 allprojects {
 
     group = 'org.odpi.egeria'
-    version = '3.10'
+    version = '3.10.1'
 
     // Mostly java, so default to this for now
     apply plugin: 'java'

build.gradle

@@ -10,7 +10,7 @@
     <parent>
         <artifactId>egeria</artifactId>
         <groupId>org.odpi.egeria</groupId>
-        <version>3.10</version>
+        <version>3.10.1</version>
     </parent>
 
     <name>Add module name here</name>

developer-resources/License-Example-Files/License_for_POM_Files.xml

@@ -64,7 +64,7 @@ are GPG signed and distributed to [Maven Central](https://oss.sonatype.org).
 #### 4. Update master version & cleanup notes
 * `git checkout master`
 * `git pull upstream master`
-* Edit all files (command line or IDE) to replace 'x.y-SNAPSHOT' with the next version, ie change '1.3-SNAPSHOT' to '3.10'. Most of the changes are in pom.xml files, however some code & documentation also has references to our versions and all need modifying. 
+* Edit all files (command line or IDE) to replace 'x.y-SNAPSHOT' with the next version, ie change '1.3-SNAPSHOT' to '3.10.1'. Most of the changes are in pom.xml files, however some code & documentation also has references to our versions and all need modifying. 
 * If using an IDE like IntelliJ make sure you have all hits by searching again as by default only a limited number of hits are shown - see https://youtrack.jetbrains.com/issue/IDEA-157855 for Intellij advice.
 * Commit
 * Now remove all the release notes from the 'release-notes' directory other than README.md - so users will always get directed to the latest in master

developer-resources/Release-Process.md

@@ -11,7 +11,7 @@ It uses commands such as:
 
 ```bash
 $ curl --insecure -X GET https://localhost:9443/open-metadata/platform-services/users/test/server-platform/origin
-Egeria OMAG Server Platform (version 3.10)
+Egeria OMAG Server Platform (version 3.10.1)
 ```
 
 Note that Egeria is using https, so if you have not replaced the provided self-signed certificate, ensure to add '--insecure' to any requests