HI,
Signing of a RM keys is not a requirement to make a release, you can make a
release without this step. It’s is nice to have this, but is not needed.
Thanks,
Justin
Lei Rui created IOTDB-306:
-
Summary: count query is not that fast
Key: IOTDB-306
URL: https://issues.apache.org/jira/browse/IOTDB-306
Project: Apache IoTDB
Issue Type: Improvement
Hi,
After one weeks disappearance, I am back to the community now :D
And I have signed Jialin's GPG key @Jialin, hope it does not delayed your
RM work.
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Hi,
+1 (PPMC vote)
I have checked following items:
Source release:
1. Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the
extracted source bundle (Correct)
2. Compile and build code with command: mvn clean package. (Correct)
3. Verifying the signature (ASC) (Correct)
4.
I also write a document to introduce how to sign other's key, you can get
it at [1].
It is translated from calcite's document[2].
Hope it is helpful for you.
[1]
https://cwiki.apache.org/confluence/display/IOTDB/How+to+certify+someone%27s+GPG+key+in+Chinese
[2]
Hi,
+1 (PPMC vote)
The followings are successfully verified:
Source release:
1. ASC sinature
2. Hashes
3. LICENSE, NOTICE, README, RELEASE_NOTES
4. RAT
5. mvn clean package
6. start server and client
7. execute basic operations and reboot
8. python client
Binary distribution:
1. ASC