How to Verify Release

Verify the candidate version

For detailed check list, please refer to the official check list

Version content accessible in browser https://dist.apache.org/repos/dist/dev/hertzbeat/

1. Download the candidate version

Download the candidate version to be released to the local environment Need to rely on gpg tool, if not, it is recommended to install gpg2.

주의

If the network is poor, downloading may be time-consuming. The download is completed normally in about 20 minutes, please wait patiently.

#If there is svn locally, you can clone to the local
$ svn co https://dist.apache.org/repos/dist/dev/hertzbeat/`release_version`-`rc_version`/
#or download the material file directly
$ wget https://dist.apache.org/repos/dist/dev/hertzbeat/`release_version`-`rc_version`/xxx.xxx

2. Verify that the uploaded version is compliant

Start the verification process, which includes but is not limited to the following content and forms.

2.1 Check whether the release package is complete

The package uploaded to dist must include the source code package, and the binary package is optional.

1. Whether to include the source code package
2. Whether to include the signature of the source code package
3. Whether to include the sha512 of the source code package
4. If the binary package is uploaded, also check the contents listed in (2)-(4)

2.2 Check gpg signature

First import the publisher's public key. Import KEYS from the svn repository to the local environment. (The person who releases the version does not need to import it again, the person who helps to do the verification needs to import it, and the user name is enough for the person who issued the version)

2.2.1 Import public key

-curl  https://downloads.apache.org/hertzbeat/KEYS > KEYS # Download KEYS
gpg --import KEYS # Import KEYS to local

2.2.2 Trust the public key

Trust the KEY used in this version:

$ gpg --edit-key xxxxxxxxxx #KEY user used in this version
gpg (GnuPG) 2.2.21; Copyright (C) 2020 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Secret key is available.
gpg> trust #trust
Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)

  1 = I don't know or won't say
  2 = I do NOT trust
  3 = I trust marginally
  4 = I trust fully
  5 = I trust ultimately
  m = back to the main menu

Your decision? 5 #choose 5
Do you really want to set this key to ultimate trust? (y/N) y  #choose y

gpg>

2.2.3 Check the gpg signature

for i in *.tar.gz; do echo $i; gpg --verify $i.asc $i; done

check result

If something like the following appears, it means the signature is correct. Keyword: Good signature

apache-hertzbeat-${release_version}-src.tar.gz
gpg: Signature made XXXX
gpg: using RSA key XXXXX
gpg: Good signature from "XXX <xxx@apache.org>"

2.3 Check sha512 hash

for i in *.tar.gz; do echo $i; sha512sum --check  $i.sha512; done

2.4 Check the binary package

unzip apache-hertzbeat-${release.version}-bin.tar.gz

tar -xzvf apache-hertzbeat-${release.version}-bin.tar.gz

check as follows:

• Check whether the source package contains unnecessary files, which makes the tar package too large
• There are LICENSE and NOTICE files
• The year in the NOTICE file is correct
• Only text files exist, not binary files
• All files have ASF license at the beginning
• Able to compile correctly
• .....

2.5 Check the source package

If the binary/web-binary package is uploaded, check the binary package.

Unzip apache-hertzbeat-${release_version}-src.tar.gz

cd apache-hertzbeat-${release_version}-src

compile the source code: Build HertzBeat Binary Package

and check as follows:

• There are LICENSE and NOTICE files
• The year in the NOTICE file is correct
• All text files have ASF license at the beginning
• Check the third-party dependent license:
• Compatible with third-party dependent licenses
• All third-party dependent licenses are named in the LICENSE file
• If you are relying on the Apache license and there is a NOTICE file, then these NOTICE files also need to be added to the version of the NOTICE file
• .....

You can refer to this article: ASF Third Party License Policy

3. Email reply

If you initiate a posting vote, you can refer to this response example to reply to the email after verification

Attention

When replying to the email, you must bring the information that you have checked by yourself. Simply replying to +1 approve is invalid.

When new PMC votes in the dev@hertzbeat.apache.org hertzbeat community, Please bring the binding suffix to indicate that it has a binding vote for the vote in the hertzbeat community, and it is convenient to count the voting results.

Non-PMC member:

+1 (non-binding)
I checked:
     1. All download links are valid
     2. Checksum and signature are OK
     3. LICENSE and NOTICE are exist
     4. Build successfully on macOS(Big Sur)
     5.

PMC member:

+1 (binding)
I checked:
     1. All download links are valid
     2. Checksum and signature are OK
     3. LICENSE and NOTICE are exist
     4. Build successfully on macOS(Big Sur)
     5.

---

This doc refer from Apache StreamPark