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 dc60e58 formatting
dc60e58 is described below
commit dc60e585b8f510f6222c54af1372f4286898ec36
Author: Chris Mattmann <[email protected]>
AuthorDate: Sat Oct 5 16:14:09 2019 -0700
formatting
---
Release-Process.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Release-Process.md b/Release-Process.md
index 24a62b6..28d4bc3 100644
--- a/Release-Process.md
+++ b/Release-Process.md
@@ -10,7 +10,7 @@
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`)
- 2.1 Note if you see messages like
+ <br/>2.1 Note if you see messages like
```[INFO] [INFO] --- maven-gpg-plugin:1.6:sign (sign-release-artifacts)
@ dms ---
[INFO] gpg: signing failed: Inappropriate ioctl for device
[INFO] gpg: signing failed: Inappropriate ioctl for device
