You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@drat.apache.org by ma...@apache.org on 2019/10/05 23:07:28 UTC
[drat.wiki] branch master updated: fix GPG doco
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 8495866 fix GPG doco
8495866 is described below
commit 8495866b76a15a2940ff2da09a896eaf84dcc1c5
Author: Chris Mattmann <ch...@gmail.com>
AuthorDate: Sat Oct 5 16:07:27 2019 -0700
fix GPG doco
---
Release-Process.md | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Release-Process.md b/Release-Process.md
index 40781a8..24a62b6 100644
--- a/Release-Process.md
+++ b/Release-Process.md
@@ -10,6 +10,12 @@
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
+ ```[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
+ ```
+ You need to see [here](https://gist.github.com/repodevs/a18c7bb42b2ab293155aca889d447f1b) for an easy solution.
3. `mvn release:perform`
## Send Email