+1 (binding) Chris
Details of what I checked:
Source-Release
- Signatures: OK
- Hashes: OK
- LICENSE, NOTICE, README, RELEASE_NOTES exist: OK
- README refers to wrong paths after the latest changes in the build
(client/target/iotdb-client-0.8.0 instead of client/cli ... same for server)
- RAT: OK
- The .checkstyle file doesn't have an Apache Header (minor issue)
- There seem to be some log files included in the source-bundle
(client/logs/* and tsfile/logs/*) they don't have Apache headers, but I think
this is just a minor thing (In general the source-release shouldn't contain log
files)
- The only binaries found are pictures
- Building:
- server as in the readme (mvn clean package -pl server -am
-Dmaven.test.skip=true): OK
- client as in the readme (mvn clean package -pl client -am
-Dmaven.test.skip=true): OK
- full build with all tests (mvn clean verify): OK
- Running Server: OK
- Running Client: OK
- No reference of SNAPSHOT versions: OK
- Only the Hadoop pom and the Dockerfile still reference SNAPSHOT
versions (minor)
Binary distribution:
- Signatures: OK
- Hashes: OK
- Running Server: OK
- Running Client: OK
Am 06.08.19, 16:56 schrieb "Julian Feinauer" <j.feina...@pragmaticminds.de>:
Hi all,
thanks to cdutz for finding some major issues in RC2 and fixing them we are
able to already provide RC3 now.
Important: All PMCs please note that you have to CHECK the release
artifacts [1] (see below) before being allowed to vote “+1”, see [3,4].
Apache IoTDB (Incubating) 0.8.0 has been staged under [1] and it’s time to
vote
on accepting it for release. All Maven artifacts are available under [2].
If approved we will seek final release approval from the IPMC.
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.
Release tag: release/0.8.0
Hash for the release tag: 2f4da03b05d1c063eaaca622c68de86abe35de22
Per [3] "Before voting +1 [P]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://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.0/rc3
[2] https://repository.apache.org/content/repositories/orgapacheiotdb-1003
[3] https://www.apache.org/dev/release.html#approving-a-release
[4]
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
