[plc4x] branch develop updated: Updated the guides for building with an empty repo on Windows and added a template that can be used for the vote response email.

[cd...@apache.org]

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

cdutz pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/plc4x.git


The following commit(s) were added to refs/heads/develop by this push:
     new 49d4962  Updated the guides for building with an empty repo on Windows and added a template that can be used for the vote response email.
49d4962 is described below

commit 49d49629139b218ef3eeaed171b7b36a07148d8b
Author: Christofer Dutz <ch...@c-ware.de>
AuthorDate: Fri Sep 10 03:52:58 2021 -0700

    Updated the guides for building with an empty repo on Windows and added a template that can be used for the vote response email.
---
 .../asciidoc/developers/release/validation.adoc    | 28 +++++++++++++++++++++-
 1 file changed, 27 insertions(+), 1 deletion(-)

diff --git a/src/site/asciidoc/developers/release/validation.adoc b/src/site/asciidoc/developers/release/validation.adoc
index ebb9b0a..e9d627a 100644
--- a/src/site/asciidoc/developers/release/validation.adoc
+++ b/src/site/asciidoc/developers/release/validation.adoc
@@ -68,7 +68,7 @@ NOTE: Especially in the `sandbox` there may be parts that are not formally relea
 [%interactive]
 * [ ] Search for `Copyright` references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file.
 * [ ] Build the project according to the information in the README.md file.
-* [ ] [RM] Build the project with all `with-xyz` profiles and tests enabled and an empty maven local repo: by appendng `-Dmaven.repo.local=../.m2`.
+* [ ] [RM] Build the project with all `with-xyz` profiles and tests enabled and an empty maven local repo: by appending `-Dmaven.repo.local=../.m2` (On windows use `-D"maven.repo.local"="../.m2"`).
 
 === Using RAT
 
@@ -103,3 +103,29 @@ This will download all the files into a directory: `downloaded-plc4x-{current-fu
 After that it will calculate the SHA512 hash and compare it with the staged hash.
 
 Last not least it will validate the PGP key and print out some information on it.
+
+=== Template for the email for voting
+
+----
++1/-1 (binding)
+
+Name
+
+[] Download all staged artifacts under the url specified in the release vote email.
+[] Verify the signature is correct.
+[] Check if the signature references an Apache email address.
+[] Verify the SHA512 hashes.
+[] Unzip the archive.
+[] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
+[] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
+[] [RM] Verify the staged source README, RELEASE_NOTE files correspond to those in the extracted source bundle.
+[] [RM] Run RAT externally to ensure there are no surprises.
+[] Search for SNAPSHOT references: Only found some in the dummy website copy in the integration-tests
+[] Search for Copyright references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file.
+[] Build the project according to the information in the README.md file.
+[] [RM] Build the project with all with-xyz profiles and tests enabled and an empty maven local repo.
+----
+
+If everything is ok, I put "OK" int the square brackets.
+If there are minor issues, I put "MINOR" in there and, if it's a short reason, I put an explanation at the end of the line. If it's longer I put a longer section after the checklist.
+If there are major issues, I put "FAIL" in there and comment the same way as with minor issues.
\ No newline at end of file