+1 Verified signatures. Verified checksum. Built from source. Verified 'ozone version' output of binary. Ran basic freon commands..
Thanks Wei-Chiu for driving the release. -Sadanand On Fri, 11 Apr 2025, 21:09 Devesh Singh, <deveshsi...@cloudera.com.invalid> wrote: > Thank you Wei-Chiu for all the release work. > > +1 > > * Built from source > * Verified Checksums > * Verified Signature > * Checked the docs in the release package. > * Verified Mac build package instructions. > * Verified few volume and bucket and few OM and SCM admin commands. > > Thanks > Devesh > > > > On 11 Apr 2025, at 6:18 PM, Zita Dombi <zitado...@apache.org> wrote: > > > > Thank you Wei-Chiu for working on the release! > > > > +1 (non-binding) > > > > - Built it from source > > - Verified signatures > > - Verified checksums > > - Checked the docs in the release tarball > > - Verified `ozone version` output > > - Tried a few `ozone sh` commands > > - Ran the upgrade compatibility acceptance tests > > > > Thanks, > > Zita Dombi > > > > Wei-Chiu Chuang <weic...@cloudera.com.invalid> ezt írta (időpont: 2025. > > ápr. 10., Cs, 22:53): > > > >> Thanks Nicholas for the detailed report! > >> Those are probably made in the dist-layout-stitching script. The license > >> files are in the repo/tarball, but at different locations. > >> > >> On Thu, Apr 10, 2025 at 12:28 PM Tsz-Wo Nicholas Sze < > szets...@gmail.com> > >> wrote: > >> > >>> +1 > >>> > >>> - Verified all checksums and signatures. > >>> > >>> - Checked LICENSE and NOTICE. > >>> > >>> - Compared the files in the src tarball with the files in git. Below > >>> are the files found in the tarball but not in git. > >>> DESTINATION_NOT_EXIST: cp "ozone-2.0.0-src/licenses/LICENSE-guava.txt" > >>> "../git-ozone/licenses/LICENSE-guava.txt" > >>> DESTINATION_NOT_EXIST: cp "ozone-2.0.0-src/licenses/LICENSE-nvd3.txt" > >>> "../git-ozone/licenses/LICENSE-nvd3.txt" > >>> DESTINATION_NOT_EXIST: cp > >>> "ozone-2.0.0-src/licenses/LICENSE-angular-nvd3.txt" > >>> "../git-ozone/licenses/LICENSE-angular-nvd3.txt" > >>> DESTINATION_NOT_EXIST: cp > >>> "ozone-2.0.0-src/licenses/LICENSE-bootstrap.txt" > >>> "../git-ozone/licenses/LICENSE-bootstrap.txt" > >>> DESTINATION_NOT_EXIST: cp > >>> "ozone-2.0.0-src/licenses/LICENSE-glyphicons.txt" > >>> "../git-ozone/licenses/LICENSE-glyphicons.txt" > >>> DESTINATION_NOT_EXIST: cp > >>> "ozone-2.0.0-src/licenses/LICENSE-jquery.txt" > >>> "../git-ozone/licenses/LICENSE-jquery.txt" > >>> DESTINATION_NOT_EXIST: cp > >>> "ozone-2.0.0-src/licenses/LICENSE-angular.txt" > >>> "../git-ozone/licenses/LICENSE-angular.txt" > >>> DESTINATION_NOT_EXIST: cp > >>> > >>> > >> > "ozone-2.0.0-src/hadoop-ozone/ozonefs-hadoop3-client/dependency-reduced-pom.xml" > >>> > >>> > >> > "../git-ozone/hadoop-ozone/ozonefs-hadoop3-client/dependency-reduced-pom.xml" > >>> DESTINATION_NOT_EXIST: cp > >>> > "ozone-2.0.0-src/hadoop-ozone/ozonefs-shaded/dependency-reduced-pom.xml" > >>> "../git-ozone/hadoop-ozone/ozonefs-shaded/dependency-reduced-pom.xml" > >>> > >>> It seems that the source tarball was generated by some maven > >>> packaging. Should we generate it by simply tar over the source root > >>> dir? This is a minor issue not requiring another RC. > >>> > >>> - Built from source successfully using JDK 8, JDK 11 and JDK 23. > >>> > >>> - Passed all unit tests. > >>> https://github.com/szetszwo/ozone/actions/runs/14373156040 > >>> > >>> - Manual started a cluster from the binary tarball in my laptop > machine: > >>> Successfully started one OM, one SCM and one datanode. > >>> Successfully created volumes and buckets. > >>> Failed to create keys due to not enough datanode (only one) > >>> Failed to start more datanodes: datanode is running as process > >>> 41418. Stop it first. > >>> * Will see if it can be worked around. These are minor issues not > >>> requiring another RC. > >>> > >>> - Found a minor issue: > >>> OZONE_CONF_DIR is "etc/hadoop" but not "etc/ozone"; filed HDDS-12818 > >> [1]. > >>> > >>> Wei-Chiu, thanks again for working on the release! > >>> > >>> Tsz-Wo > >>> [1] https://issues.apache.org/jira/browse/HDDS-12818 > >>> > >>> > >>> On Thu, Apr 10, 2025 at 12:09 PM Ayush Saxena <ayush...@gmail.com> > >> wrote: > >>> > >>>> +1 (Binding) > >>>> > >>>> * Built from source > >>>> * Verified Checksums > >>>> * Verified Signature > >>>> * Validated no code diff b/w git tag & src tar > >>>> * Verified the output of ozone version > >>>> * Ran some basic shell commands. > >>>> * Verified the NOTICE & LICENSE files > >>>> * Skimmed over the contents of ReleaseNotes, ChangeLog & maven > >> artifacts > >>>> > >>>> Thanx Wei-Chiu for driving the release, Good Luck!!! > >>>> > >>>> -Ayush > >>>> > >>>> On Fri, 11 Apr 2025 at 00:31, Nandakumar <na...@apache.org> wrote: > >>>>> > >>>>> Thanks Wei-Chiu for all the work. > >>>>> > >>>>> +1 > >>>>> > >>>>> * Verified signatures > >>>>> * Verified checksums > >>>>> * Verified ozone-2.0.0-RC2 tag > >>>>> * Built from source > >>>>> * Verified `ozone version` > >>>>> * Verified all the web UIs > >>>>> * Deployed a pseudo-cluster and verified basic read/write operations > >>>>> * Deployed a docker-cluster and verified basic read/write operations > >>>>> > >>>>> Thanks, > >>>>> Nanda > >>>>> > >>>>> On Fri, Apr 11, 2025 at 12:19 AM Nilotpal Nandi < > >>>> nilotpalna...@apache.org> > >>>>> wrote: > >>>>> > >>>>>> Thanks Wei-Chiu. > >>>>>> I plan to run a few validation tests on this RC build. > >>>>>> It would be helpful if the availability could be extended through > >>>> mid-next > >>>>>> week. > >>>>>> > >>>>>> Thanks, > >>>>>> Nilotpal Nandi > >>>>>> > >>>>>> > >>>>>> > >>>>>> On 2025/04/10 18:28:07 Wei-Chiu Chuang wrote: > >>>>>>> We have three binding +1 votes so technically it passes. However, > >>> I'd > >>>>>> like > >>>>>>> to wait for a few more days so folks have more time to evaluate. > >>>>>>> Especially that @Nilotpal Nandi <nna...@cloudera.com> is > >> testing > >>>> the > >>>>>> RC2 > >>>>>>> using Cloudera's internal test infra. > >>>>>>> > >>>>>>> On Wed, Apr 9, 2025 at 2:33 PM Arpit Agarwal > >>>>>> <aagar...@cloudera.com.invalid> > >>>>>>> wrote: > >>>>>>> > >>>>>>>> Hi folks, given this is our first major release in many years > >> it > >>>> will > >>>>>> be > >>>>>>>> good to have more people take a look at it and validate the > >>>> release. > >>>>>>>> > >>>>>>>> Is there any way we can scan the RPC interfaces for potential > >>>>>>>> incompatibilities that might prevent 1.x fat clients from > >> talking > >>>> to a > >>>>>> 2.x > >>>>>>>> service or vice versa? The application interfaces (s3 and > >> Hadoop > >>>> FS) > >>>>>> should > >>>>>>>> be stable in any case. > >>>>>>>> > >>>>>>>> Thanks, > >>>>>>>> Arpit > >>>>>>>> > >>>>>>>> > >>>>>>>> On Apr 4, 2025 at 3:28:53 AM, Wei-Chiu Chuang < > >>> weic...@apache.org> > >>>>>> wrote: > >>>>>>>> > >>>>>>>>> Here's the RC2: > >>>>>>>>> > >>>>>>>>> Git tag: > >>>>>> https://github.com/apache/ozone/releases/tag/ozone-2.0.0-RC2 > >>>>>>>>> > >>>>>>>>> 1708 resolved jiras: > >>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>> > >>>> > >>> > >> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20HDDS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.0.0 > >>>>>>>>> > >>>>>>>>> Source code and binary tarball: > >>>>>>>>> https://dist.apache.org/repos/dist/dev/ozone/2.0.0-rc2/ > >>>>>>>>> Maven artifacts: > >>>>>>>>> > >>>>>> > >>>> > >> https://repository.apache.org/content/repositories/orgapacheozone-1031/ > >>>>>>>>> > >>>>>>>>> Release page: https://jojochuang.github.io/release/2.0.0/ > >>>>>>>>> Full jira list: > >>>>>>>>> > >> https://issues.apache.org/jira/projects/HDDS/versions/12353070 > >>>>>>>>> > >>>>>>>>> RC1 and RC2 diff: > >>>>>>>>> > >>>>>>>> > >>>>>> > >>>> > >>> > >> > https://github.com/apache/ozone/compare/ozone-2.0.0-RC1...ozone-2.0.0-RC2 > >>>>>>>>> ea8762e509 (HEAD, tag: ozone-2.0.0-RC2, origin/ozone-2.0) > >>>> HDDS-12750. > >>>>>>>> Move > >>>>>>>>> StorageTypeProto from > >> ScmServerDatanodeHeartbeatProtocol.proto > >>> to > >>>>>>>>> hdds.proto (#8208) > >>>>>>>>> 24060a598c HDDS-12751. native build fails with CMake 4 > >> (#8215) > >>>>>>>>> 18f8e3fc0c HDDS-12703. Close pipeline command should display > >>>> error on > >>>>>>>>> failure (#8169) > >>>>>>>>> 847f9eb7a1 HDDS-12736. Bump hadoop-thirdparty to 1.4.0 > >> (#8193) > >>>>>>>>> af3e6c1525 HDDS-12724. hdds-rocks-native build fails if > >>> JAVA_HOME > >>>>>> not set > >>>>>>>>> (#8183) > >>>>>>>>> 85363a2ecb HDDS-12733. Bump axios to 0.30.0 (#8189) > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> On Wed, Mar 26, 2025 at 10:58 PM Wei-Chiu Chuang < > >>>> weic...@apache.org > >>>>>>> > >>>>>>>>> wrote: > >>>>>>>>> > >>>>>>>>> Here's RC1 vote: > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> Git tag: > >>>>>> https://github.com/apache/ozone/releases/tag/ozone-2.0.0-RC1 > >>>>>>>>> > >>>>>>>>> A total of 1699 resolved jiras: > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>> > >>>> > >>> > >> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20HDDS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.0.0 > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> Source code and binary tarball: > >>>>>>>>> > >>>>>>>>> https://dist.apache.org/repos/dist/dev/ozone/2.0.0-rc1/ > >>>>>>>>> > >>>>>>>>> Maven artifacts: > >>>>>>>>> > >>>>>>>>> > >>>>>> > >>>> > >> https://repository.apache.org/content/repositories/orgapacheozone-1030/ > >>>>>>>>> > >>>>>>>>> PGP key: https://dist.apache.org/repos/dist/dev/ozone/KEYS > >>>>>>>>> > >>>>>>>>> Fingerprint: 3ED23305D7631918 > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> RC0 and RC1 diff: > >>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>> > >>>> > >>> > >> > https://github.com/apache/ozone/compare/ozone-2.0.0-RC0...ozone-2.0.0-RC1 > >>>>>>>>> > >>>>>>>>> 7 commits: > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> HDDS-12327. HDDS-12668. Fix HSync upgrade test failure in > >>> non-HA > >>>>>> upgrade > >>>>>>>>> > >>>>>>>>> test (#8171) > >>>>>>>>> > >>>>>>>>> HDDS-12684. Update NOTICE and LICENSE file (#8160) > >>>>>>>>> > >>>>>>>>> HDDS-12327. Restore non-HA (to HA) upgrade test (#7880) > >>>>>>>>> > >>>>>>>>> HDDS-12662. Rename upgrade callback directory 1.5.0 to 2.0.0 > >>>> (#8131) > >>>>>>>>> > >>>>>>>>> HDDS-12668. HSync upgrade test failure (#8137) > >>>>>>>>> > >>>>>>>>> HDDS-12671. Include .editorconfig and .run in source tarball > >>>> (#8139) > >>>>>>>>> > >>>>>>>>> HDDS-12666. Remove -SNAPSHOT from OZONE_CURRENT_VERSION in > >>>> upgrade > >>>>>> test > >>>>>>>>> > >>>>>>>>> (#8136) > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> Please also take a look at the release page draft: > >>>>>>>>> > >>>>>>>>> https://jojochuang.github.io/release/2.0.0/ > >>>>>>>>> > >>>>>>>>> Full CHANGELOGS > >>>>>>>>> > >>>>>>>>> https://jojochuang.github.io/release/2.0.0/changelog.2.0.0/ > >>>>>>>>> > >>>>>>>>> Full ReleaseNotes: > >>>>>>>>> > >>>>>>>>> > >> https://jojochuang.github.io/release/2.0.0/releasenotes.2.0.0/ > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> changelogs and releasenotes are generated by Apache Yetus > >>>>>>>> releasedocmaker: > >>>>>>>>> > >>>>>>>>> ./releasedocmaker --project HDDS --version 2.0.0 > >> --projecttitle > >>>>>> "Apache > >>>>>>>>> > >>>>>>>>> Ozone" --fileversions --dirversions --usetoday > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> On Fri, Mar 21, 2025 at 3:42 PM Wei-Chiu Chuang < > >>>> weic...@apache.org> > >>>>>>>>> > >>>>>>>>> wrote: > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>> Hi Ozone community, > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>>> Please try out and cast your vote for the Ozone 2.0.0 > >> release > >>>>>> candidate > >>>>>>>>> 0. > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>>> This is a huge release, containing 1691 resolved jiras, > >>>> numerous > >>>>>>>> features > >>>>>>>>> > >>>>>>>>>> and stability improvements. > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>>> Release process: > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>> > >>>> > >>> > >> > https://ozone-site-v2.staged.apache.org/docs/developer-guide/project/release-guide/ > >>>>>>>>> > >>>>>>>>>> Git tag: > >>>>>> https://github.com/apache/ozone/releases/tag/ozone-2.0.0-RC0 > >>>>>>>>> > >>>>>>>>>> All resolved jiras: > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>> > >>>> > >>> > >> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20HDDS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.0.0 > >>>>>>>>> > >>>>>>>>>> Source code and binary tarball: > >>>>>>>>> > >>>>>>>>>> > >> https://dist.apache.org/repos/dist/release/ozone/2.0.0-rc0/ > >>>>>>>>> > >>>>>>>>>> The Maven artifacts are staged at: > >>>>>>>>> > >>>>>>>>>> > >>>>>>>> > >>>>>> > >>>> > >> https://repository.apache.org/content/repositories/orgapacheozone-1029/ > >>>>>>>>> > >>>>>>>>>> PGP key: https://dist.apache.org/repos/dist/dev/ozone/KEYS > >>>>>>>>> > >>>>>>>>>> Fingerprint: 3ED23305D7631918 > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>>> Per Apache policy, this release candidate vote will open > >> for > >>> 7 > >>>> days > >>>>>>>> until > >>>>>>>>> > >>>>>>>>>> the end of March 28th 2025. PMC members can cast binding > >>> votes > >>>>>> while > >>>>>>>>> > >>>>>>>>>> committers and community contributors are welcomed to cast > >>>>>> non-binding > >>>>>>>>> > >>>>>>>>>> votes. > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>>> Best regards, > >>>>>>>>> > >>>>>>>>>> Weichiu > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>> > >>>>>> > >> --------------------------------------------------------------------- > >>>>>> To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org > >>>>>> For additional commands, e-mail: dev-h...@ozone.apache.org > >>>>>> > >>>>>> > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org > >>>> For additional commands, e-mail: dev-h...@ozone.apache.org > >>>> > >>>> > >>> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org > For additional commands, e-mail: dev-h...@ozone.apache.org > >
