This is an automated email from the ASF dual-hosted git repository.
aharui pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-asjs.wiki.git
The following commit(s) were added to refs/heads/master by this push:
new bcf7288 Updated Release Steps Jobs On Jenkins (markdown)
bcf7288 is described below
commit bcf72885a65f6475ee5b097611f92fd9827dc45a
Author: aharui <[email protected]>
AuthorDate: Sun Jun 23 09:09:04 2019 -0700
Updated Release Steps Jobs On Jenkins (markdown)
---
Release-Steps-Jobs-On-Jenkins.md | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Release-Steps-Jobs-On-Jenkins.md b/Release-Steps-Jobs-On-Jenkins.md
index ef30fbf..f15ef94 100644
--- a/Release-Steps-Jobs-On-Jenkins.md
+++ b/Release-Steps-Jobs-On-Jenkins.md
@@ -6,6 +6,11 @@ Historically, only one person has been able to run the
releasecandidate.xml scri
The purpose of verification is to convince the RM that it is safe to GPG sign
the artifacts created on a shared server like the CI Server. This is done by
having the release scripts create JARs and SWCs that are binary identical no
matter what computer builds the binary (Mac or Win). This assumes that the RM
has the same versions of Java and Ant (for sure) and probably Maven.
+Current versions are:
+* Java: 1.8.0_152
+* Ant: 1.9.9
+* Maven: Apache Maven 3.6.0
+
The Ant source package is verified in a slightly different way. The
verification script clones the tags from the 3 repos onto the RM's computer and
builds its own source package. The result will not binary match what the CI
server generated because making it match would require running a Maven plug-in
and we don't want to require that everyone who wants to build a release package
(for nightly builds and other reasons) have both Ant and Maven. We only want
to require that of RMs for no [...]
## Security
