+1 (binding) * Verified the signature and checksums * Verified tag * Build from source * Start a cluster using binary package * Run freon command * Run ozonesecure acceptance test * Verified information displayed on Recon UI * Verified basic file commands * Verified the reconfig commands
Thanks Yiyang for driving this! On Thu, 11 Jan 2024 at 01:12, Yiyang <yiyang0...@apache.org> wrote: > Hello all, > > As discussed in the last email, I am calling for a vote on Apache Ozone > 1.4.0 RC1. > > - 1584 Jiras were resolved as part of this release: > - > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20HDDS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%201.4.0 > - The RC1 tag can be found on Github at: > - https://github.com/apache/ozone/releases/tag/ozone-1.4.0-RC1 > - The source and binary tarballs can be found at: > - https://dist.apache.org/repos/dist/dev/ozone/1.4.0-rc1/ > - Maven artifacts are staged at: > - > > https://repository.apache.org/content/repositories/orgapacheozone-1022/ > - The public key used to sign the artifacts can be found at: > - https://dist.apache.org/repos/dist/release/ozone/KEYS > - The fingerprint of the key used to sign the artifacts is: > - 8E79A8F5563EA1D080DD75DE52AD71D85FD4D759 > > > > The vote will run for 7 days, ending on Jan 18th 2024 at 10:00 am > UTC+8. > > > For suggestions mentioned in last email: > > - BSD-tar showing warnings for GNU-tar. > - *Fixed by building in Ubuntu.* > - Hidden files found after untaring with GNU-tar. > - *Fixed by building in Ubuntu.* > - Empty directories in binary tarball. > - *Empty directores not introduced by releasing.* > - Update Ratis version to 3.0.1. > - *Fixed by cherry-pick HDDS-10035.* > - Signing key length not valid. > - *Fixed by using RSA4096 signing key* > - JIRA URL not showing correct JIRA issues. > - *Fixed in above description.* > - Builder with common user name. > - *Fixed by using name of "ozone".* > > > > > > -------- > > Thanks > > Yiyang >
