Thanks ChungEn for working on the release.

Tests from following features were covered as part of regression testing and 
successfully executed on RC0.

Ozone Filesystem
Ozone S3
Ozone wire encryption
Ozone HA (both OM and SCM)
Ozone Trash
Ozone SPNEGO
Ozone MapReduce
Ozone Container Replication/Re-replication
Ozone Pipeline
Ozone TDE (Transparent data encryption)
Ozone Container Balancer
Ozone Erasure Coding
Ozone Hive, Spark, Impala (Basic Integration)
Ozone Multitenancy
Ozone DN decommissioning
Ozone hsync
Ozone snapshots

Sammi has also scoped in for running few performance/benchmarking tests. Thanks 
for that.

- Nilotpal Nandi

On 2025/10/28 02:33:34 Sammi Chen wrote:
> The goal of run Ozone tests is to verify there are no regression issues for
> this new release.
> Because the tests will likely take a week to finish, it can save time when
> it's running concurrently with the RC review process.
> Noticed the HDDS-13792 since Attila has left the comments.  There could be
> other changes(add/remove), thus new RCs.
> If new changes are not in the key path, and not fundamental, tests with RC0
> results can still be valid, and whether to start a new round of tests
> against new RCs can be a choice.
> 
> 
> On Tue, 28 Oct 2025 at 01:33, Ethan Rose <[email protected]> wrote:
> 
> > For HDDS-13792 we would need to update the protolock files as well. I guess
> > this would be done on the 2.1 branch and then cherry-picked back to
> > master. HDDS-12982 also came up in the community sync today as an issue
> > that was reverted on master which also needs to be reverted on the release
> > branch.
> >
> > On Mon, Oct 27, 2025 at 4:08 AM Sammi Chen <[email protected]> wrote:
> >
> > > I created a canary build with ozone-2.1.0-RC0
> > > <https://github.com/apache/ozone/releases/tag/ozone-2.1.0-RC0> tag,
> > > and Nilotpal will help to run some Ozone tests.  Thanks Nilotpal!
> > >
> > > The test is expected to be completed by the end of this week if
> > everything
> > > goes well.
> > >
> > > On Wed, 22 Oct 2025 at 05:14, Chung En Lee <[email protected]> wrote:
> > >
> > > > Hi Ozone community, Please try out and cast your vote for the Ozone
> > 2.1.0
> > > > release candidate 0. 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.1.0-RC0
> > > All
> > > > resolved jiras:
> > > >
> > > >
> > >
> > https://issues.apache.org/jira/browse/HDDS-13821?jql=project%20%3D%20HDDS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.1.0
> > > > <
> > > >
> > >
> > 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.1.0-rc0/ The Maven
> > > > artifacts
> > > > are staged at:
> > > >
> > https://repository.apache.org/content/repositories/orgapacheozone-1033/
> > > > PGP
> > > > key: https://dist.apache.org/repos/dist/release/ozone/KEYS
> > Fingerprint:
> > > > 5D7C98B18E5F04D8
> > > >   Per Apache policy, this release candidate vote will open for 7 days
> > > until
> > > > the end of September 29 2025. PMC members can cast binding votes while
> > > > committers and community contributors are welcomed to cast non-binding
> > > > votes. Best regards, ChungEn
> > > >
> > >
> >
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to