[drat.wiki] branch master updated: Created Release Process (markdown)

[ma...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mattmann pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/drat.wiki.git


The following commit(s) were added to refs/heads/master by this push:
     new ee1c259  Created Release Process (markdown)
ee1c259 is described below

commit ee1c259fbe50c12b0bd95141bcb0dcf2c9b59b14
Author: Chris Mattmann <ch...@gmail.com>
AuthorDate: Sat Sep 28 10:18:10 2019 -0700

    Created Release Process (markdown)
---
 Release-Process.md | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/Release-Process.md b/Release-Process.md
new file mode 100644
index 0000000..e18ab7d
--- /dev/null
+++ b/Release-Process.md
@@ -0,0 +1,17 @@
+## Pre-Reqs
+
+  1. Read [the OODT Release Process](https://cwiki.apache.org/confluence/display/OODT/Release+Process). It's got plenty of tips and tricks and helps you get your environment set up and all your Apache bits configured.
+  2. Make sure you have [set your useful DRAT environment variables](https://github.com/apache/drat/wiki/Installation#useful-environment-variables)
+  3. Make sure you have Maven, GPG and Java installed.
+
+## Begin Release
+
+  1. from the DRAT top level directory, make sure the version is set appropriately for all the Maven modules. Youc an use the [mvn:versions plugin here](https://stackoverflow.com/questions/5726291/updating-version-numbers-of-modules-in-a-multi-module-maven-project). For example, `mvn versions:set -DnewVersion=1.1-SNAPSHOT` if you are about to release 1.1.
+  2. `mvn release:prepare` (and make sure that the tag looks like `release-X.Y` when you set it and the other versions look right. E.g., for 1.1, make sure the SCM tag is `release-1.1`)
+  3. `mvn release:perform`
+
+## Send Email 
+
+  1. Use the Apache OODT template from its release guide.
+
+That's it!