+1 (non-binding) 1. Verified signatures and checksums. 2. Maven build sucessfully from source tarball. 3. Ran `docker-compose` and successfully started a cluster. 4. Verified the output of `ozone version`. 5. Verified UIs (om, scm and recon). 6. Used `ozone shell` to create/delete volume/bucket and tried to read/write key.
Thanks to Sammi for doing this for Ozone 1.0.0 release. Sorry, my last email wasn' formatted correctly. Neo Yang On 2020/08/25 14:01:02, Sammi Chen <sammic...@apache.org> wrote: > RC1 artifacts are at: > https://home.apache.org/~sammichen/ozone-1.0.0-rc1/ > <https://home.apache.org/~sammichen/ozone-1.0.0-rc0/> > > Maven artifacts are staged at: > https://repository.apache.org/content/repositories/orgapachehadoop-1278 > <https://repository.apache.org/content/repositories/orgapachehadoop-1277> > > The public key used for signing the artifacts can be found at: > https://dist.apache.org/repos/dist/release/hadoop/common/KEYS > > The RC1 tag in github is at: > https://github.com/apache/hadoop-ozone/releases/tag/ozone-1.0.0-RC1 > <https://github.com/apache/hadoop-ozone/releases/tag/ozone-1.0.0-RC0> > > Change log of RC1, add > 1. HDDS-4063. Fix InstallSnapshot in OM HA > 2. HDDS-4139. Update version number in upgrade tests. > 3. HDDS-4144, Update version info in hadoop client dependency readme > > *The vote will run for 7 days, ending on Aug 31th 2020 at 11:59 pm PST.* > > Thanks, > Sammi Chen > --------------------------------------------------------------------- To unsubscribe, e-mail: ozone-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-dev-h...@hadoop.apache.org
