From 68dbe65a4c428ed4bbecc2d9618246afa7c7b860 Mon Sep 17 00:00:00 2001
From: ejacox <jacox_edwin@hotmail.com>
Date: Tue, 14 Mar 2017 16:17:20 -0700
Subject: [PATCH 1/2] maven instructions

---
 pom.xml                   |  2 +-
 scripts/release/README.md | 10 +++++++---
 2 files changed, 8 insertions(+), 4 deletions(-)

diff --git a/pom.xml b/pom.xml
index faaf8104..bfc3ecfb 100644
--- a/pom.xml
+++ b/pom.xml
@@ -4,7 +4,7 @@
   <groupId>org.ga4gh</groupId>
   <artifactId>ga4gh-schemas</artifactId>
   <packaging>jar</packaging>
-  <version>0.6.0a10-SNAPSHOT</version>
+  <version>0.6.0a10</version>
 
   <name>GA4GH: Schemas</name>
   <description>Data models and APIs for Genomic data.</description>
diff --git a/scripts/release/README.md b/scripts/release/README.md
index 68ecf09f..421c60ce 100644
--- a/scripts/release/README.md
+++ b/scripts/release/README.md
@@ -16,10 +16,14 @@ Setup:
 
 Release:
 1. Update the version in pom.xml.
-2. mvn deploy
+2. mvn -Prelease deploy
 3. From oss.sontaype.org#stagingRepositories, login and check the release just
    uploaded. If good, use the close button above the repository list to make it
-   public. If there is a problem, the drop button will delete the release.
+   public. If there is a problem, the drop button can be used to delete the 
+   release.
 4. After the release is rsynced to the Maven Central repository, confirm
-   checksums match and verify signatures.
+   checksums match and verify signatures. Then press the release button.
+
+See http://central.sonatype.org/pages/releasing-the-deployment.html for details
+about releasing the deployment from sonatype.
 

From 5f7921544f08015f41c327c21dd034b449153636 Mon Sep 17 00:00:00 2001
From: ejacox <jacox_edwin@hotmail.com>
Date: Tue, 21 Mar 2017 11:29:11 -0700
Subject: [PATCH 2/2] moved maven deployment documentation to the development
 doc

---
 doc/source/development.rst | 27 +++++++++++++++++++++++++++
 scripts/release/README.md  | 29 -----------------------------
 2 files changed, 27 insertions(+), 29 deletions(-)
 delete mode 100644 scripts/release/README.md

diff --git a/doc/source/development.rst b/doc/source/development.rst
index bcea5b8b..1373ee50 100644
--- a/doc/source/development.rst
+++ b/doc/source/development.rst
@@ -79,3 +79,30 @@ we create a release using the following process:
 #. Follow steps 1-5 in the process for `Development releases`_ above,
    except using the ``release-$MAJOR.$MINOR`` branch as the base
    instead of ``master``.
+
++++++++++++++++++++++++++++++++++
+Releasing to the Maven repository
++++++++++++++++++++++++++++++++++
+
+Prerequisites/Setup:
+1. Create a GPG key. Review [the Maven guidelines on working
+with keys](http://central.sonatype.org/pages/working-with-pgp-signatures.html),
+2. Set up your environment (add it to keys).
+    a. Add the GPG key to the KEYS file.
+    b. Copy (or incorporate) the settings.xml file to ``~/.m2/settings.xml``
+       and add your GPG key and sonatype login. There is an example file in 
+       the scripts/release directory. 
+3. Obtain a sonatype login (request from the project manager).
+
+Release:
+1. Update the version in pom.xml.
+2. Run ``mvn -Prelease deploy`` from the schemas directory.
+3. From oss.sontaype.org#stagingRepositories, login and check the release just
+   uploaded. If good, use the close button above the repository list to make it
+   public. If there is a problem, the drop button can be used to delete the 
+   release.
+4. After the release is rsynced to the Maven Central repository, confirm
+   checksums match and verify signatures. Then press the release button.
+
+See http://central.sonatype.org/pages/releasing-the-deployment.html for details
+about releasing the deployment from sonatype.
diff --git a/scripts/release/README.md b/scripts/release/README.md
deleted file mode 100644
index 421c60ce..00000000
--- a/scripts/release/README.md
+++ /dev/null
@@ -1,29 +0,0 @@
-Notes for release managers
----
-
-This document describes how to make a GA4GH schemas release.
-
-Prerequisites:
-1. Create a GPG key. Review [the Maven guidelines on working
-with keys](http://central.sonatype.org/pages/working-with-pgp-signatures.html),
-Setup your environment (add it to keys).
-2. Obtain a sonatype login (request from the project manager).
-
-Setup:
-1. Add the GPG key to the KEYS file.
-1. Copy (or incorporate) the settings.xml file to ```~/.m2/settings.xml``` and
-   add your GPG key and sonatype login.
-
-Release:
-1. Update the version in pom.xml.
-2. mvn -Prelease deploy
-3. From oss.sontaype.org#stagingRepositories, login and check the release just
-   uploaded. If good, use the close button above the repository list to make it
-   public. If there is a problem, the drop button can be used to delete the 
-   release.
-4. After the release is rsynced to the Maven Central repository, confirm
-   checksums match and verify signatures. Then press the release button.
-
-See http://central.sonatype.org/pages/releasing-the-deployment.html for details
-about releasing the deployment from sonatype.
-