+1 (binding) Chris
This time all seems to have worked. [OK] Download all staged artifacts under the url specified in the release vote email into a directory we’ll now call download-dir. [OK] Verify the signature is correct and references an Apache Email address [OK] Verify the SHA512 hashes: [OK] Unzip the archive: [OK] Verify the existence of LICENSE, NOTICE, DISCLAIMER files in the extracted source bundle. [OK] Verify the content of LICENSE, NOTICE, DISCLAIMER files in the extracted source bundle. [MINOR] Run RAT externally to ensure there are no surprises. [OK] Search for SNAPSHOT references [OK] Search for Copyright references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file. [OK] Build the project according to the Maven defaults Remarks: Rat complains about the Dockerfile not having an Apache header ... however it does have one. Not sure why RAT doesn't like it. Am 09.09.20, 15:54 schrieb "Christofer Dutz" <[email protected]>: Apache Training (Incubating) Tools 1.0.0 RC2 has been staged under [2] and it’s time to vote on accepting it for release. All Maven artifacts are available under [1]. Voting will be open for 72hr. A minimum of 3 binding +1 votes and more binding +1 than binding -1 are required to pass. Repository: https://gitbox.apache.org/repos/asf/incubator-training.git Release tag: releases/tools/1.0.0 Hash for the release tag: 15513a9b48f94f389678107e0e59dc1b7359ef44 Per [3] "Before voting +1 PMC members are required to download the signed source code package, compile it as provided, and test the resulting executable on their own platform, along with also verifying that the package meets the requirements of the ASF policy on releases." You can achieve the above by following [4]. [ ] +1 accept (indicate what you validated - e.g. performed the non-RM items in [4]) [ ] -1 reject (explanation required) [1] https://repository.apache.org/content/repositories/orgapachetraining-1001 [2] https://dist.apache.org/repos/dist/dev/incubator/training/tools/1.0.0/rc2/ [3] https://www.apache.org/dev/release/validation.html#approving-a-release [4] https://plc4x.apache.org/developers/release/validation.html
