Thanks Ethan for creating a new RC.  Looks mostly good to me:

* Verified signatures, checksums
* Verified source matches ozone-1.2.0-RC1 tag
* Verified docs are present in binary tarball
* Verified `ozone version` (version number, git revision)
* Built from source without local Maven cache
* Executed upgrade acceptance test with both source and binary

However, I noticed one minor issue, in the output of `ozone version`:

Source code repository https://github.com/errose28/hadoop-ozone.git -r
9ee6f1872dca8469057d3c7bf880931c0e7b7f3e
Compiled by ethanrose on 2021-11-04T16:49Z

It should point to the Apache repo.  Here's the output from the
previous release for comparison:

Source code repository https://github.com/apache/ozone.git -r
f2406c4b4eb2b1295d06ec379cfe684ed9a16637
Compiled by ppogde on 2021-04-09T04:10Z

-Attila

On Thu, Nov 4, 2021 at 8:26 PM Ethan Rose <er...@cloudera.com.invalid> wrote:
>
> Hello all,
>
> Fixes have been applied on top of RC0 and I would now like to call a vote
> for RC1. RC1 fixes the following issues with RC0:
> - Docs are now included in the release tarball.
> - HDDS-5908 has been included to fix a potential read failure for multi
> part upload keys.
> - HDDS-5933 has been included to fix a dependency issue that was causing an
> unnecessary size increase in the release tarball.
>
> 472 Jiras were resolved as part of this release. RC0 fixed 468 jiras. Each
> of the above mentioned jiras had an original fix jira and a cherry pick
> jira for the release branch, resulting in the increase of 4 fixes over RC0.
> https://issues.apache.org/jira/browse/HDDS-5893?jql=project%20%3D%20HDDS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%201.2.0
>
> The RC1 tag can be found on Github at:
> https://github.com/apache/ozone/releases/tag/ozone-1.2.0-RC1
>
> The source and binary tarballs can be found at:
> https://dist.apache.org/repos/dist/dev/ozone/1.2.0-rc1/
>
> Maven artifacts are staged at:
> https://repository.apache.org/content/repositories/orgapacheozone-1002/
>
> The public key used to sign the artifacts can be found at:
> https://dist.apache.org/repos/dist/dev/ozone/KEYS
>
> The fingerprint of the key used to sign the artifacts is:
> 00D357B731EBDD66D7CA91B39146CE06B541B7E7
>
> Thanks,
> Ethan Rose

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
For additional commands, e-mail: dev-h...@ozone.apache.org

Reply via email to